Bug 784634

Summary:	[RFE] User would like to get a report of which packages need to be updated on a consumer
Product:	[Retired] Pulp	Reporter:	Jeff Ortel <jortel>
Component:	consumers	Assignee:	Jeff Ortel <jortel>
Status:	CLOSED DUPLICATE	QA Contact:	Preethi Thomas <pthomas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Master	CC:	jason.dobies, kbsingh, mmccune, skarmark
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	2.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-05 15:09:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Ortel 2012-01-25 16:11:50 UTC

Feature Request:

User's would like to get a report of which packages need to be updated on a consumer and probably consumer groups.

This could be provided by adding a flag to package (install, update, remove) operations that would indicate the transaction is not to be commited (is a "dry run").  This approach would support a wide range of use cases including this one.  We'd need to expose this flag in the pulp agent, manager layer, REST API layer and CLI.

The gofer package plugin already supports an "apply" flag which creates the YUM transaction but does not execute it.

Comment 1 Mike McCune 2012-01-25 16:23:50 UTC

just some thoughts

Comment 2 Mike McCune 2012-01-25 17:30:50 UTC

please ignore my previous comment.  I had no real coherent thoughts and decided to just add myself to the CC instead.   

if and when you discuss how to implement this please let me know, would like to be part of any discussions.

Comment 3 Jay Dobies 2012-11-28 23:21:36 UTC

I think this is a duplicate based on a recent bug filed by Katello asking for this view. I aligned this bug to sprint 43 when that other one is aligned to (didn't look it up, we can address it in sprint 43) and we will likely close this out as a duplicate.

Comment 4 Jay Dobies 2013-02-05 15:09:10 UTC

Closing as a duplicate. This functionality is available with the fix to 877061.

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