Is a change in /etc/pki/vdsm/cert/cacert.pem on the nodes going to
disrupt the communications between nodes and the engine?
The procedure I followed blew away all of /etc/pki/vdsm on each node. I
saved the old one.
Jason
On 8/4/23 14:38, Jason P. Thomas wrote:
I restarted vdsmd and
cen,
apache.p12 was the first snowflake in this avalanche. I did find
something showing how to generate a new one and install it. That
actually allowed me to access the engine web interface again. Kinda
useless since the engine can't talk to any of the nodes though. Haha.
Thanks for the
cen,
apache.p12 was the first snowflake in this avalanche. I did find
something showing how to generate a new one and install it. That
actually allowed me to access the engine web interface again. Kinda
useless since the engine can't talk to any of the nodes though. Haha.
Thanks for the
Hi,
I went through a similar ordeal half a year ago and forgot all the exact
procedures already but for me, in the end after following all the guides
and replacing the "standard" certs
it was either engine.p12 or apache.p12 keystore that also had outdated
certs (apparently mTLS is being
Is a change in /etc/pki/vdsm/cert/cacert.pem on the nodes going to
disrupt the communications between nodes and the engine?
The procedure I followed blew away all of /etc/pki/vdsm on each node. I
saved the old one.
Jason
On 8/4/23 14:38, Jason P. Thomas wrote:
I restarted vdsmd and
I restarted vdsmd and libvirtd after the cert update on each host.
Jason
On 8/4/23 14:34, Derek Atkins wrote:
Did you restart vdsm after updating the certs?
-derek
On Fri, August 4, 2023 2:12 pm, Jason P. Thomas wrote:
I updated the VDSM certs on the hosts and the apache cert on the
engine.
Did you restart vdsm after updating the certs?
-derek
On Fri, August 4, 2023 2:12 pm, Jason P. Thomas wrote:
> I updated the VDSM certs on the hosts and the apache cert on the
> engine. I'm guessing something is wrong with however the engine
> interacts with vdsm, I just don't know exactly what
I updated the VDSM certs on the hosts and the apache cert on the
engine. I'm guessing something is wrong with however the engine
interacts with vdsm, I just don't know exactly what to do about it.
Jason
On 8/4/23 14:00, Derek Atkins wrote:
Sounds like the Host Certs need to be updated.. Or
Sounds like the Host Certs need to be updated.. Or possibly even the
Engine CA Cert.
-derek
On Fri, August 4, 2023 1:45 pm, Jason P. Thomas wrote:
> Konstantin,
> Right after I sent the email I got the engine running. The
> libvirt-spice certs had incorrect ownership. It still is not
Konstantin,
Right after I sent the email I got the engine running. The
libvirt-spice certs had incorrect ownership. It still is not connecting
to anything. Error in Events on the Engine is now: "VDSM
command Get Host Capabilities failed: General SSLEngine
problem"
So status right now
> Now the engine won't start at all and I'm afraid I'm one power outage
> away from complete disaster. I need to keep the old location up and
> functioning for another 4-6 months, so any insights would be greatly
> appreciated.
Hi,
'engine won't start at all' can mean two things:
1) OS
11 matches
Mail list logo
