Description of problem:
After performing an all-in-one install, RHEV will not start virtual machines due to a missing path. The exact error message RHEV-M gives is:
VM r7 is down. Exit message: internal error process exited while
connecting to monitor: ((null):25215): Spice-Warning **:
reds.c:3255:reds_init_ssl: Could not load certificates from
/etc/pki/libvirt-spice/server-cert.pem failed to initialize spice
The 'libvirt-spice' directory does not exist, however creating a symlink works around the issue:
[root@work2 pki]# pwd
[root@work2 pki]# ls -tlrh
drwx------. 2 root root 4.0K Aug 15 2013 rsyslog
drwxr-xr-x. 2 root root 4.0K Jan 31 14:40 rpm-gpg
drwxr-xr-x. 4 root root 4.0K Jan 31 15:07 ca-trust
drwxr-xr-x. 2 root root 4.0K Jan 31 15:07 java
drwxr-xr-x. 5 root root 4.0K Jan 31 15:07 tls
drwxr-xr-x. 2 root root 4.0K Jan 31 15:45 product
drwxr-xr-x. 2 root root 4.0K Feb 3 16:25 entitlement
drwxr-xr-x. 5 vdsm kvm 4.0K Feb 13 09:01 vdsm
drwxr-xr-x. 6 ovirt ovirt 4.0K Feb 19 16:04 ovirt-engine
drwxr-xr-x. 3 root root 4.0K Feb 19 16:04 libvirt
drwxr-xr-x. 6 root root 4.0K Feb 19 16:04 CA
lrwxrwxrwx. 1 root root 19 Feb 20 11:42 libvirt-spice -> vdsm/libvirt-spice/
drwxr-xr-x. 2 root root 4.0K Feb 20 13:40 nssdb
Version-Release number of selected component (if applicable):
The all-in-one install is shipped by Red Hat, however longer term it appears a single-node hosted install would be a more elegant path. That said, the convenience and simplicity of the all-in-one install is valuable.
it seems as if there is now component for the All-In-One image. If we ship it we should have a component, shouldn't we?
the rpm is part of setup package iirc.
This is strange!
vdsm should use /etc/pki/vdsm/libvirt-spice/server-cert.pem
Dan, any thought why it looks at the wrong place?
its declared in /etc/libvirt/qemu.conf (spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice")
Dave, can you check if the value exists there after fresh allinone installation ? it also part of the libvirt_configure when we set qemu.conf values.
Dave, please attach your complete /etc/libvirt/qemu.conf and /etc/vdsm/vdsm.conf.
Have you disabled ssl at one time?
Created attachment 867656 [details]
Created attachment 867657 [details]
On a fresh install, the spice_tls_x509_cert_dir variable matches your output.
Attached. I have not disabled SSL.
Some additional information. I did a fresh install (allinone / rhevm-setup) on a new host and couldn't replicate the problem. On the host exibiting the problem, I'd initially tried an unsuccessful self-hosted install via 'hosted-engine --deply' before trying allinone/rhevm-setup.
Didi, I think you've seen something similar this week. Can you take a look?
(In reply to Dave Kline from comment #8)
> On a fresh install, the spice_tls_x509_cert_dir variable matches your output.
> Attached. I have not disabled SSL.
> Some additional information. I did a fresh install (allinone / rhevm-setup)
> on a new host and couldn't replicate the problem. On the host exibiting the
> problem, I'd initially tried an unsuccessful self-hosted install via
> 'hosted-engine --deply' before trying allinone/rhevm-setup.
(In reply to Sandro Bonazzola from comment #9)
> Didi, I think you've seen something similar this week. Can you take a look?
Sorry, don't remember the exact details. I am pretty certain that the failed hosted-engine deploy left the system in a "bad" state (as described above) which is not solved by merely re-configuring system components for vdsm (libvirt, spice etc) - because vdsm-tool checks and thinks it already did the required configuration and does not do the required changes.
The real bug is that hosted-engine/all-in-one/vdsm do not provide cleanup scripts, nor manage to clean up previous attempts during setup.
I currently suggest to close this as duplicate of bug #1034634 .
Dave - can you please verify that running a recent (changed merged upstream at end of last week) hosted-engine --deploy, then killing it in the middle (e.g. when it asks if the OS was successfully installed on the VM reply 'Cancel' or whatever it's called), then trying engine-setup all-in-one does work?
Happy to try again with the latest bits. I'll need a few days due to travel and obligations however.
(In reply to Dave Kline from comment #11)
> Happy to try again with the latest bits. I'll need a few days due to travel
> and obligations however.
Very well. I am currently closing this bug. Please reopen if still relevant. Thanks!
*** This bug has been marked as a duplicate of bug 1034634 ***