Bug 1329751

Summary: hammer host errata apply async - always displays success
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: HammerAssignee: Zach Huntington-Meath <zhunting>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, jcallaha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14860
Whiteboard:
Fixed In Version: rubygem-hammer_cli_katello-0.0.22.10-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:23:40 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:

Description sthirugn@redhat.com 2016-04-22 20:31:29 UTC 
Description of problem:
hammer host errata apply - always displays success. This is supposed to show the task id of the created task

Version-Release number of selected component (if applicable):
Satellite-6.2-Snap-9

How reproducible:
Always

Steps to Reproduce:
hammer> host errata apply --host-id=4 --errata-ids=RHBA-2016:0546 --async
Errata applied successfully

Actual results:
'Errata applied successfully' message displayed while the task is still running.

Expected results:
The confirmation message should display the task id of the created async task.

Additional info:
Comment 2 Zach Huntington-Meath 2016-04-27 19:23:07 UTC 
Created redmine issue http://projects.theforeman.org/issues/14860 from this bug
Comment 3 Bryan Kearney 2016-05-09 16:17:34 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14860 has been closed
Comment 4 jcallaha 2016-05-31 18:56:28 UTC 
Verified in Satellite 6.2 Beta Snap 13.

[root@rhsm-qe-1 ~]# hammer host errata apply --host-id 2 --errata-ids RHSA-2016:0064 --async
Errata is being applied with task a6540a82-f16f-4abc-8a89-df9a907712d4
Comment 5 Bryan Kearney 2016-07-27 11:23:40 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-2016:1501