Bug 1734360

Summary:	When vdsm spice CA file checking may fail if spice ca directory don't exists
Product:	[oVirt] ovirt-engine	Reporter:	Ondra Machacek <omachace>
Component:	ovirt-host-deploy-ansible	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavol Brilla <pbrilla>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	future	CC:	lleistne, mperina
Target Milestone:	ovirt-4.3.6	Flags:	pm-rhel: ovirt-4.3+
Target Release:	4.3.6.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.6.1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-26 19:43:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ondra Machacek 2019-07-30 10:59:42 UTC

Description of problem:
https://github.com/oVirt/ovirt-engine/blob/825a709e765cb1b7f3a72fcb4804edd74207f497/packaging/playbooks/roles/ovirt-host-enroll-certificate/tasks/vdsm.yml#L7

If the spice ca directory don't exist the task above fails.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3

How reproducible:
always

Steps to Reproduce:
1. Make sure the ca directory don't exist and run enroll certificate command.

Actual results:
fail

Expected results:
succeed

Additional info:

Comment 1 Pavol Brilla 2019-09-10 11:23:02 UTC

host_mixed_3# mv libvirt-spice libvirt-spice2

Enroll certificate from engine:
Sep 10, 2019, 1:18:03 PM Enrolling certificate for host host_mixed_3 was completed successfully (User: admin@internal-authz).
Sep 10, 2019, 1:17:20 PM Enrolling certificate for host host_mixed_3 was started (User: admin@internal-authz).


# yum list ovirt-engine
Installed Packages
ovirt-engine.noarch                                      4.3.6.5-0.1.el7

Comment 2 Sandro Bonazzola 2019-09-26 19:43:34 UTC

This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.