Cannot update oVirt Node
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 able to upgrade any node (running oVirt Node NG 4.5.4 or older). I just click Upgrade in the oVirt Manager, and I get a bunch of events telling me that everything was OK and the upgrade succeeded, but in reality nothing happened on the nodes: the result of "nodectl info" before and after the upgrade process is exactly the same. I gave a look to the engine.log and to the relevant ovirt-host-mgmt-ansible log in the ovirt-engine VM, but I cannot find the problem. Do any of you have any ideas ? I am attaching some relevant files. Note that the upgrade consistently fails in the same way on other nodes, which have other versions of oVirt Node NG (always in the 4.5 family). Thanks for your help --gianluca
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 <gianluca.amato.74@gmail.com> 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 able to upgrade any node (running oVirt Node NG 4.5.4 or older). I just click Upgrade in the oVirt Manager, and I get a bunch of events telling me that everything was OK and the upgrade succeeded, but in reality nothing happened on the nodes: the result of "nodectl info" before and after the upgrade process is exactly the same.
I gave a look to the engine.log and to the relevant ovirt-host-mgmt-ansible log in the ovirt-engine VM, but I cannot find the problem. Do any of you have any ideas ? I am attaching some relevant files.
Note that the upgrade consistently fails in the same way on other nodes, which have other versions of oVirt Node NG (always in the 4.5 family).
Thanks for your help --gianluca
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OVJVQ5CD6J6SMD...
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/ovirt-engine/ansible-runner-service-project/project/ovirt-host-upgrade.yml) by replacing the "include" directive with "import_tasks" -- not sure if it is the proper solution, but it worked for me. --- ovirt-host-upgrade.yml.original 2023-12-27 18:40:10.425430841 +0000 +++ ovirt-host-upgrade.yml 2023-12-27 18:41:08.283251148 +0000 @@ -10,7 +10,7 @@ pre_tasks: - include_vars: ovirt_host_upgrade_vars.yml - - include: ovirt-host-yum-conf.yml + - import_tasks: ovirt-host-yum-conf.yml - block: # Check if certificates need re-enrollment: @@ -74,5 +74,5 @@ - name: ovirt-host-deploy-vnc-certificates post_tasks: - - include: ovirt-host-remove-yum-conf.yml - - include: ovirt-host-reconfigure-ovn.yml + - import_tasks: ovirt-host-remove-yum-conf.yml + - import_tasks: ovirt-host-reconfigure-ovn.yml Let me know if this worked for you as well Regards, Marco On Thu, 4 Jan 2024 at 11:22, Gianluca Amato <gianluca.amato.74@gmail.com> 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 able to upgrade any node (running oVirt Node NG 4.5.4 or older). I just click Upgrade in the oVirt Manager, and I get a bunch of events telling me that everything was OK and the upgrade succeeded, but in reality nothing happened on the nodes: the result of "nodectl info" before and after the upgrade process is exactly the same.
I gave a look to the engine.log and to the relevant ovirt-host-mgmt-ansible log in the ovirt-engine VM, but I cannot find the problem. Do any of you have any ideas ? I am attaching some relevant files.
Note that the upgrade consistently fails in the same way on other nodes, which have other versions of oVirt Node NG (always in the 4.5 family).
Thanks for your help --gianluca
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OVJVQ5CD6J6SMD...
Do you think it is the case I submit an issue on github ? It does not seem to be already reported. --gianluca
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 VM, we went through and upgraded all of the nodes one-by-one including reboots, and then realized after we thought we were done that none of the packages on the nodes get upgraded at all. From the UI side of things, you'd think it had worked (hosts goes maintenance, says updating but quickly goes to rebooting, comes back up and activates showing no updates needed until the next time you issue "check for upgrades" against it).
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 resolution.
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 the notification that updates are available.
participants (5)
-
Gianluca Amato -
Jayme -
Levi Wilbert -
Marco Fais -
Mark R