Description of problem: In the docs for RHN Satellite 3.5 beta, section 5.2 and 5.3 of RHN-satellite.pdf discuss giving the CertAdmin role to a user, creating new entitlement certificates, and uploading them. This functionality isn't there, if you follow the steps in the doc. Check with robin, but I believe that this is not supposed to be customer-visible, and therefore shouldn't be documented. Version-Release number of selected component (if applicable): RHN Satellite 3.5 Beta How reproducible: Always Steps to Reproduce: 1. See description 2. 3. Actual results: If you try to follow the instructions, you find that the features referenced aren't there. Expected results: It shouldn't be documented. Additional info:
Excellent catch, Max. I'm claiming, bumping the version and aligning to the 3.6 documentation tracking bug.
Reassigning to Robin to confirm, as Max suggested.
Setting to NEEDINFO. Robin, can you confirm that the Certificate Administrator role introduced in 350 is internal to RHN only and not available to customers? Thanks
That is correct - this feature is internal-only (for now). See: http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/rhn/docs/protospec/cert-creation-tool.txt?rev=HEAD;content-type=text%2Fplain;cvsroot=RHN And BZ #107039
OK, I'm reclaiming this bug and will remove the offending text. Specifically, the sections of the Entitlements chapter of the Sat. install guide need removal/rewriting. I will also ensure the Satellite 3.6 release notes contain no mention of this internal feature.
OK, these changes have been made and will be visible in the 3.6 versions of the Satellite Release Notes and Installation Guide. First, references to the interface have been removed from both the Major Enhancements and Documentation sections of the release notes. Second, its references have been removed from the Entitlements chapter (5) in both the introductory text and by deleting the entire Generating the Certificate section (formely 5.2). Finally, I removed the Finding the Entitlement Certificate Interface section (formerly 8.6.1.3) from the Maintenance chapter. Setting to ON_DEV.
QA push. {ON_DEV,QA_READY} --> ON_QA
Shifting this from the 3.6 hosted doc tracking bug (rhn360docs) to the 3.6 sat tracking bug (rhn360satdocs) to reflect the timeline in which this change will appear.
Docs review done. Rel notes review done. Golden --> PROD_READY!
docs complete
Mass move from PROD_READY to CLOSED:CURRENTRELEASE