Red Hat Bugzilla – Bug 1136091
hammer content-host errata apply is only async operation
Last modified: 2016-07-27 05:11:01 EDT
Description of problem: When I used remote package install/update/remove, the operation is synchronized by default. But When I try to use errata apply, the operation is asynchronous - hammer doesn't wait for pending status is changed. This behaviour is inconsistent. >> hammer --server <SERVER> --username <USER> --password <PASS> content-host errata apply -h Usage: hammer content-host package install [OPTIONS] Options: --async Do not wait for the task --content-host CONTENT_HOST_NAME Name to search by --content-host-id CONTENT_HOST_ID UUID of the content host --organization ORGANIZATION_NAME Organization name to search by --organization-id ORGANIZATION_ID --organization-label ORGANIZATION_LABEL Organization label to search by --packages PACKAGES List of package names Comma separated list of values. -h, --help print help >> hammer --server <SERVER> --username <USER> --password <PASS> content-host errata apply -h Usage: hammer content-host errata apply [OPTIONS] Options: --content-host CONTENT_HOST_NAME Name to search by --content-host-id CONTENT_HOST_ID UUID of the content host --errata-ids ERRATA_IDS List of Errata ids to install Comma separated list of values. --organization ORGANIZATION_NAME Organization name to search by --organization-id ORGANIZATION_ID --organization-label ORGANIZATION_LABEL Organization label to search by -h, --help print help Version-Release number of selected component (if applicable): rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch rubygem-hammer_cli-0.1.1-12.el6sat.noarch rubygem-hammer_cli_katello-0.0.4-14.el6sat.noarch rubygem-hammer_cli_foreman-0.1.1-16.el6sat.noarch How reproducible: always Steps to Reproduce: 1. register system 2. try to remote apply errata 3. check installed package from errata on system Actual results: 1) operation is asynchronous by default 2) lost synchronize operation Expected results: 1) operation is synchronize by default 2) I can use --async flag for asynchronous operation
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/11750 from this bug
Upstream hammer-cli-katello PR: https://bugzilla.redhat.com/show_bug.cgi?id=1136091
Upstream bug component is Content Management
Moving to POST since upstream bug http://projects.theforeman.org/issues/11750 has been closed ------------- Brad Buckingham Applied in changeset commit:hammer-cli-katello|fa017a14a31ebf603e628ac4e7b711af4a9f5902.
Currently, the Content Host registration is failing on Nightly most probably due to Host Unification feature. And hence blocked on verifying this bug.
I was verifying this in Sat 6.2 snap 6.1. I see --async option is added for errata apply but due to bug 1303570 I cant verify the operation is actually sync by default. So marking this bug as dependent of 1303570.
Verified in Satellite-6.2-Beta-Snap9 Synchronous: hammer> host errata apply --host-id=4 --errata-ids=RHBA-2016:0545 [...........................................................................................................................................] [100%] tuned-2.5.1-4.el7_2.3.noarch Asynchronous: hammer> host errata apply --host-id=4 --errata-ids=RHBA-2016:0546 --async Errata applied successfully But the success message is always displayed while the task was still running which is being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1329751
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