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.

Bug 1425481

Summary: Provisioning guide: Explain difference between 7Server and 7.x repositories
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: Docs Content Management GuideAssignee: Sergei Petrosian <spetrosi>
Status: CLOSED CURRENTRELEASE QA Contact: Russell Dickenson <rdickens>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.7CC: adahms, lzap, rdickens, sbream, swadeley
Target Milestone: Unspecified   
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: 2017-05-15 13:04:02 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 Lukas Zapletal 2017-02-21 14:29:46 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/pdf/provisioning_guide/Red_Hat_Satellite-6.2-Provisioning_Guide-en-US.pdf

In the provisioning guide, we do not explain difference between 7Server and 7.x repositories. The main aspect is that 7Server contains all updates from RHEL7 while 7.x (e.g. 7.2) is a specific release that will stop getting updates when next minor version comes out (7.3).

Please explain a good practice to create Operating System called RHEL7 associated with 7Server repositories when customer want to have clients getting all updates and OS called RHEL 7.x for each individual 7.x repository.

I've seen a customer who created RHEL7 OS and associated all 7.0, 7.1 ... 7.3 installation media to it, then they were switching installation media on the New Host form. While this is possible, it is NOT recommended because Satellite needs to redownload kernel/initramdisk to TFTP server everytime a change is made.

Comment 1 Andrew Dahms 2017-03-01 01:51:40 UTC
Assigning to Zac for review.

Zac - comment #5 of BZ#1321177 calls out a similar need and provides some good information about this issue as well.

What we need is some additional clarification based on the advice in that comment and in this bug to help users understand what to do.

Comment 4 Stephen Wadeley 2017-03-15 19:34:35 UTC
Hello

I think this subject is better explained where manifests and repositories are covered. I do not see any of that in the Provisioning Guide.

I have just done a review of all the places where manifests are covered here:
https://bugzilla.redhat.com/show_bug.cgi?id=1389768#c3

Perhaps the Content Strategist has a better idea.

Thank you

Comment 5 Steve Bream 2017-03-16 01:52:23 UTC
Hello,

Thank you Stephen, I agree that it makes sense to explain this where we discuss using repositories. Section 4.5 in the Content Management Guide (https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/content_management_guide/importing_red_hat_content#Importing_Red_Hat_Content-Selecting_Red_Hat_Repositories_to_Synchronize) already mentions these repos in the table detailing the repos that will be used in the sample scenario.

I suggest adding a note following this paragraph:

The relationship between products and specific repositories is connected through a cascading hierarchy. Select a product and this opens a list of repository sets for that product. Select a repository set and this opens a list of repositories that you can enable. For our scenario, select Red Hat Enterprise Linux Server, then Red Hat Enterprise Linux 7 Server (RPMs), then enable Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server. This enables the latest RPM files for Red Hat Enterprise Linux 7.

to explain the difference in the repositories and give the guidance that Lukas has suggested for using them.

I realize that this puts the note only in the GUI instructions, but I'm reluctant to add the same description twice. The only other option I can see is to add the note to the table listing the repos being selected for the sample scenario.

Does this seem a reasonable compromise to everyone?

Comment 6 Lukas Zapletal 2017-03-27 08:11:37 UTC
WFM thanks guys.

Comment 7 Andrew Dahms 2017-05-07 23:38:46 UTC
Re-assigning to Sergei based on current availability.

Sergei - see comment #5 for what is required in this bug, and let me know if you have any questions!

Comment 14 Sergei Petrosian 2017-05-15 13:04:02 UTC
These changes are now live on the customer portal.

Comment 16 Lukas Zapletal 2017-06-05 11:04:43 UTC
The way I understand this - kickstart repo is basically a "released DVD", you froze the distribution, add Anaconda to it, test it and then publish it. It never changes, updates go into "normal" 7.x or 7Server repos.