This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2262958 - [RFE] There is no option to set lifecycle environment for Ansible roles
Summary: [RFE] There is no option to set lifecycle environment for Ansible roles
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-06 08:38 UTC by yopatil@redhat.com
Modified: 2024-06-06 17:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:01:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-23084 0 None Migrated None 2024-06-06 17:01:43 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.