- Users - oVirt List Archives

Quick Question: Degraded Gluster
by Christian Reiss 18 Mar '21

18 Mar '21

Hey folks, quick question: I have a 3 node cluster (HC) in a production environment. I recently swapped all the storage SSDs with bigger enterprise grades SSDs. So I took a host down (migrating all VMs away, maintenance, shutdown, fix raid, gluster repair, back online). This worked well and all three nodes are now hardware-wise replaced. The last one is still gluster-healing (roughly 20% done). The other two nodes are happily serving the vms while the third one is still in maintenance. my question is: Can I online the maintenance node while gluster is still healing? Or will will open up a can of worms I would not like? It would be cool having all three nodes back online soon while the gluster is still repairing. We have no urge tho. If there is a risk I would wait. If this is somewhat risk-free and do-able why not :) -- with kind regards, mit freundlichen Gruessen, Christian Reiss

2 1

Upgrading DWH from 4.4.4 to 4.4.5
by Nur Imam Febrianto 18 Mar '21

18 Mar '21

Hi, I’m currently trying to upgrade my oVirt Cluster into 4.4.5. Hosted engine upgrade work successfully. But whenever I tried upgrading DWH on separate machine it keep giving me this error : Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans' In engine-setup log : 2021-03-18 23:34:10,976+0700 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/apache/selinux.py", line 40, in _misc osetupcons.SystemEnv.SELINUX_BOOLEANS KeyError: 'OVESETUP_SYSTEM/selinuxBooleans' 2021-03-18 23:34:10,977+0700 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans' Using CentOS 8.3 as separate DWH machine. Anybody maybe can help me ? Thanks before. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

1 0

oVirt 4.4.5 is now generally available
by Lev Veyde 18 Mar '21

18 Mar '21

oVirt 4.4.5 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.5 , as of March 18th, 2021. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.5 Release? This update is the fifth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - oVirt Node (based on CentOS Linux 8.3) - CentOS Stream (tech preview) oVirt Node and Appliance have been updated, including: - oVirt 4.4.5: https://www.ovirt.org/release/4.4.5/ - Ansible 2.9.18: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Advanced Virtualization 8.3.1 - Gluster 8.4: https://docs.gluster.org/en/latest/release-notes/8.4/ See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.5 release highlights: https://www.ovirt.org/release/4.4.5/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.5/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

4.4.5 released? Fails to upgrade
by Rik Theys 18 Mar '21

18 Mar '21

Hi, My systems pulled in 4.4.5 packages last night, so I assume oVirt 4.4.5 was released? The release notes page does not list the release and I also did not see any announcement. The packages are 4.4.5.10-1.el8. I ran an engine-setup and upgraded to this release but the upgrade has failed due to a failure to update the database schema and it seems the rollback was not successful as my instance failed to start afterwards. I've downgraded all packages and ran engine-setup --offline, which seems to at least bring back my engine to a working state. I'm confused: has 4.4.5 been released or did I pull in some intermediate version with known issues? Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee +32(0)16/32.11.07 ---------------------------------------------------------------- <<Any errors in spelling, tact or fact are transmission errors>>

3 3

Python SDK rename virtual machine
by Gerard Weatherby 18 Mar '21

18 Mar '21

Is there an API call in the Ovirt Python SDK to rename an existing virtual machine?

2 2

Migrate windows 2003 server 64bits from libvirt to ovirt
by Fernando Hallberg 17 Mar '21

17 Mar '21

Hi, I have a VM with 2003 server x64, and I upload the vm image to oVirt. The VM boot on the oVirt, but, the blue screen appear with a error message: [image: image.png] Anybody has some information about this? I try to convert de img file from raw to qcow2, but the error persists. Regards, Fernando Hallberg

5 8

Access to the internet from oVirt VMs
by unityresearcher＠alterpost.org 16 Mar '21

16 Mar '21

