Hi,
we are experiencing a weird issue with our Ovirt setup. We have two
physical hosts (DC1 and DC2) and mounted Lenovo NAS storage for all VM data.
They are connected via a managed network switch.
What happens is that if switch goes down for whatever reason (firmware
update etc), physical h
x27;t have any serious uptime requirements so
this seems like the easiest and safest way forward.
Best regards,
cen
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovir
user with password (perhaps with restricted SSH) to perform a console login?
Best regards, cen
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
Excellent news!
Having good terraform support is crucial in this day and age. Is there a
minimum oVirt version that is needed by the provider?
Best regards, cen
On 08/06/2022 11:44, Janos Bonic wrote:
Hey everyone,
You may still remember the email we sent last year about reworking the
enroll host1 first, then run the engine-setup and then do
the host2.
It doesn't really make sense to run engine-setup again after enrolling
host2 though, so that would make it 1 (host1), 2, 1 (host2), skip 2. Or
does it?
Best regards, cen
___
Hi
Our VDSM certs have expired, both hosts are unassigned and can't be put
into maintenance from UI.
vdsm-client is not working, times out even with --insecure flag. Does
host and port need to be specified when run locally or should defaults work?
Error in console events is: Get Host Capab
fferent CA but that didn't make a difference.
Best regards
On 10/03/2023 05:13, cen wrote:
Hi
Our VDSM certs have expired, both hosts are unassigned and can't be
put into maintenance from UI.
vdsm-client is not working, times out even with --insecure flag. Does
host and port need
Yes, that is the exact guide I followed.
I can now actually use vdsm-client on each host after cert swap but
ovirt-engine still can't establish connection.
I had to manually generate the apache certs to get into the UI console
at the beginning and that was successful.
Is there a specific
I did not but I finally found the issue, what a ride this was..
After updating keys/engine.p12 hosts finally showed up. While there are
probably more certs outdated and some parts not working now I can
finally do regular enrollments.
I was right all along, the auth cert was causing the proble
S is being used!).
Updating these keystores is not documented anywhere. No idea if you are
in the same situation but wanted to throw this out there.
Best regards, cen
On 4. 08. 23 20:12, Jason P. Thomas wrote:
I updated the VDSM certs on the hosts and the apache cert on the
engine. I'm gue
10 matches
Mail list logo
