Back to bug 1321381

Who When What Removed Added
Sandro Bonazzola 2016-04-11 06:57:50 UTC Assignee sbonazzo stirabos
Sandro Bonazzola 2016-04-11 09:58:48 UTC CC sbonazzo
See Also https://bugzilla.redhat.com/show_bug.cgi?id=1146710
Sandro Bonazzola 2016-04-11 10:00:32 UTC Target Milestone --- ovirt-4.1.0
Simone Tiraboschi 2016-04-11 12:54:46 UTC CC nashok
Flags needinfo?(nashok)
Simone Tiraboschi 2016-04-11 14:47:21 UTC Summary Addition of second host fails if the RHEV-M portal is using custom Apache certificate hosted-engine-setup trusts also the system defined CA certs while the oVirt python SDK ignores them
Simone Tiraboschi 2016-04-11 14:48:07 UTC Blocks 1146710
See Also https://bugzilla.redhat.com/show_bug.cgi?id=1146710
Juan Hernández 2016-04-11 15:00:46 UTC CC juan.hernandez
Simone Tiraboschi 2016-04-12 14:56:47 UTC Depends On 1326386
Sandro Bonazzola 2016-04-13 06:45:57 UTC Link ID oVirt gerrit 56051
Status NEW POST
Target Milestone ovirt-4.1.0 ovirt-4.0.0
nijin ashok 2016-04-18 16:44:49 UTC Flags needinfo?(nashok)
nijin ashok 2016-04-18 17:42:20 UTC Link ID Red Hat Knowledge Base (Solution) 2262081
Simone Tiraboschi 2016-04-29 15:57:06 UTC Link ID oVirt gerrit 56853
Status POST MODIFIED
Simone Tiraboschi 2016-05-02 17:02:50 UTC Doc Text The user can replace the apache cert,
if so hosted-engine-setup cannot simply rely on the internal CA cert but has to ask to the user to provide the right CA cert or proceed in insecure mode.
hosted-engine-setup was trusting also the system defined CA certs while the oVirt python SDK ignores them so, if the user replaced the apache cert with trusted by the host, hosted-engine-setup was skipping the cert question but was failing trying to use the SDK with it.
Simone Tiraboschi 2016-05-04 14:32:21 UTC Blocks 1330523
meital avital 2016-05-10 11:16:10 UTC QA Contact mavital alukiano
Sandro Bonazzola 2016-05-10 11:28:15 UTC Target Milestone ovirt-4.0.0-alpha ovirt-3.6.6
Sandro Bonazzola 2016-05-10 11:34:57 UTC Blocks 1334702
Keywords ZStream
Target Milestone ovirt-3.6.6 ovirt-4.0.0-alpha
Blocks 1330523
Sandro Bonazzola 2016-05-19 11:16:43 UTC Status MODIFIED ON_QA
Target Release --- 4.0.0
Target Milestone ovirt-4.0.0-alpha ovirt-4.0.0-beta
Artyom 2016-05-22 15:16:11 UTC Keywords Triaged
Status ON_QA VERIFIED
Megan Lewis 2016-08-19 05:58:41 UTC CC melewis
Doc Text The user can replace the apache cert,
if so hosted-engine-setup cannot simply rely on the internal CA cert but has to ask to the user to provide the right CA cert or proceed in insecure mode.
hosted-engine-setup was trusting also the system defined CA certs while the oVirt python SDK ignores them so, if the user replaced the apache cert with trusted by the host, hosted-engine-setup was skipping the cert question but was failing trying to use the SDK with it.
Previously, when a user replaced the apache certificate hosted-engine-setup trusted the system defined CA certificate and skipped the certificate question when deploying a second host. This meant that the deployment of the second host failed because the certificate was not actually trusted. Now, hosted-engine-setup no longer skips the certificate question and prompts the user for the correct CA certificate or asks to proceed in insecure mode.
errata-xmlrpc 2016-08-23 01:06:15 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-08-23 21:00:39 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-08-23 17:00:39 UTC

Back to bug 1321381