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.
+++ This bug was initially created as a clone of Bug #979587 +++
Note that the --name flag is required:
$ pulp-admin rpm consumer package update run
Command: run
Description: triggers an immediate package update on a consumer
Available Arguments:
--consumer-id - (required) unique identifier; only alphanumeric, -, and _
allowed
--name, -n - (required) package name; may repeat for multiple packages
--no-commit - test the transaction without committing it
--reboot - reboot after a successful transaction
--import-keys - import GPG keys as needed
--all, -a - update all content units
The following options are required but were not specified:
--consumer-id
--name
This is not useful for users who want to apply all available updates to a consumer.
Instead, it would make more sense if we got rid of the -a flag, and defaulted to installing all updates if no -n flags were passed. This would be more consistent with yum and other package managers' behaviors.
--- Additional comment from Michael Hrivnak on 2013-08-02 14:54:28 EDT ---
--- Additional comment from Sayli Karmarkar on 2013-09-06 11:56:44 EDT ---
Merged.
$ pulp-admin rpm consumer package update run --help
Command: run
Description: triggers an immediate package update on a consumer
Available Arguments:
--bg - if specified, the client process will end immediately (the
task will continue to run on the server)
--consumer-id - (required) unique identifier; only alphanumeric, ., -, and _
allowed
--name, -n - package name; may repeat for multiple packages. if
unspecified, all packages are updated
--no-commit - test the transaction without committing it
--reboot - reboot after a successful transaction
--import-keys - import GPG keys as needed
--- Additional comment from Jeff Ortel on 2013-09-12 18:35:29 EDT ---
build: 2.3.0-0.10.alpha
--- Additional comment from Preethi Thomas on 2013-09-19 13:58:50 EDT ---
[root@pulp-v2-server ~]# rpm -qa pulp-admin-client
pulp-admin-client-2.3.0-0.14.alpha.el6.noarch
[root@pulp-v2-server ~]#
[root@pulp-v2-server ~]# pulp-admin rpm consumer package update run
Command: run
Description: triggers an immediate package update on a consumer
Available Arguments:
--bg - if specified, the client process will end immediately (the
task will continue to run on the server)
--consumer-id - (required) unique identifier; only alphanumeric, ., -, and _
allowed
--name, -n - package name; may repeat for multiple packages. if
unspecified, all packages are updated
--no-commit - test the transaction without committing it
--reboot - reboot after a successful transaction
--import-keys - import GPG keys as needed
The following options are required but were not specified:
--consumer-id
[root@pulp-v2-server ~]#