Bug 1353616

Summary:	[RFE] Provide option to automatically update Composite content view when a child content view is incrementally updated
Product:	Red Hat Satellite	Reporter:	sthirugn <sthirugn>
Component:	Errata Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, bkearney, egolov, jcallaha, ktordeur, pgervase, sthirugn
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-08 18:46:25 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:

Description sthirugn@redhat.com 2016-07-07 15:08:08 UTC

Description of problem:
Provide option to automatically update Composite content view when a child content view is incrementally updated

Version-Release number of selected component (if applicable):
Satellite 6.2 Beta Snap 18.2

How reproducible:
Always

Steps to Reproduce:
1. Create a content view, add repos, publish, promote
2. Create a composite content view with content view from step1 and select the latest version, publish, promote
3. Incremental update the content view from Step 1

Actual results:
The composite content view is not automatically updated

Expected results:
The composite content is automatically updated

Additional info:
see:
https://bugzilla.redhat.com/show_bug.cgi?id=1304891#c10
https://bugzilla.redhat.com/show_bug.cgi?id=1304891#c12

Comment 2 Evgeni Golov 2017-05-23 14:25:39 UTC

IMHO a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1177766

Comment 3 sthirugn@redhat.com 2017-06-05 21:06:32 UTC

@Evgeni: This bug talks about auto promoting composite CV when a child CV is incrementally updated. The bug that you linked in Comment 2 talk about Content view promotion in general.

Are you sure that this issue is addressed for Incremental update scenario as well?  If so, move this bug to ON_QA.  Let's not close this as a dupe as I like QE to test this specifically for Incremental update scenario.

Comment 4 Evgeni Golov 2017-06-06 06:35:16 UTC

Hi,

yes/no/maybe ;)

https://bugzilla.redhat.com/show_bug.cgi?id=1177766 is in POST, but it should not be (see https://bugzilla.redhat.com/show_bug.cgi?id=1177766#c15). The linked upstream redmine (http://projects.theforeman.org/issues/15950) is only about providing a "latest" version for CVs, which we now have. But this still does not trigger automatic publish of the CCV if the underlying CV changed, which you and 1177766 are talking about

So I *think* that it should not matter whether the underlying CV is changed incrementally or not 
* for the "latest" version in the CCV to point to the really latest one
* for the triggering of an automatic publish/promote

We have 1, but we don't have 2.

But you are right and we should keep both RFEs open, just to have both ways to change the CV be part of QE for that feature.

Comment 5 Bryan Kearney 2018-03-08 18:46:25 UTC


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