Trying Jayme's solution seems to have worked in my case:
- Put host into maintenance mode
- Manually run "dnf update" on the host to update ovirt-node-ng-image-update to
4.5.5 from 4.5.4.
- Reboot host
- In Manager GUI, click "check for updates" once again on the updated node,
which should clear
Just to throw in my two cents, I am attempting to update oVirt Node on our
cluster from 4.5.4 to 4.5.5, appears to run, but once the system reboots they
go into recovery mode and will not boot. Even trying a fresh install of oVirt
Node 4.5.5 does the same on our systems, so hoping to find a reso
To add a "me too" this same problem bit us when updating our 4.5 cluster today.
It will surely hit anyone once their hosted engine updates ansible to 2.16.2,
which breaks the host upgrades until you patch the specific file mentioned by
Marco.
In our case, after we'd upgraded the hosted-engine V
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: https://www.ovirt.org/privac
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:
https://www.ovirt.org/community/a
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
(/usr/share/
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 not
7 matches
Mail list logo
