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.

Bug 2176272

Summary: new wait task introduced by rh_cloud 6.0.44 is not recognized by maintain as OK to interrupt
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: Satellite MaintainAssignee: Evgeni Golov <egolov>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.1CC: bbuckingham, ehelms, juwatts, lpramuk, zhunting
Target Milestone: 6.12.3Keywords: AutomationBlocker, Regression, Triaged, Upgrades
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-1.1.12-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2164330 Environment:
Last Closed: 2023-04-04 15:20:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Lukas Pramuk 2023-03-17 15:25:30 UTC
FailedQA.

@Satellite 6.12.3 Snap1
rubygem-foreman_maintain-1.2.6-1.el8sat.noarch

we bumped gem version unintentionally - provided 6.13.0 rubygem in 6.12.z repo

I'd expect rubygem-foreman_maintain-1.1.11-1.el8sat be in 6.12.3 repo instead

Comment 4 Lukas Pramuk 2023-03-29 09:13:39 UTC
VERIFIED.

@Satellite 6.12.3 Snap3
rubygem-foreman_maintain-1.1.12-1.el8sat.noarch

by the upgrade automation running 6.12.1 -> 6.12.3 upgrade

# foreman-maintain upgrade check --plaintext --whitelist="repositories-validate" --target-version 6.12.z -y
...

--------------------------------------------------------------------------------
Check for running tasks:                                              [OK]
--------------------------------------------------------------------------------
Check for old tasks in paused/stopped state:                          [OK]
--------------------------------------------------------------------------------
Check for pending tasks which are safe to delete:                     [OK]
--------------------------------------------------------------------------------
Check for tasks in planning state:                                    [OK]
--------------------------------------------------------------------------------
...

>>> there are now no running tasks reported so the upgrade can proceed

Comment 9 errata-xmlrpc 2023-04-04 15:20:04 UTC
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 (Important: Satellite 6.12.3 Async Security 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/RHSA-2023:1630