Bug 789705

Summary: unable to start vm's when using spice with ssl
Product: [Retired] oVirt Reporter: Ohad Levy <ohadlevy>
Component: vdsmAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, bazulay, iheim, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-12 08:57:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ohad Levy 2012-02-12 13:10:35 UTC
Description of problem:

when installing recent ovirt with ssl enabled, a new vm which is using spice is unable to start.

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

vdsm-4.9.3.2-0.fc16.x86_64
spice-server-0.10.1-1.fc16.x86_64
How reproducible:
100%


Steps to Reproduce:
1.start a vm
2.wait for failure
3.
  
Actual results:

reds_init_ssl: Could not load certificates from /etc/pki/libvirt-spice/server-cert.pem


Expected results:


Additional info:

a simple link from /etc/pki/libvirt-spice to /etc/pki/vdsm/libvirt-spice/ solves the issue.

Comment 1 Yaniv Kaul 2012-02-12 13:19:27 UTC
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=773371 ?

Comment 2 Ohad Levy 2012-02-13 07:24:34 UTC
I see, it does seem like a dup, the only difference, is that this is a new host, with vdsm installed prior to engine adding it, so, imho, maybe the engine should reconfigure vdsm in case that you add a new host?

Comment 3 Yaniv Kaul 2012-02-13 07:43:57 UTC
(In reply to comment #2)
> I see, it does seem like a dup, the only difference, is that this is a new
> host, with vdsm installed prior to engine adding it, so, imho, maybe the engine
> should reconfigure vdsm in case that you add a new host?

Perhaps, but this is a different bug (or RFE actually).

Comment 4 Itamar Heim 2013-03-12 08:57:09 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.