In the Events view in webadmin I see many messages of the type "Update of
host ovirt-clai1. ......". The last message is "Update of host ovirt-clai1.
Stop services." followed by two consecutive error message "Failed to
upgrade Host ovirt-clai1 (User: admin(a)internal-authz)."
I have extracted the files in the /var/log directory of the management
engine which are related to the clai1 server. They are attached to this
email. There are a bunch of files coming from the
./ovirt-engine/host-deploy/ directory, in addition to the
Upgrade was attempted on Oct 19, 11:22 PM, and the relevant file should be
Later, I reinstalled the current version of oVirt node, and the logs should
Reading these logs, I see the following error message:
*Local storage domains were found on the same filesystem as / ! Please
migrate the data to a new LV before upgrading, or you will lose the VMs*
This is weird, since my VMs are in a completely different disk and LVM
volume group w.r.t. the root partition. In any case, this does not explain
while I cannot attempt the upgrade anymore.
On Fri, Oct 21, 2022 at 9:16 AM Martin Perina <mperina(a)redhat.com> wrote:
In the Events view in webadmin there should be a message announcing that
host upgrade failed and more information could be found within specific log
file on oVirt Engine machine. Could you please share this log file?
On Thu, Oct 20, 2022 at 10:49 AM Gianluca Amato <
> Hi all,
> I recently tried to upgrade an oVirt node from 4.5.1 to 4.5.3. The
> upgrade failed (I have no idea idea why... how can I access the
> installation logs?). The node is still working fine running the old 4.5.1
> release, but now the oVirt web console says that it is up to date and it
> does not let me retry the upgrade. However, I am still on version 4.5.1, as
> witnessed by the result of "nodectl info":
> default: ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64)
> ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64):
> index: 0
> args: crashkernel=auto resume=/dev/mapper/onn_ovirt--clai1-swap
> rhgb quiet boot=UUID=9d44cf2a-38bb-477d-b542-4bfc30463d1f rootflags=discard
> img.bootid=ovirt-node-ng-4.5.1-0.20220623.0+1 intel_iommu=on
> modprobe.blacklist=nouveau transparent_hugepage=never hugepagesz=1G
> hugepages=256 default_hugepagesz=1G
> root: /dev/onn_ovirt-clai1/ovirt-node-ng-4.5.1-0.20220623.0+1
> title: ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64)
> blsid: ovirt-node-ng-4.5.1-0.20220623.0+1-4.18.0-394.el8.x86_64
> current_layer: ovirt-node-ng-4.5.1-0.20220623.0+1
> Comparing the situation with other hosts in the same data center, it
> seems that the problem is that the package
> ovirt-node-ng-image-update-placeholder is not installed anymore, hence "dnf
> upgrade" has nothing to do. My idea was to manually download and install
> the 4.5.1 version of ovirt-node-ng-image-update-placeholder and attempt
> installation again.
> Is it a correct way to proceed ?
> Thanks for any help.
> --gianluca amato
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> List Archives:
Manager, Software Engineering
Red Hat Czech s.r.o.