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.
Description of problem:
Can't create VM. due to Could not load certificates from /etc/pki/libvirt-spice/server-cert.pem
Steps to Reproduce:
1. create VM
2.
3.
Vdsm.log:
[root@navy-vds1 ~]# less /var/log/vdsm/vdsm.log
Thread-6550::ERROR::2011-03-14 14:23:36,330::vm::643::vm.Vm::(_startUnderlyingVm) vmId=`d7138c82-b646-4673-a9eb-bc9eca8c6b8e`::Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 613, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/libvirtvm.py", line 782, in _run
self._connection.createXML(domxml, flags),
File "/usr/share/vdsm/libvirtconnection.py", line 72, in wrapper
raise e
libvirtError: internal error process exited while connecting to monitor: do_spice_init: starting 0.7.2
reds_init_ssl: Could not load certificates from /etc/pki/libvirt-spice/server-cert.pem
Thread-6550::DEBUG::2011-03-14 14:23:36,333::vm::1776::vm.Vm::(setDownStatus) vmId=`d7138c82-b646-4673-a9eb-bc9eca8c6b8e`::Changed state to Down: internal error process exited wh
ile connecting to monitor: do_spice_init: starting 0.7.2
reds_init_ssl: Could not load certificates from /etc/pki/libvirt-spice/server-cert.pem
libvirtd.conf:
listen_addr="0" # by vdsm
unix_sock_group="kvm" # by vdsm
unix_sock_rw_perms="0770" # by vdsm
auth_unix_rw="sasl" # by vdsm
save_image_format="lzop" # by vdsm
log_outputs="1:file:/var/log/libvirtd.log" # by vdsm
log_filters="1:util 3:json 1:libvirt 1:qemu 1:remote" # by vdsm
auth_tcp="none" # by vdsm
listen_tcp=1 # by vdsm
listen_tls=0 # by vdsm
missing the following values:
ca_file="/etc/pki/vdsm/certs/cacert.pem"
cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
But do the files at /etc/pki/libvirt-spice/server-cert.pem and /etc/pki/vdsm/certs/cacert.pem etc actually exist?
I think this can happen if you manually changed vdsm to use ssl without generating the keys.
I guess it makes sense for vdsm to check their configuration and existence on service vdsmd start.
/etc/pki/libvirt-spice/server-cert.pem and /etc/pki/vdsm/certs/cacert.pem files does exist!
I did not change any default vdsm settings
This bug is very hard to reproduce because there is no pre-requirements
After talking to Yotam i would like to clear my bug description.
The bug is:
vdsm does not fully configure libvirtd.conf the following lines are missing:
ca_file="/etc/pki/vdsm/certs/cacert.pem"
cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
Manually adding these line makes vdsm works great!
From reading the code, I assume that this can happen if the vdsm is started before the installation process is over.
The vdsm will not re-insert values into libvirtd.conf if it already did so, so subsequent installs won't change the (bad) values there.
I think this is the scenario that reproduces it:
- Install RHEL6 from scratch
- Install VDSM
- Start the vdsm
- Stop the vdsm
- Start installation
You should see the bug reproducing.
Opened a preintegration ticket.
Reproducible in vdsm-71
Problem is when configuration script is run before host is installed into rhev-m environment, libvirtd.conf is edited and due to certificates in /etc/pki/vdsm/ don't exist, following lines are appended
auth_tcp="none" # by vdsm
listen_tcp=1 # by vdsm
listen_tls=0 # by vdsm
After host is installed into rhev-m env., configuration script is not run again therefore it can't append paths to certs.
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
Description of problem: Can't create VM. due to Could not load certificates from /etc/pki/libvirt-spice/server-cert.pem Steps to Reproduce: 1. create VM 2. 3. Vdsm.log: [root@navy-vds1 ~]# less /var/log/vdsm/vdsm.log Thread-6550::ERROR::2011-03-14 14:23:36,330::vm::643::vm.Vm::(_startUnderlyingVm) vmId=`d7138c82-b646-4673-a9eb-bc9eca8c6b8e`::Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 613, in _startUnderlyingVm self._run() File "/usr/share/vdsm/libvirtvm.py", line 782, in _run self._connection.createXML(domxml, flags), File "/usr/share/vdsm/libvirtconnection.py", line 72, in wrapper raise e libvirtError: internal error process exited while connecting to monitor: do_spice_init: starting 0.7.2 reds_init_ssl: Could not load certificates from /etc/pki/libvirt-spice/server-cert.pem Thread-6550::DEBUG::2011-03-14 14:23:36,333::vm::1776::vm.Vm::(setDownStatus) vmId=`d7138c82-b646-4673-a9eb-bc9eca8c6b8e`::Changed state to Down: internal error process exited wh ile connecting to monitor: do_spice_init: starting 0.7.2 reds_init_ssl: Could not load certificates from /etc/pki/libvirt-spice/server-cert.pem