Bug 2262958

Summary:	[RFE] There is no option to set lifecycle environment for Ansible roles
Product:	Red Hat Satellite	Reporter:	yopatil <yopatil>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.12.0	CC:	ahumbe, dsinglet, egolov, nalfassi, rlavi, sajha
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:01:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description yopatil@redhat.com 2024-02-06 08:38:35 UTC

1. Proposed title of this feature request.

- There is no option to set a lifecycle environment for Ansible roles on Red Hat Satellite.

2. What is the nature and description of the request?

At different stages of a lifecycle within Satellite, servers can access different versions of packages. Going for example from Dev -> Test -> Prod, promotions make new versions of packages visible so that they can be installed on different servers when the admins are confident that they won't break anything.

BUT

The same is not true of Ansible Roles. If we update a Role definition, that new definition is instantly visible everywhere and, therefore cannot go through the same test and promotion cycle. Not only does this mean that a particular version of a Role might be run on a Production system even though not properly tested, a role/package combination can get out of step, for example, if the configuration of a piece of software changes with package version, you might have a situation where for a particular server, it sees the earlier package but the later configuration Role


3. Is there already an existing RFE upstream or in Red Hat Bugzilla?

NA


4. Does the customer have any specific timeline dependencies and which release would they like to target?

NA

5. Is the sales team involved in this request and do they have any additional input?

NA

Comment 4 Eric Helms 2024-06-06 17:01:44 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.