Hi Gianluca,

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?

Thanks,
Martin


On Thu, Oct 20, 2022 at 10:49 AM Gianluca Amato <gianluca.amato...@gmail.com>
wrote:

> 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":
>
> ----
> bootloader:
>   default: ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64)
>   entries:
>     ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64):
>       index: 0
>       kernel:
> /boot//ovirt-node-ng-4.5.1-0.20220623.0+1/vmlinuz-4.18.0-394.el8.x86_64
>       args: crashkernel=auto resume=/dev/mapper/onn_ovirt--clai1-swap
> rd.lvm.lv=onn_ovirt-clai1/ovirt-node-ng-4.5.1-0.20220623.0+1 
> rd.lvm.lv=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
>       initrd:
> /boot//ovirt-node-ng-4.5.1-0.20220623.0+1/initramfs-4.18.0-394.el8.x86_64.img
>       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
> layers:
>   ovirt-node-ng-4.5.1-0.20220623.0:
>     ovirt-node-ng-4.5.1-0.20220623.0+1
> 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@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/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2VS5Q56URFSVO2DQGRAGQ4XCI6Q7W7W/
>


-- 
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
_______________________________________________
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/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/A4WLHY6Q7K6JNA6U6DTUSFTFAR3ZRXDQ/

Reply via email to