11:49 a.m.
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
10:16 a.m.
New subject: After failed upgrade from 4.5.1 to 4.5.3, upgrades do not show up anymore
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.74(a)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(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:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2VS5Q56URF...
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
11:16 a.m.
New subject: After failed upgrade from 4.5.1 to 4.5.3, upgrades do not show up anymore
Hi Martin,
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
./ovirt-engine/engine.log file.
Upgrade was attempted on Oct 19, 11:22 PM, and the relevant file should be
ovirt-host-mgmt-ansible-20221019232347-ovirt-clai1.unich.it-1079f2e5-c2f2-42c1-b738-ed85bdb79b5c.log.
Later, I reinstalled the current version of oVirt node, and the logs should
be in
ovirt-host-deploy-ansible-20221020094242-ovirt-clai1.unich.it-b784707f-205d-4878-846d-f1bcaa1772be.log.
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.
Thank,
--gianluca
On Fri, Oct 21, 2022 at 9:16 AM Martin Perina <mperina(a)redhat.com> wrote:
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.74(a)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(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:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2VS5Q56URF...
>
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
12:44 p.m.
At the end I proceeded as follows:
1) I manually installed the package ovirt-node-ng-image-update-placeholder version 4.5.1
on the host; with this change alone, the manager engine began detecting available
updates;
2) before proceeding with the updates, I had to fix my host setup. The error "Local
storage domains were found on the same filesystem as /" was due to the fact that I
was mounting storage at the path /data/normal, while the entire /data path should be on a
different filesystem than root.
After making these changes, upgrade went smoothly to 4.5.3.2
Now I have problems upgrading to 4.5.4, but I think this is a different problem.
717
days inactive
765
days old
3 comments
2 participants
participants (2)
-
Gianluca Amato -
Martin Perina