Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Hi Team,
The customer has requested similar functionality to the following:
"In Satellite 5.8 we were able to create configuration channels and upload/create files.
Each file had a way to control versioning.... say we wanted to deploy version 13 of a specific file or even roll back version 14 to version 13. We could easily do this.
In satellite v6.x, we are not seeing where this functionality resides. We need some assistance to show/demonstrate this ability.
If this functionality does not exist, we would like to open an enhancement request."
1. Proposed title of this feature request
Individual file versioning in satellite 6.x as compared to v5.8
2. What is the nature and description of the request?
See above from customer's description.
3. Why do you need this? (List the business requirements here)
The customer used this functionality in Satellite 5.8 to control configurations and needs it to work the same way in Satellite 6.
4. How would you like to achieve this? (List the functional requirements here)
The customer is providing Red Hat Engineering full latitude to decide how this is to be accomplished.
5. For each functional requirement listed, specify how Red Hat and your organization can test to confirm the requirement is successfully implemented.
NA
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
7. Do you have any specific timeline dependencies and which release would they like to target (i.e. RHEL8.3, Sat7)?
ASAP would be great!
8. List any affected packages or components.
Considering the future of Satellite, Ansible may be able to accomplish this.
9. Would you be able to assist in testing this functionality if implemented?
Yes