Description of problem: The public docs and the internal documentation differ on the setup required for subscribing an image to katello Internal - http://documentation-stage.bne.redhat.com/docs/en-US/CloudForms/1.0/html/User_Documentation/sect-User_Documentation-Using_Synchronization-Registering_a_System.html Community - https://fedorahosted.org/katello/wiki/GuideSystemRegistrationClient Actual results: 1) The provided subscription instructions do not work for a private katello instance. I believe they'll register you to hosted (or similar). Expected results: 1) a series of instructions that when performed, subscribe a system to katello content 2) also, I'd expect to see some similar steps as outlined in the community registration page (https://fedorahosted.org/katello/wiki/GuideSystemRegistrationClient) Additional info: * Escalating as a final release blocker for CloudForms
Note, bug#790835 was fixed and the instructions have been updated to reflect this new procedure (see https://fedorahosted.org/katello/wiki/GuideSystemRegistrationClient). Lana, let me know if you need more detail. Someone from System Engine may be needed to document this feature.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Document how to subscribe an image to CFSE: https://fedorahosted.org/katello/wiki/GuideSystemRegistrationClient).
Lana: just trying to understand what the resolution is: are we adding this to the release notes only (and if so, how do we validate it?) or adding to the official docs for the 1.0 release?
(In reply to comment #9) > Lana: just trying to understand what the resolution is: are we adding this to > the release notes only (and if so, how do we validate it?) or adding to the > official docs for the 1.0 release? I believe this will be release noted for v1.0, and moved to the user guide for future releases. Lana, does that match your expectations? As for validating, the Cloud Engine crew has a similar bug. They are walking through the upstream instructions to see if they can backup the database(s) and configs, reinstall a fresh Engine system, and restore the previous database(s) and configs.
Back to assigned for doc update. LKB
Hi James, I've been comparing the steps in https://fedorahosted.org/katello/wiki/GuideSystemRegistrationClient and the ones we have added in the 1.1 User Guide. Can you review the following for us and let us know if more information needs to be added? http://documentation-devel.engineering.redhat.com/docs/en-US/CloudForms/1.1/html/System_Engine_User_Guide/Registering_a_System.html I realize that our "Registering systems" section deals only with activation key registration. I'd like some guidance between the options of using the bootstrap configuration and manual configuration. Are there any situations wherein manual configuration is required?
Hi Athene, I might divide up registration into the following sub-sections. As always, feel free to adjust to your liking ... 6.2. Registering a System 6.2.1 Configuration 6.2.1.1 Automated [ detail installing cert-consumer.rpm installation ] 6.2.1.2 Manual [ Detail updating /etc/rhsm/rhsm.conf via `subscription-manager config` ] 6.2.2 Registration [ subscription-manager register --org [your_CFSE_org_name] ] NOTE: Simplify registration with activation keys [ subscription-manager register --org [your_CFSE_org_name] --activationkey [your_CFSE_activation_key]] For more information on managing subscriptions and entitlements, consult the "RHEL Deployment Guide :: Chapter 4. Product Subscriptions and Entitlements" at https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/entitlements.html
mass-move of docs-related bugs to ecs-bugs. If this appears to be incorrect, feel free to bounce back to katello-qa-list and/or request clarification.
This documentation has now been dropped to translation ahead of publication. For any further issues, please open a new a bug. LKB
This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug. LKB
getting rid of 6.0.0 version since that doesn't exist