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:
When there are pending tasks in the background and the upgrade is started the upgrade might fail and the user has a complex recovery process to fix all aborted tasks and also the upgrade process in katello-install upgrade might not run until the end because of conflicting tasks
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Start RedHat sync of 50 channels
2. Start Content View publishing with 30.000+ packages
3. Start the katello-installer --upgrade
Actual results:
- Conflicting tasks preventing upgrade process to finsihed successful
- Aborted tasks after upgrade
- Complex recovery process similair to https://access.redhat.com/solutions/1381053
Expected results:
The katello-installer shall only start the upgrade when no pending tasks are running. The user shall wait for tasks to finsih or stop them manual first.
The katello-installer shall put Sat6 in a global 'suspended' state that no new tasks are started during the upgrade
Additional info:
In 6.2.0, we introduced the pre-upgrade check script which includes this.
See: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/installation-guide/#upgrading_satellite_server 2.b.:
"Run the pre-upgrade check script to get a list of hosts that can be deleted after upgrading. If any unassociated hosts are found, associating them to an organization before upgrading is recommended.
# foreman-rake katello:upgrade_check
If the upgrade check reports a failure due to running tasks, then it is recommended that you wait for the tasks to complete. It is possible to cancel some tasks, but you should follow the guidance in the Red Hat Knowledgebase solution How to manage paused tasks on Red Hat Satellite 6 to understand which tasks are safe to cancel and which are not safe to cancel. "
Thanks!