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:
pre-migration step in foreman maintain asks for permission twice.
Version-Release number of selected component (if applicable):
@satellite 6.5.0
@rubygem-foreman_maintain-0.3.3-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. Run #foreman-maintain upgrade run --target-version 6.5
2. on "Procedures before migrating to Satellite 6.5" it asks twice for permission to continue.
Actual results:
Continue with [Procedures before migrating to Satellite 6.5], [y(yes), n(no), q(quit)] y
Continue with [Procedures before migrating to Satellite 6.5], [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.5
================================================================================
disable active sync plans:
- Total 0 sync plans are now disabled. [OK]
--------------------------------------------------------------------------------
Expected results:
Continue with [Procedures before migrating to Satellite 6.5], [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.5
================================================================================
disable active sync plans:
- Total 0 sync plans are now disabled. [OK]
--------------------------------------------------------------------------------
Additional info:
Verified
Verified with:
- Satellite 6.6.0 snap 19
- rubygem-foreman_maintain-0.4.8-1.el7sat.noarch
Steps to Reproduce:
1. Run #foreman-maintain upgrade run --target-version 6.6.z --whitelist repositories-validate
Observation:
- pre-migration step of foreman maintain didn't ask for permission twice.
Continue with [Procedures before migrating to Satellite 6.6.z], [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.6.z
================================================================================
disable active sync plans:
| Total 0 sync plans are now disabled. [OK]
--------------------------------------------------------------------------------
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, 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-2019:3181