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 785810 - [RFE] ability to insert new environments in an environment path
Summary: [RFE] ability to insert new environments in an environment path
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Ondřej Pražák
QA Contact: Jameer Pathan
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 16:43 UTC by Todd Warner
Modified: 2022-10-10 12:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-07 14:21:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13983 0 Normal Closed ability to insert new environments in an environment path 2019-12-22 23:40:54 UTC

Description Todd Warner 2012-01-30 16:43:18 UTC 
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".
Comment 1 Ivan Necas 2012-04-05 13:17:38 UTC 
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?
Comment 2 Mike McCune 2013-08-16 18:22:12 UTC 
getting rid of 6.0.0 version since that doesn't exist
Comment 3 Todd Warner 2015-09-11 19:03:07 UTC 
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.
Comment 4 Ondřej Pražák 2016-03-01 15:58:47 UTC 
Created redmine issue http://projects.theforeman.org/issues/13983 from this bug
Comment 5 Bryan Kearney 2016-03-10 19:45:30 UTC 
Upstream bug assigned to oprazak
Comment 6 Bryan Kearney 2016-07-08 20:41:01 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 8 Og Maciel 2017-04-17 18:19:28 UTC 
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.
Comment 9 Justin Sherrill 2018-09-05 02:01:00 UTC 
Reopening as this was fixed upstream.  Moving this to ON_QE for 6.4.
Comment 10 tstrych 2018-09-21 16:11:52 UTC 
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.
Comment 11 Bryan Kearney 2018-11-07 14:21:54 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.