Bug 1481249 - [Docs][4.1] Missing step in the RHV Administration Guide
Summary: [Docs][4.1] Missing step in the RHV Administration Guide
Keywords:
Status: CLOSED DUPLICATE of bug 1483371
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-14 12:36 UTC by Jaroslav Spanko
Modified: 2020-09-10 11:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-29 00:59:25 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)

Description Jaroslav Spanko 2017-08-14 12:36:44 UTC
Hi

There is missing one step in section

D.2. Replacing the Red Hat Virtualization Manager Apache SSL Certificate
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/appe-red_hat_enterprise_virtualization_and_ssl#Replacing_the_Manager_SSL_Certificate

As in Procedure D.1 step 3
~~~
# openssl pkcs12 -in /etc/pki/ovirt-engine/keys/apache.p12 -nocerts -nodes > /tmp/apache.key
# openssl pkcs12 -in /etc/pki/ovirt-engine/keys/apache.p12 -nokeys > /tmp/apache.cer
~~~
we are using the generated /tmp/apache.key and /tmp/apache.cer

In the Procedure D.2 step 5 is ok
~~~
5. Copy the private key to the required location:
# cp /tmp/apache.key /etc/pki/ovirt-engine/keys/apache.key.nopass
~~~

but there is missing one step - copy the certificate which was generated with the key
~~~
# cp /tmp/apache.cer /etc/pki/ovirt-engine/certs/apache.cer
~~~

Thank you

Comment 1 Lucy Bopf 2017-08-29 00:54:21 UTC
Didi, can you take a look at this request, and confirm whether an extra step is required? I know you did a thorough review of this procedure with Emma in bug 1416232 recently.

Comment 2 Lucy Bopf 2017-08-29 00:59:25 UTC
Actually, on further bug triage, I see there is already discussion about this issue in bug 1483371. I'm closing this one as a duplicate, so we can keep the conversation in one place.

*** This bug has been marked as a duplicate of bug 1483371 ***


Note You need to log in before you can comment on or make changes to this bug.