Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/User_Guide/sect-Lifecycle_Environments.html
Section Number and Name:
3.3. Lifecycle Environments
Describe the issue:
Lifecycle environment: It is clear what it does. What is missing is how to promote a sytem from one environment to another or a link to a relevant section explaining this
Suggestions for improvement:
Megan/Mirek: New Sections on Promoting systems (products?) from one environment to another
Comment 1RHEL Program Management
2014-10-16 09:23:02 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Hayley,
I'm going to throw this to you to triage. Can we fit this into 6.1? This is the first I've heard about the changed functionality. It seems like a small change and may only require the removal of "you can only promote to the next env in sequence" but PM may want more, including use cases and examples as per 1169876.
thanks