I am receiving the following error when attempting to update a Node manually that will not update through the administration portal: error: %pre(ovirt-node-ng-image-update-4.3.4-1.el7.noarch) scriptlet failed, exit status 1 Error in PREIN scriptlet in rpm package ovirt-node-ng-image-update-4.3.4-1.el7.noarch Software OS Version: RHEL - 7 - 6.1810.2.el7.centos OS Description: oVirt Node 4.3.3.1 Kernel Version: 3.10.0 - 957.10.1.el7.x86_64 KVM Version: 2.12.0 - 18.el7_6.3.1 LIBVIRT Version: libvirt-4.5.0-10.el7_6.6 VDSM Version: vdsm-4.30.13-1.el7 SPICE Version: 0.14.0 - 6.el7_6.1 GlusterFS Version: glusterfs-5.5-1.el7 CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.10.1-3.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Enabled Any advice?
On Wed, Jun 19, 2019 at 8:24 PM <zachary.winter@witsconsult.com> wrote:
I am receiving the following error when attempting to update a Node manually that will not update through the administration portal:
error: %pre(ovirt-node-ng-image-update-4.3.4-1.el7.noarch) scriptlet failed, exit status 1 Error in PREIN scriptlet in rpm package ovirt-node-ng-image-update-4.3.4-1.el7.noarch
Software OS Version: RHEL - 7 - 6.1810.2.el7.centos OS Description: oVirt Node 4.3.3.1 Kernel Version: 3.10.0 - 957.10.1.el7.x86_64 KVM Version: 2.12.0 - 18.el7_6.3.1 LIBVIRT Version: libvirt-4.5.0-10.el7_6.6 VDSM Version: vdsm-4.30.13-1.el7 SPICE Version: 0.14.0 - 6.el7_6.1 GlusterFS Version: glusterfs-5.5-1.el7 CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.10.1-3.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Enabled
Any advice?
Perhaps try to find out what exactly failed? IIRC you might find stuff in the logs (/var/log/ovirt-engine/host-deploy/*). If not, you can try checking 'yum history' and 'yum history info $ID', or if you want to try again: yum --rpmverbosity=debug update $PACKAGE (and either also '-y' and redirect to a file, or be prepared for a very long output in your terminal to copy/paste later). If you fail to get more info, 'rpm -q --scripts $PACKAGE' should should you the scripts it runs. In the case of ovirt-node-ng-update-image, the %pre script is [1]: ================================================================= local_sds=($(find / -xdev -name "__DIRECT_IO_TEST__")) if [ "$local_sds" ]; then echo "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" echo "See: https://bugzilla.redhat.com/show_bug.cgi?id=1550205#c3" echo "Storage domains were found in:" for sd in "${local_sds[@]}"; do echo -e "\t$(dirname $sd)" done exit 1 fi ================================================================= I can see mainly two ways in which it can fail - either the 'find' command failed for whatever reason (unintendedly), or local storage domains were found (and then the failure is intended) and you should get somewhere the output - did you? Best regards, [1] https://github.com/oVirt/ovirt-node-ng/blob/master/packaging/ovirt-node-ng.s... -- Didi
Regarding "Perhaps try to find out what exactly failed?", that is why I posted this thread. I am new to oVirt and trying to master it, but I do not know where to look. I have not found any documentation yet that tells me which logs to look at when, so please bear with me as I try to figure this out. Thank you however for your help. I ran the yum command you listed and got the debug output. I do in fact have a storage domain on the Node, and I am almost certain that is why it is failing. I suspect that removing the storage domain will allow the update to work, but I am confused though because I have successfully updated this node with a storage domain on it several times now, so is this going to be a permanent requirement? is there any advanced documentation (i.e., this log captures this, here is what to look for when this happens) available?
On Sun, Jun 23, 2019 at 3:30 AM <zachary.winter@witsconsult.com> wrote:
Regarding "Perhaps try to find out what exactly failed?", that is why I posted this thread. I am new to oVirt and trying to master it, but I do not know where to look. I have not found any documentation yet that tells me which logs to look at when, so please bear with me as I try to figure this out. Thank you however for your help.
For general information, see: https://www.ovirt.org/documentation/admin-guide/chap-Log_Files.html
I ran the yum command you listed and got the debug output. I do in fact have a storage domain on the Node, and I am almost certain that is why it is failing. I suspect that removing the storage domain will allow the update to work, but I am confused though because I have successfully updated this node with a storage domain on it several times now, so is this going to be a permanent requirement?
This check was added for the following bug, in 4.2.2 (so rather new - it makes sense that you did mange to use one in the past): https://bugzilla.redhat.com/show_bug.cgi?id=1549630 So it seems to prevent local storage domains on the root filesystem. So you can/should probably try moving your storage domain to a separate filesystem.
is there any advanced documentation (i.e., this log captures this, here is what to look for when this happens) available?
There is lots of material on ovirt.org, including many pages and many many posts to the mailing lists. I am not aware of any book-style "advanced documentation". For this particular example, to find above bug, I did this: Found the place in the source code that includes this scriptlet: https://github.com/oVirt/ovirt-node-ng/blob/master/packaging/ovirt-node-ng.s... Search the git log for this file. You can do this in github ("History" button), but I find it much more comfortable to use 'git log -u' and search inside. This finds: https://github.com/oVirt/ovirt-node-ng/commit/a46150de468fac72224762e67e4f7f... And this links to the bug. Best regards, -- Didi
participants (2)
-
Yedidyah Bar David -
zachary.winter＠witsconsult.com