Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 978376

Summary: consumer/consumer group - how to update all pkgs on a consumer or group?
Product: [Retired] Pulp Reporter: Brad Buckingham <bbuckingham>
Component: consumersAssignee: Jeff Ortel <jortel>
Status: CLOSED DUPLICATE QA Contact: Preethi Thomas <pthomas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.1.1CC: mhrivnak, skarmark
Target Milestone: ---Keywords: Triaged
Target Release: 2.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-02 18:54:27 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:    
Bug Blocks: 950743    

Description Brad Buckingham 2013-06-26 13:31:50 UTC 
Description of problem:

From the pulp v2 documentation, it is unclear how to use the API to trigger an update of all packages on a consumer or consumer group.  The goal is to be able to perform the equivalent of a 'yum update' on a single consumer or on all consumers within a consumer group. 

Documentation:

Consumer:
  - http://pulp-dev-guide.readthedocs.org/en/pulp-2.1/integration/rest-api/consumer/content.html#update-content-on-a-consumer

  Note: There is an option for 'all'; however, based on discussion, it seems that the user must still pass in package names.

Consumer Group:
http://pulp-dev-guide.readthedocs.org/en/pulp-2.1/integration/rest-api/index.html

  Note: I don't see any content management docs for consumer groups.

Version-Release number of selected component (if applicable):
pulp-server-2.1.2-0.3.beta.el6.noarch
Comment 1 Michael Hrivnak 2013-08-02 18:54:27 UTC 

*** This bug has been marked as a duplicate of bug 979587 ***