Do you think it is the case I submit an issue on github ? It does not seem to
be already reported.
--gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
Thanks a lot Marco, it worked for me !!!
___
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
oVirt Code of Conduct:
Hi Gianluca,
I had the same problem.
The issue is with the updated ansible-core package (I am
running ansible-core-2.16.1-1.el8.x86_64) -- they have removed the
"include" directive in 2.16 (was deprecated already), and the upgrade
playbook is now failing.
I have modified the playbook
What happens if you place a node in maintenance and run yum update on the
node directly and reboot?
On Thu, Jan 4, 2024 at 7:22 AM Gianluca Amato
wrote:
> Hello,
> I am trying to update my oVirt installation to 4.5.5, but while I had no
> problems upgrading the self-hosted ovirt-engine, I am
ADDENDUM:
OVN configured stays at No for hosts...
___
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
oVirt Code of Conduct:
Concerning the keymap issue:
setting ClientModeConsoleDefault to spice will evade the problem by using the
keymap configured on the remote system aka the virtual machine
# engine-config -s ClientModeConsoleDefault=spice
otherwise VNC is used as standard and will only function properly if the
I have made progress on the network issue and it turns out, there is something
missing from the dependencies. It's a python library that redefines the
behavior of a function. This has the effect of not producing an interpreter
error when missing...
I got the networks to function by installing
7 matches
Mail list logo