Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/index.html Section Number and Name: Page no. 9, Section 1.4.1 Base Operating System Describe the issue: In the Satellite 6.1 Installation Guide Documentation, on page # 09 where it has been mentioned that while registering the host system through RHSM, specify the type as a Red Hat Satellite server. Customer is unable to register the system with the type "Red Hat Satellite" but could successfully register the system with the type "Satellite". Hence requesting you to change the type from "Red Hat Satellite" to "Satellite" in the Satellite 6.1 Installation Guide Document. Suggestions for improvement: Change the type from "Red Hat Satellite" to "Satellite" in the Satellite 6.1 Installation Guide. Additional information: My findings: # subscription-manager register --type=Red Hat Satellite cannot parse argument: Hat cannot parse argument: Satellite # subscription-manager register --type=RedHatSatellite Username: rhn-support-jmadur Password: Unit type 'RedHatSatellite' could not be found. # subscription-manager register --type= Red Hat Satellite --> added a space cannot parse argument: Red cannot parse argument: Hat cannot parse argument: Satellite # subscription-manager register --type=Satellite Username: rhn-support-jmadur Password: The system has been registered with ID: 6d3b74fd-0376-455b-a4e2-8f98ec4484f4 We could see from the above command's output that the type 'Red Hat Satellite" is not working for registering the Satellite 6.1 server where as the type "Satellite" works and system gets registered.
I was just opening a new bug to say: The Guide says: "When registering your host system through Red Hat Subscription Manager (RHSM), specify the type as a Red Hat Satellite server: " This is misleading as it hints that something like "--type-satellite" is required. Suggestions for improvement: Delete that sentence. Quote from Tom McKay: The entire sentence could be removed. The example following that sentence, "subscription-manager register," is correct. Additional information: I think that part of the doc should be rewritten as a procedure.
+1 to the above, we should never use the --type flag, and the docs should be clear to not indicate or hint at this.
Hello I updated this Kbase to explain about the repos: What is katello-agent used for on Red Hat Satellite 6? - https://access.redhat.com/solutions/1392153 then discovered this: Satellite 6.1 now requires the use of the Satellite Tools repositories which replaces the use of Red Hat Common for client libraries - https://access.redhat.com/solutions/1427513
(In reply to Stephen Wadeley from comment #4) > Hello > > I updated this Kbase to explain about the repos: > What is katello-agent used for on Red Hat Satellite 6? - > https://access.redhat.com/solutions/1392153 > > then discovered this: > Satellite 6.1 now requires the use of the Satellite Tools repositories > which replaces the use of Red Hat Common for client libraries - > https://access.redhat.com/solutions/1427513 In *theory* (?) once we get the contents of a KBase included, verified, and released in the product doc, the KBase article is supposed to get retired. This is so we don't end up with duplicate or contradicting information, and we only have to update in one place. In practice this doesn't quite happen. At some point we should set up a firm process and policy for this, but that would have to happen between GSS, PM, and related ppl.
*** This bug has been marked as a duplicate of bug 1256498 ***