Bug 1673414

Summary: [RFE] Allow setting of 6Server/7Server tag for 3rd party repositories
Product: Red Hat Satellite Reporter: Stefan Meyer <smeyer>
Component: Subscription ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: jcallaha
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: bkearney, rjerrido
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-15 13:37:54 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 Stefan Meyer 2019-02-07 13:22:57 UTC
1. Proposed title of this feature request
Allow setting of 6Server/7Server tag for 3rd party repositories via Satellite GUI and hammer


3. What is the nature and description of the request?
The customer is using docker base images for RHEL 6 and 7 to build images on a RHEL 7 host.
To allow the builds to succeed the assigned CV contains all required repositories for RHEL 6 and 7.
For Red Hat provided repositories they have a proper tag set for the OS and only the repos for correct
OS is visible inside the container build. For 3rd party repositories (like EPEL) this tag is not set
and both repositories for EPEL 6 and 7 can be enabled when building the container image.

There is already a "Restrict to architecture" in Sat 6.4 GUI but no option to limit the use on the RHEL release.


4. Why does the customer need this? (List the business requirements here)
- To prevent the installation of the wrong software in containers.
- It would also make it easier to create one CV for EPEL 6 and 7 that can be released at the same time.


5. How would the customer like to achieve this? (List the functional requirements here)
It is already possible to set the requiredtags flag in the candlepin database to achieve this:

candlepin=# update cp2_content set requiredtags='rhel-7-server' where label='org_Extra_Packages_for_Enterprise_Linux_Extra_Packages_for_Enterprise_Linux_7_x86_64';
candlepin=# update cp2_content set requiredtags='rhel-6-server' where label='org_Extra_Packages_for_Enterprise_Linux_Extra_Packages_for_Enterprise_Linux_6_x86_64';

There should be an option in the GUI and hammer commandline tool to set the "requiredtags" flag.


6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- For GUI it should be presented as an option in the repository configuration.
- For hammer an option to the "hammer repository update" command can be added like this
  # hammer repository update --release=7Server
  

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


8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
A future release of Satellite server


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


10. List any affected packages or components.
- candlepin
- katello
- hammer
- possibly pulp too


11. Would the customer be able to assist in testing this functionality if implemented?
Yes, they have a test environment for Satellite beta releases.

Comment 5 Rich Jerrido 2019-02-15 13:37:54 UTC

*** This bug has been marked as a duplicate of bug 1526564 ***