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 1781128

Summary: foreman-maintain failed to resume the paused task.
Product: Red Hat Satellite Reporter: Devendra Singh <desingh>
Component: Satellite MaintainAssignee: Kavita <kgaikwad>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: apatel, hhudgeon, kgaikwad, pcreech, sghai, vijsingh
Target Milestone: 6.7.0Keywords: AutomationBlocker, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.5.1-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 12:58:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1792836    
Bug Blocks:    

Description Devendra Singh 2019-12-09 11:49:52 UTC
Description of problem:
Foreman-maintain failed to resume the paused task. 

Version-Release number of selected component (if applicable):
6.7

How reproducible:
always

Steps to Reproduce:
1. Start upgrade using foreman-maintain from 6.6.0 to 6.7
2. Upgrade tasks completed successfully.
3. Running Procedures after migrating to Satellite 6.7, but it was failed while resuming the paused task.

 Warning: An error occured while loading module hammer_cli_csv.
 Total tasks found paused in error state: 1
 Total tasks resumed:                     1
 Resumed tasks:                           
  1) Task identifier: 544fbdae-ad73-4dbc-bbfe-4d69579f1101
     Task action:     Update http Capsule details
     Task errors:     The world 76a9b520-b5b7-4a94-bddb-60006e70846d is not active (terminating or terminated)

Actual results:
Failed to resume the pause task

Expected results:

Resume operation should be successfully completed.

Additional info: This issue faced in Snap4 too.

Comment 6 Jameer Pathan 2019-12-19 07:31:00 UTC
Issue seems to be that "Task action: Update http Capsule details" always 
ends up in paused state during upgrade.

Comment 7 Bryan Kearney 2019-12-30 09:03:14 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28479 has been resolved.

Comment 16 Jameer Pathan 2020-01-28 12:36:21 UTC
Verified

Verified with:
- Satellite 6.7.0 snap 10
- foreman-installer-1.24.1.5-1.el7sat.noarch
- rubygem-foreman_maintain-0.5.1-1.el7sat.noarch

Test steps:
1. Have satellite 6.6 with repos/products.
2. Upgrade Satellite to 6.7 version using foreman-maintain.

Observation:
- Satellite upgrade completed successfully.
- Foreman-maintain check related to paused task 
worked as expected.

Comment 20 errata-xmlrpc 2020-04-14 12:58:36 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, 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-2020:1442