Red Hat Bugzilla – Bug 1263062
Can create a content view and promote it straight from Library to the "production" environment, by-passing all other lifecycle environments
Last modified: 2015-10-16 13:07:14 EDT
Description of problem:
When creating a new Content View, I can publish it in the Library, and then promote to ANY environment (e.g. Production), by-passing Development and any previous environments which form part of the predefined lifecycle. Is this a design feature (is this why there is a star next to the "suggested environment")?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a Content view (and associate Puppet modules, repositories,etc)
2.Publish the view into the library
3.Assume Current lifecycle is Library-> Development -> ProdProd -> Prod.
4.Promote into Prod (without promoting into Development and Preprod). An error message comes up "Force Promote? Suggested Environment is Development".
5.Select "Promote" in the error message - the content is now being promoted straight to Prod
Same goes for any version of the Content View, which can be promoted to ANY environment, e.g. Pre-Prod (with the same error message).
*** This bug has been marked as a duplicate of bug 1104346 ***