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: Upgrade job gets stuck in GUI investigation stage.
Version-Release number of selected component (if applicable):
6.10 Snap16
How reproducible:
always with snap15 and snap16
Steps to Reproduce:
1. Restore the 6.9.z satellite by using a specific customers database backup.
2. Satellite restored successfully.
3. Run the pulp migration.
4. Pulp migration completes successfully.
5. Run the upgrade check with assumeyes flag but the job stucks at ui investigation stage.
Actual results:
The job stuck and there was no method except UI to proceed with the job, In UI, there was a cancellation option but it was in disabled.
Expected results:
The job should be canceled or moved to the stopped stage until the upgrade process has not been completed.
Additional info:
Verified on 6.10.1 Snap1
Verification points:
- The satellite upgrade didn't get failed due to "ForemanInventoryUpload::Async::GenerateAllReportsJob" task.
- Verified the foreman-maintain fixed-in version.
# rpm -qa|grep rubygem-foreman_maintain-0.8.21
rubygem-foreman_maintain-0.8.21-1.el7sat.noarch
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.1 Async Bug Fix Update), 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:4737