Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1263062 - Can create a content view and promote it straight from Library to the "production" environment, by-passing all other lifecycle environments
Summary: Can create a content view and promote it straight from Library to the "produc...
Keywords:
Status: CLOSED DUPLICATE of bug 1104346
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-15 04:56 UTC by Nelli Zinder
Modified: 2015-10-16 17:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-16 17:07:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nelli Zinder 2015-09-15 04:56:58 UTC 
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):
6.1

How reproducible:

Always

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).

Actual results:


Expected results:


Additional info:
Comment 1 Bryan Kearney 2015-10-16 17:07:14 UTC 

*** This bug has been marked as a duplicate of bug 1104346 ***
Note You need to log in before you can comment on or make changes to this bug.