Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: In Capsule upgrade, "yum update" dump some error messages.
Version-Release number of selected component (if applicable):
6.8 Snap14
How reproducible:
always
Steps to Reproduce:
1. Prepare the environment to perform the satellite-upgrade from 6.7 to 6.8.
2. Upgrade the satellite using workaround BZ#1875357#c6
3. Add the subscription and enable all the required repository to perform capsule upgrade from 6.7 to 6.8.
4. Execute "yum update -y" on capsule and get below warning messages.
.....
.....
warning: /etc/foreman-installer/scenarios.d/foreman-answers.yaml created as /etc/foreman-installer/scenarios.d/foreman-answers.yaml.rpmnew
ERROR: Selected scenario is DISABLED, can not continue.
Use --list-scenarios to list available options.
You can also --enable-scenario SCENARIO to make the selected scenario available.
warning: %post(foreman-installer-1:2.1.2.6-1.el7sat.noarch) scriptlet failed, exit status 27
Non-fatal POSTIN scriptlet failure in rpm package 1:foreman-installer-2.1.2.6-1.el7sat.noarch
Updating : 1:foreman-installer-katello-2.1.2.6-1.el7sat.noarch
.....
.....
warning: /etc/foreman-installer/scenarios.d/katello.yaml created as /etc/foreman-installer/scenarios.d/katello.yaml.rpmnew
ERROR: Selected scenario is DISABLED, can not continue.
Use --list-scenarios to list available options.
You can also --enable-scenario SCENARIO to make the selected scenario available.
ERROR: Selected scenario is DISABLED, can not continue.
Use --list-scenarios to list available options.
You can also --enable-scenario SCENARIO to make the selected scenario available.
warning: %post(foreman-installer-katello-1:2.1.2.6-1.el7sat.noarch) scriptlet failed, exit status 27
Non-fatal POSTIN scriptlet failure in rpm package 1:foreman-installer-katello-2.1.2.6-1.el7sat.noarch
Actual results:
Error messages appears in yum update.
Expected results:
Error and un-expected warning messages should not be come.
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4366