Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 705322

Summary: Can't start VM with spice console due to /etc/pki/vdsm/libvirt-spice/ rights
Product: Red Hat Enterprise Linux 6 Reporter: Pavel Stehlik <pstehlik>
Component: vdsmAssignee: Yotam Oron <yoron>
Status: CLOSED ERRATA QA Contact: Pavel Stehlik <pstehlik>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.1CC: abaron, bazulay, danken, iheim, ilvovsky, mburns, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.9-68.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 07:18:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pavel Stehlik 2011-05-17 11:30:15 UTC
Created attachment 499314 [details]
libvirt.log

Description of problem:
 When trying start VM on the rhev-hypervisor-6.1-20110510.1.el6 , then the Audit log shows the same as libvirtd.log: 
 internal error process exited while connecting to monitor: do_spice_init: starting 0.8.0
reds_init_ssl: Could not use private key file

Full err msg in Add info.


Workaround could be used:
chown vdsm:kvm -R /etc/pki/vdsm/libvirt-spice/


Version-Release number of selected component (if applicable):
rhev-hypervisor-6.1-20110510.1.el6
vdsm-4.9-63
libvirt-0.8.7-18

How reproducible:
100%

Steps to Reproduce:
1. have VM with Spice console
2. try to run this VM on this rhev-h
3.
  
Actual results:


Expected results:


Additional info:
10:02:26.097: 9865: warning : qemudStartVMDaemon:3336 : Executing /usr/libexec/qemu-kvm
10:02:26.099: 9865: warning : qemudStartVMDaemon:3346 : Executing done /usr/libexec/qemu-kvm
10:02:29.106: 9865: error : qemuMonitorOpenUnix:288 : monitor socket did not show up.: Connection refused
10:02:29.107: 9865: error : qemudWaitForMonitor:2314 : internal error process exited while connecting to monitor: do_spice_init: starting 0.8.0
reds_init_ssl: Could not use private key file

Comment 2 Mike Burns 2011-05-17 12:23:28 UTC
/etc/pki/vdsm/libvirt-spice is created during the host approval process with rhevm.  This flow is specific to the vdsm component and not part of ovirt-node.

Comment 4 Dan Kenigsberg 2011-05-17 15:53:31 UTC
Pavel, what's

ls -lR /etc/pki/vdsm/libvirt-spice

before the workaround chmod?

Comment 8 Dan Kenigsberg 2011-05-19 08:10:42 UTC
Ok, that's clearly my bug, shutil.copy2 does not copy file ownership.

http://gerrit.usersys.redhat.com/#change,439

Comment 11 errata-xmlrpc 2011-12-06 07:18:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHEA-2011-1782.html