Hide Forgot
Description of problem: "Update HTTP Proxy details" tasks ends up in paused state (even after resuming the task using foreman-maintain's foreman-tasks-not-paused check) after satellite upgrade from 6.6 to 6.7 causing Foreman-maintain's "foreman-tasks-not-paused" check to be failed. Version-Release number of selected component (if applicable): - Satellite 6.7.0 snap 8 - rubygem-foreman_maintain-0.5.1-1.el7sat.noarch - tfm-rubygem-foreman-tasks-0.17.5.1-1.el7sat.noarch How reproducible: - Always Steps to Reproduce: 1. Have satellite 6.6 with repos/products.(Reproducible in QE's upgrade automation) 2. Upgrade to 6.7 using foreman-maintain. 3. Foreman-maintain detects "Update HTTP Proxy details" task in paused state. 4. Try to resume the task using foreman-maintain. 5. "Update HTTP Proxy details" goes into paused state even after resuming, causing foreman-maintain check to fail, in turn causing a unsuccessful upgrade. Actual results: - "Update HTTP Proxy details" always ends up in paused state. Expected results: - "Update HTTP Proxy details" shouldn't be in paused state. Additional info: - Foreman-maintain issue BZ#1781128
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28834 has been resolved.
We still have 28837 to resolve.
BUILD TEAM: there are two issues that need cherry picking Moving to post as upstream issue is merged
Patrick, I don't see a cherry pick for the installer (puppet-katello) change?
Verified Verified with: - Satellite 6.7.0 snap 10 - foreman-installer-1.24.1.5-1.el7sat.noarch Test steps: 1. Have satellite 6.6 with repos/products. 2. Upgrade to 6.7 using foreman-maintain. Observations: - No paused task detected by foreman-maintain during update. - Upgrade completed successfully. - Http Proxy feature works as expected after upgrade.
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/RHSA-2020:1454