Bug 785810

Summary:	[RFE] ability to insert new environments in an environment path
Product:	Red Hat Satellite	Reporter:	Todd Warner <taw>
Component:	Content Views	Assignee:	Ondřej Pražák <oprazak>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jameer Pathan <jpathan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	bkearney, jsherril, mmccune, omaciel, tstrych
Target Milestone:	Unspecified	Keywords:	FutureFeature, Reopened
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/13983
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-07 14:21:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.