Hide Forgot
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:
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.
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).
QA Verified. Packages promoted to $env now show up as expected when said $env is chosen
getting rid of 6.0.0 version since that doesn't exist