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:
If the customer is prompted to enter a hammer password when running this command:
# satellite-maintain upgrade check --target-version 6.7
and if the wrong password is entered, the password field in "/etc/foreman-maintain/foreman-maintain-hammer.yml" changes to the incorrect password.
Version-Release number of selected component (if applicable):
6.7
How reproducible:
Only when the upgrade check prompts for a hammer password.
Steps to Reproduce:
1. cat /etc/foreman-maintain/foreman-maintain-hammer.yml to see the current password.
2. Run "satellite-maintain upgrade check --target-version 6.7".
3. If prompted for a hammer password, enter a different, incorrect password.
4. cat /etc/foreman-maintain/foreman-maintain-hammer.yml to see the incorrect password there.
Actual results:
System configuration is permanently changed by an upgrade check.
Expected results:
The system configuration should not be changed by a check.
Additional info:
Verified.
Tested on Satellite 6.10.0 Snap 16.0
Version: rubygem-foreman_maintain-0.8.13-2.el7sat.noarch
Steps:
1. # hammer user update --login admin --password <new-password>
2. # foreman-maintain advanced procedure run hammer-setup
Observation:
Step 2 fails firstly as it contains initial_admin_password set by satellite-answers.yaml, after updating password using step1, also requires an update in /etc/foreman-maintain/foreman-maintain-hammer.yml.
So when running step 2 again, it prompts for admin password, if entered incorrectly then it doesn't store password and exits with RC 1, else only when entered correctly this stores password in /etc/foreman-maintain/foreman-maintain-hammer.yml.
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 (Satellite 6.10 Satellite Maintenance 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/RHBA-2021:4697