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.
I created DEV --> TEST --> PRODUCTION
Our new release management process needs it to be this...
DEV --> TEST --> STAGE --> PRODUCTION
But, I have a zillion templates and systems associated to these environments. So some addition and rename, or moving everything around is *painful*. I want to do a true "insert".
How should changesets between TEST and PRODUCTION created before introducing of the new environment look like? Should we change them to act like they were created between TEST and STAGE and do some "fake" changeset between STAGE and PRODUCTION?
Needinfo answer (geez, from 2012!)...
How should changesets be appropriately managed? Dunno. Maybe STAGE in this example, when initialized, becomes a clone of TEST and then the plumbing is rewired? Or some such?
It doesn't seem like rocket science, on the surface.
This is an older bug which I do not envision being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.
Verified with Sat 6.4 snap 22.
Insertion of environments in to environment list works for every position, It's possible to insert at first,last position or anywhere between two existing environments.
After the new environment is inserted, there is no sign of a problem with promotion of content view to newly inserted environment. Same with Content Hosts, everything works as expected.