After failed upgrade from 4.5.1 to 4.5.3, upgrades do not show up anymore
by 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":
----
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
1 year, 4 months
vdsmd crashes with sigsegv
by ovirt＠kirschke.de
Hello,
since upgrade from ovirt 4.3 to 4.5., I encounter problems with one host. vdsmd permanently crashes after a while and it tells me, a segmentation violation is the cause.
As result, it becomes unresponsive to ovirt-engine.
Environment:
rocky linux 8.6, up to date
ovirt 4.5.2;
One datacenter, compatibility level 4.7
The ovirt engine is on a seperate vm outside of ovirt.
Any one else had that problem, or a has a tipp, where to start investigating the problem?
Thanks and best regards
Steffen
1 year, 5 months
what happens to vms when a host shutdowns?
by Nathanaël Blanchet
Hi,
We are installing UPS powerchute client on hypervisors.
What is the default vms behaviour of running vms when an hypervisor is
ordered to shutdown: do the vms live migrate or do they shutdown
properly (even the restart on an other host because of HA) ?
--
Nathanaël Blanchet
Supervision réseau
SIRE
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet(a)abes.fr
1 year, 5 months
Hosted engine 4.5.3.2 - still with bug
by vanBulion＠gmail.com
hi
I've try to install new hosted-engine version but deploy process finish with an error after vm start on shared storage (FC disks from SAN storage).
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check engine VM health]
this cuz Jboos web page not working
"Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
I open console to VM engine and...
disk dm-6 and dm-3 was corrupted - LOL - must fix by xfs_repair.
But after restart hosted-engne.service wont start.
● ovirt-engine.service - oVirt Engine
Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2022-10-31 15:35:30 CET; 4min 11s ago
Process: 1469 ExecStart=/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify $EXTRA_ARGS start (code=exited, status=1/FAILURE)
Main PID: 1469 (code=exited, status=1/FAILURE)
Oct 31 15:35:23 ovirt systemd[1]: Starting oVirt Engine...
Oct 31 15:35:23 ovirt systemd[1]: Started oVirt Engine.
Oct 31 15:35:26 ovirt ovirt-engine.py[1469]: 2022-10-31 15:35:26,606+0100 ovirt-engine: INFO _detectJBossVersion:186 Detecting JBoss version. Running: /usr/lib/jvm/jre-11-openjdk-11.0.>
Oct 31 15:35:30 ovirt ovirt-engine.py[1469]: 2022-10-31 15:35:30,369+0100 ovirt-engine: INFO _detectJBossVersion:206 Return code: -6, | stdout: '['#', '# A fatal error has been detect>
Oct 31 15:35:30 ovirt ovirt-engine.py[1469]: 2022-10-31 15:35:30,370+0100 ovirt-engine: ERROR run:543 Error: Cannot detect JBoss version
Oct 31 15:35:30 ovirt.pogodno systemd[1]: ovirt-engine.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 15:35:30 ovirt.pogodno systemd[1]: ovirt-engine.service: Failed with result 'exit-code'.
I even try to downgrade postgresql-jdbc to 42.2.3 but no effect.
If I stop deploy process when VM start from local storage and I dont continue it - engine VM start with no error but VM start without HA IP configured - not usefully.
So I still witing to good working - ovirt-engine-appliance 4.5
ovirt-node-ng-installer-4.5.3.2-2022102813.el8.iso
ovirt-engine-appliance-4.5-20221026100732.1.el8.x86_64.rpm
Regards
Damian
1 year, 5 months
Creating new system
by vkasabiev＠gmail.com
Hello, can you pls help me with creating my oVirt system. I installed Centos 7 on one VM and on one physical server. I succesfully configured my VM for oVirtEngie and I can access to web interface.
Now I want to configure my physical server to use it as virtualization server(kvm01). My VM has 2 disks, one for system and one for ISO images. My phisycal server also has 2 disks(actually 4 but in 2 Raid1). One for system and one for virtualization storage. Its the second time I try to install everything properly, 1st time I had some issues and decided to reinstall everything. 1st time I successfully added my kvm01 to my ovirtengine, but I couldnt create any VM because I had error with my Data Center, that had status uninitialized, and it seems like I cant initialize it because I have no domain. I'm already confused and decided to ask forum for a correct answer and advices. What shell I do first? I havent added kvm01 to my ovirtEngine yet.
1 year, 5 months
VNC console connection fails [ovirt 4.5.3.1-1.el8]
by andre.liebe＠gematik.de
Hello list,
is there anybody else out there having problems to connect to a vm console via vnc or is it just me?
We are running ovirt-engine 4.5.3.1-1.el8 on up to date ovirt-nodes. I can connect to every virtual machine by spice, but am unable to connect via vnc due to a tls handshake error.
Remote-viever just shows "Failed to complete handshake Error in the pull function" (on windows and linux clients).
Wireshark tls handshake capture looks supicious to me, server hello message is just 182 bytes long and doesn't coantain a server certificate. Is this normal?
sincerely
André
1 year, 5 months
How can I download multiple disks using wget or curl?
by wodel youchi
Hi,
VM disks can be downloaded from the Manager UI. How can I achieve the
same result using curl or wget or something else?
I have several disks that I wish to download via script. Could you
help with that?
Regards.
1 year, 5 months
mom-vdsm service is failing after update to 4.5.3.2-1.el8
by Jirka Simon
Hello there,
we just updated oVirt engine to 4.5.3.2-1.el8 which was smooth, but then
when we start to update all nodes, after restart mom-vdsm service is
failing to start
mom-vdsm
rpm -q vdsm
vdsm-4.50.3.4-1.el8.x86_64 (VDSM was updated from 4.50.2.2-1.el8 )
rpm -q mom
mom-0.6.3-1.el8.noarch (MOM was not updated duting tha last update)
here is error from /var/log/vdsm/mom.log
2022-10-28 13:17:18,105 - mom - INFO - MOM starting
2022-10-28 13:17:18,138 - mom.HostMonitor - INFO - Host Monitor starting
2022-10-28 13:17:18,138 - mom - INFO - hypervisor interface
vdsmjsonrpcclient
2022-10-28 13:17:18,179 - mom.HostMonitor - INFO - HostMonitor is ready
2022-10-28 13:17:18,242 - mom.GuestManager - INFO - Guest Manager
starting: multi-thread
2022-10-28 13:17:18,247 - mom.Policy - INFO - Loaded policy '00-defines'
2022-10-28 13:17:18,247 - mom - ERROR - Failed to initialize MOM threads
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/mom/__init__.py", line 35, in run
host_monitor, guest_manager)
File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 42,
in __init__
self.load_policy()
File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 71,
in load_policy
read_policy(fname, name.split('.policy')[0])
File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 53,
in read_policy
return self.policy.set_policy(policy_name, policyStr)
File "/usr/lib/python3.6/site-packages/mom/Policy/Policy.py", line 64,
in set_policy
self.code = get_code(Evaluator(), self._cat_policies())
File "/usr/lib/python3.6/site-packages/mom/Policy/Parser.py", line
543, in get_code
tokens = scanner.tokenize(string)
File "/usr/lib/python3.6/site-packages/mom/Policy/Parser.py", line 72,
in tokenize
GenericScanner.tokenize(self, input)
File "/usr/lib/python3.6/site-packages/mom/Policy/spark.py", line 78,
in tokenize
add_lines = self.index2func[i](groups[i], line)
TypeError: t_default() takes 2 positional arguments but 3 were given
any tip what could be the reason ?
Thaak you
Jirka
1 year, 5 months
Nightly build to stable
by Erdősi Péter
Hi,
I've installed the Version
4.5.4-0.2.master.20221007083550.gitb24d914c24.el8 few days before (since
the stable not working at the time)
Is there any way to make this installation following the stable updates
if the 4.5.4 became stable?
Regards,
Peter
--
*Erdősi Péter
* /Informatikus, IKT Fejlesztési Főosztály /
*Kormányzati Informatikai Fejlesztési Ügynökség
* cím: 1134 Budapest, Váci út 35.
tel: +36 1 450 3080 e-mail: erdosi.peter(a)kifu.gov.hu
<mailto:erdosi.peter@kifu.gov.hu>
KIFÜ - www.kifu.gov.hu <http://kifu.gov.hu/kifu/>
1 year, 5 months
