Section: "Replacing the RHEVM SSL Certificate" (D1) should be updated and moved to Tech Guide .
I. The section should be updated with:
1) be persistent with the bold font. If you decide to mark some files as bold, mark all the files to be updated as bold, or do not use bold at all. otherwise confusing.
2) current solution is incomplete, since it does not cover the tools that needs to be updated, once the certificate is updated and it does not cover the scenarios when the apache-ca.pem is only an intermediate certificate, and not root CA. It will be verified by browser, but not by our tools.
More details and GSS documentation are in this bug:
II. IMO, this section should be in the Tech Guide and not the Admin Guide.
I would say, this is an advanced option and not part of the default RHEV deployment. However, I would leave this part open to discussion.
Changing status back to 'New' until re-assignment.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to
- 3.6.1 if severity >= high
- 4.0 if severity < high
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.
It appears that the inconsistent file marking has been resolved in subsequent versions of this content, and the second item depends on an unresolved engineering bug. I don't think there is anything left to address in this bug at this time.
In addition, the section mentioned in this bug is now being updated and technically reviewed for 4.0 in bug 1373046 and bug 1336845.
*** This bug has been marked as a duplicate of bug 1336845 ***