Project

General

Profile

Bug #11750

hammer content-host errata apply is only async operation

Added by Brad Buckingham over 3 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Hammer
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1136091
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

Associated revisions

Revision fa017a14 (diff)
Added by Brad Buckingham over 3 years ago

fixes #11750 - errata apply: update to support sync or async execution

Small update to support initiating an errata apply as a sync or
async operation. This makes the behavior for errata consistent with
the package actions.

Revision 30e049e9
Added by Brad Buckingham over 3 years ago

Merge pull request #313 from bbuckingham/issue-11750

fixes #11750 - errata apply: update to support sync or async execution

History

#1 Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/hammer-cli-katello/pull/313 added
  • Pull request deleted ()

#2 Updated by Brad Buckingham over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Eric Helms over 3 years ago

  • Category set to Hammer
  • Legacy Backlogs Release (now unused) set to 70
  • Triaged changed from No to Yes

Also available in: Atom PDF