Bug 789144

Summary:	Promotions - packages not listed in next environment for promoted products and repos
Product:	Red Hat Satellite	Reporter:	Brad Buckingham <bbuckingham>
Component:	WebUI	Assignee:	Brad Buckingham <bbuckingham>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Og Maciel <omaciel>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	6.0.1	CC:	cwelton, mmccune, tstrachota
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-22 18:26:06 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:
Bug Depends On:
Bug Blocks:	747354

Description Brad Buckingham 2012-02-09 22:54:31 UTC

Description of problem:

After a user promotes either a product or repo to the 'next environment', the packages promoted cannot be viewed from the the Promotions content tree for that next environment.

Version-Release number of selected component (if applicable):
git master

How reproducible:
always

Steps to Reproduce:

From Content Management -> Promotions:

1a. promote a product from env A to B

or

1b. promote a repo from env A to B

2. after the promotion completes, go to env B (i.e. next env) and navigate in the left content tree to : Products -> [product] -> Packages
  
Actual results:

The packages that were in the Products/Repos promoted from A are not listed.

Expected results:

The packages that were in the Products/Repos promoted from A are listed.

Additional info:

Comment 1 Tomas Strachota 2012-02-10 12:18:47 UTC

From my tests: This affects only promotions started from UI. CLI shows them ok.

If you promote a product from CLI and check UI, packages are listed.

Comment 2 Brad Buckingham 2012-02-10 13:21:53 UTC

commit - 4ca672f85438260cbe0635296b4dd863f0ff4041

The UI is using 'search' for retrieving the list of packages and errata.  The issue found was that after a product or repo was promoted the packages/errata were not indexed for the next environment.  As a result, when the user would navigate to it, they would not see any packages in the new product/repos; however, the content is really there (e.g. registered systems could still consume it).

Comment 3 Corey Welton 2012-02-17 21:25:36 UTC

QA Verified. Packages promoted to $env now show up as expected when said $env is chosen

Comment 5 Mike McCune 2013-08-16 18:13:47 UTC

getting rid of 6.0.0 version since that doesn't exist