Hi to all ✋😉 I've stacked with ovirt's vm network routing Infrastructure: 1. stansalone ovirt engine (hetzner cloud vm) 2. ovirt node (hetzner robot, dedicated server) 3. hetzner private cloud network. Both Engine and Node are connected to private network. For node the network is built on external NIC's tagged VLAN https://docs.hetzner.com/robot/dedicated-server/network/vswitch/ 4. Also there is a pfsense router vm in private network So my purpose is to grant access to the internet from VM inside oVirt via pfSense. Additional info: 1. pfsense machine is pingable from oVirt VM 2. oVirt VM NIC – ovirtmgmt 3. pfsenses' NAT works fine for machines in hetzner cloud 4. Painful troubleshooting showed that something on ovirtmgmt bridge forbids to route traffic to another network 5. Internet access "from the box" doesn't work because ovirtmgmt works on VLAN interface, not at physical one itself. 6. In Ovirt's docs I've found the two ways of custom routing. The first one is about external network provider, that unacceptable for me because it doesn't support VLAN tagging (without it node's network can't get access to private cloud network). The second one is custom routing inside a node that doesn't work for me as well by unknown reason What I do wrong? What are the best practices in oVirt network when we talking about internet access from oVirt's VMs? Thx 😉

1 0

ovirt 4.3, hosted engine - network interface validation
by jan.szubiak＠gmail.com 16 Mar '21

16 Mar '21

Hi Community, Right to the point: I'm struggling with the bellow error: Validate selected bridge interface if management bridge does not exists][ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The selected network interface is not valid I can not find any reason why it is rejecting my interface from being valid: [root@ovirttest ~]# ip a sh dev enp0s31f6 2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 8c:16:45:b8:4d:00 brd ff:ff:ff:ff:ff:ff inet 192.168.130.8/24 brd 192.168.130.255 scope global noprefixroute enp0s31f6 valid_lft forever preferred_lft forever inet6 fe80::c7fc:cf7:92a7:e4c/64 scope link noprefixroute valid_lft forever preferred_lft forever [root@ovirttest ~]# ping `hostname -f` -c 1 PING ovirttest.local.test (192.168.130.8) 56(84) bytes of data. 64 bytes from ovirttest.local.test (192.168.130.8): icmp_seq=1 ttl=64 time=0.027 ms --- ovirttest.local.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.027/0.027/0.027/0.000 ms [root@ovirttest ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.9 (Maipo) [root@ovirttest ~]# rpm -q ovirt-engine ovirt-engine-4.3.10.4-1.el7.noarch [root@ovirttest ~]# If I only knew what are the conditions checked against the interface.... I found many posts about this issue, mean - the same error message, but none of the sollution fits to me...:-( Kindly please for advise.... Jan

1 0

OvirtEngine Fails (any ideas?)
by Jason Alexander Hazen Valliant-Saunders 16 Mar '21

16 Mar '21

Failed to start oVirt ImageIO Daemon. CODE_FILE ../src/core/job.c CODE_FUNC job_log_done_status_message CODE_LINE 933 INVOCATION_ID 4c19d99e2caf48a39b4d3c79b290c214 JOB_RESULT failed JOB_TYPE start MESSAGE_ID be02cf6855d2428ba40df7e9d022f03d PRIORITY 3 SYSLOG_FACILITY 3 SYSLOG_IDENTIFIER systemd UNIT ovirt-imageio.service _BOOT_ID 4bd6b8dcfcc04655bb96228bbc07e371 _CAP_EFFECTIVE 3fffffffff _CMDLINE /usr/lib/systemd/systemd --switched-root --system --deserialize 17 _COMM systemd _EXE /usr/lib/systemd/systemd _GID 0 _HOSTNAME ovirt1.altignus.com _MACHINE_ID 0d2ee365ebc64b03982bae07fe190e25 _PID 1 _SELINUX_CONTEXT system_u:system_r:init_t:s0 _SOURCE_REALTIME_TIMESTAMP 1615827351504037 _SYSTEMD_CGROUP /init.scope _SYSTEMD_SLICE -.slice _SYSTEMD_UNIT init.scope _TRANSPORT journal _UID 0 __CURSOR s=896394b4edaf41349024e42366d9e760;i=3393;b=4bd6b8dcfcc04655bb96228bbc07e371;m=30ad6a7e;t=5bd961f4e04b9;x=b3fe6e1de39c7ab8 __MONOTONIC_TIMESTAMP 816671358 __REALTIME_TIMESTAMP 1615827351504057

4 6

Reset NVRAM
by Shantur Rathore 15 Mar '21

15 Mar '21

Hi all, I am doing some testing with GPU passthrough to VMs and in some cases the OVMF stops booting after a GPU passthrough. I have figured out that it's related to some state stored in NVRAM by OVMF and as soon as I create another VM with the same disks it starts booting up. I believe oVirt saves the NVRAM state. Is there a way to clear NVRAM for a VM without deleting it? Regards, Shantur

2 4