Hide Forgot
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?
getting rid of 6.0.0 version since that doesn't exist
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.
Created redmine issue http://projects.theforeman.org/issues/13983 from this bug
Upstream bug assigned to oprazak
Per 6.3 planning, moving out non acked bugs to the backlog
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.
Reopening as this was fixed upstream. Moving this to ON_QE for 6.4.
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.
Based on comment 10, I am closing this as currentrelease. If you are still seeing this issue on 6.4 please open a new bz.