August 2022 - Users - oVirt List Archives

Clarify the cert renewal docs
by cen 17 Aug '22

17 Aug '22

Hi Speaking of this guide: https://www.ovirt.org/documentation/administration_guide/index.html#chap-Re… We have 2 hosts and one HostedEngine VM. It is unclear to me if step 1 should be done for all hosts first and then do the step 2, or if I should enroll host1 first, then run the engine-setup and then do the host2. It doesn't really make sense to run engine-setup again after enrolling host2 though, so that would make it 1 (host1), 2, 1 (host2), skip 2. Or does it? Best regards, cen

1 0

oVirt node 4.4 repository missing package
by kenneth.hau＠hactl.com 17 Aug '22

17 Aug '22

Hi there, I saw that there has new package of ovirt-node-ng-image-update-placeholder-4.4.10.3-1.el8.noarch.rpm has released on 2022-06-24. However, I would like to know if there has any plan to release new package of ovirt-node-ng-image-update-4.4.10.3-1.el8.noarch.rpm as the the package is still retain at 4.4.10.2-1. Many thanks.

1 0

Cannot start VM after upgrade - certificate issue
by LAMARC 16 Aug '22

16 Aug '22

Hello, after running a PoC oVirt setup for more than a year, I ran into the "expiring certificate issue". Done an full upgrade for 4.4, engine-setup, and "Enroll certificates" to all hosts, all hosts are now green, and the certificates are renewed: - /etc/pki/vdsm/certs/vdsmcert.pem - /etc/pki/vdsm/libvirt-spice/server-cert.pem - /etc/pki/libvirt/clientcert.pem - /etc/pki/vdsm/libvirt-migrate/server-cert.pem But: I cannot start any VM any more. Getting: engine.log:2022-08-16 16:34:36,209+02 ERROR [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-213) [60c5f661-6231-4e03-87a5-f6e6f2c63ad1] Command 'org.ovirt.engine.core.bll.RunVmCommand' failed: EngineException: (Failed with error NotAfter: Mon Aug 15 09:15:42 CEST 2022 and code 5050) Any ideas? Cheers Marcus

1 0

VM (live) migrate after update ovirt 4.2 -> 4.4
by Fabian Mohren 16 Aug '22

16 Aug '22

Hi, we have upgrade the Cluster (and all Hosts) to oVirt 4.4 and Oracle Linux 8.5 After the Upgrade, we cannot migrate VMs from one Host to another (same Cluster). oVirt stock, and on Hosts Tab we see the message (one the vm): "VM-CPU dosent match the Cluster-CPU". We checked the xml config from kvm We checked the DB for Cluster-CPU and VM-CPU - its the same (Cascadelake-Server-noTSX,-mpx). select name, cpu_name, cpu_flags from cluster; name | cpu_name | cpu_flags --------------------------+----------------------------------------+------------------------------------ TestMigrationCluster | Intel Haswell Family | vmx,nx,model_Haswell-noTSX select vm_guid, vm_name, cpu_name from vms where vm_name='oVirtTest'; vm_guid | vm_name | cpu_name --------------------------------------+-----------+--------------- 421ade0f-4d76-941d-3de2-13b1df54c89d | oVirtTest | Haswell-noTSX We create a new "TestMigrationCluster" with two Hosts for better testing. We reinstall the Hosts (OS + ovirt) = failed We reset the manager to an older State = failed We have no idea where the "Cluster-CPU check" is running? We search for a ansible role or play but nothing found Have anybody a idea where the Cluster CPU check is? Thanks & Regards Fabian

1 0

Server patching on the oVirt node
by kenneth.hau＠hactl.com 16 Aug '22

16 Aug '22

Server patching on the oVirt node Hi there, we have some oVirt node running on 4.4 and found vulnerabilities after performed TVM scan on the server. Please advise how can we fix the below vulnerabilities. Python Unsupported Version Detection CentOS 8 : cockpit (CESA-2022:2008) CentOS 8 : container-tools:3.0 (CESA-2022:1793) CentOS 8 : container-tools:3.0 (CESA-2022:2143) CentOS 8 : samba (CESA-2022:2074) CentOS 8 : maven:3.6 (CESA-2022:1860)

1 0

Changing Cluster Compatibility Version from 4.6 to 4.7 issue
by Alexandr Mikhailov 15 Aug '22

15 Aug '22

Hi! Just uprgaded from 4.4. to 4.5. Had all the problems with this update, such as postgresql-jdbc version and with stripeCount in cli.y . But I managed it, everything works more or less. Now I cannot raise the Cluster compatibility level. The problem is that increasing the level tries to change something in the HE configuration but cannot. This is error massage: Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. "There was an attempt to change Hosted Engine VM values that are locked." is one of the error(s). To fix the issue, please go to each VM/Template, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details. If i trying to edit HE machine without changing anything i se next error: There was an attempt to change Hosted Engine VM values that are locked/ I think this is linked issues. Log from engine log when i trying to update Cluster version: 2022-05-27 14:20:54,410+06 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-212) [1b8b6b78] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Ca nnot update compatibility version of Vm/Template: [HostedEngine], Message: There was an attempt to change Hosted Engine VM values that are locked. Log from engine log when i trying to save HE configuration without any changing: 2022-05-27 14:34:10,965+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock Acquired to object 'EngineLock:{exclusiveLocks='[HostedEngine= VM_NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}' 2022-05-27 14:34:10,968+06 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Validation of action 'UpdateVm' failed for user admin@internal-auth z. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,VM_CANNOT_UPDATE_HOSTED_ENGINE_FIELD 2022-05-27 14:34:10,969+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock freed to object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_ NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}' It is not clear what is happening and what changes to the configuration are trying to be saved and what to do about it. Help please.

4 4

Re: gluster service on the cluster is unchecked on hci cluster
by Strahil Nikolov 15 Aug '22

15 Aug '22

Can you check for AVC denials and the error message like the described in https://github.com/gluster/glusterfs-selinux/issues/27#issue-1097225183 ? Best Regards,Strahil Nikolov On Mon, Jul 11, 2022 at 16:44, Jiří Sléžka<jiri.slezka(a)slu.cz> wrote: Hello, On 7/11/22 14:34, Strahil Nikolov wrote: > Can you check something on the host: > cat /etc/glusterfs/eventsconfig.json cat /etc/glusterfs/eventsconfig.json { "log-level": "INFO", "port": 24009, "disable-events-log": false } > semanage port -l | grep $(awk -F ':' '/port/ {gsub(",","",$2); print > $2}' /etc/glusterfs/eventsconfig.json) semanage port -l | grep 24009 returns empty set, it looks like this port is not labeled Cheers, Jiri > > Best Regards, > Strahil Nikolov > В понеделник, 11 юли 2022 г., 02:18:57 ч. Гринуич+3, Jiří Sléžka > <jiri.slezka(a)slu.cz> написа: > > > Hi, > > I would like to change CPU Type in my oVirt 4.4.10 HCI cluster (based on > 3 glusterfs/virt hosts). When I try to I got this error > > Error while executing action: Cannot disable gluster service on the > cluster as it contains volumes. > > As I remember I had Gluster Service enabled on this cluster but now both > (Enable Virt Services and Enable Gluster Service) checkboxes are grayed > out and Gluster Service is unchecked. > > Also Storage / Volumes displays my volumes... well, displays one brick > on particular host in unknown state (? mark) which is new situation. As > I can see from command line all bricks are online, no healing in > progress, all looks good... > > I am not sure if the second issue is relevant to first one so main > question is how can I (re)enable gluster service in my cluster? > > Thanks in advance, > > Jiri > _______________________________________________ > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> > To unsubscribe send an email to users-leave(a)ovirt.org > <mailto:users-leave@ovirt.org> > Privacy Statement: https://www.ovirt.org/privacy-policy.html > <https://www.ovirt.org/privacy-policy.html> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://www.ovirt.org/community/about/community-guidelines/> > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/S4NVCQ33ZSJSH… > <https://lists.ovirt.org/archives/list/users@ovirt.org/message/S4NVCQ33ZSJSH…>

2 22

Upgrade 4.4 to 4.5 node package issue
by Jason Beard 15 Aug '22

15 Aug '22

I'm updating my environment from 4.4 to 4.5. The Hosted Engine upgrade completed with no errors. On both nodes it fails at step 1. My nodes are CentOS Stream 8. Is there a release package I can download somewhere? Or is something else going on? # dnf install -y centos-release-ovirt45 Last metadata expiration check: 0:08:42 ago on Thu 11 Aug 2022 10:43:28 PM CDT. No match for argument: centos-release-ovirt45 Error: Unable to find a match: centos-release-ovirt45 # cat /etc/os-release NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8.6.2109.0" VARIANT="oVirt Node 4.4.10.2" VARIANT_ID="ovirt-node" PRETTY_NAME="oVirt Node 4.4.10" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.ovirt.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" PLATFORM_ID="platform:el8"

3 3

oVirt 4.5.2 is now generally available
by Lev Veyde 13 Aug '22

13 Aug '22

The oVirt project is excited to announce the general availability of oVirt 4.5.2, as of August 10th, 2022. 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 on top of oVirt 4.4. Important notes before you install / upgrade Some of the features included in oVirt 4.5.2 require content that is available in RHEL 8.6 (or newer) and derivatives. NOTE: If you’re going to install oVirt 4.5.2 on RHEL or similar, please read Installing on RHEL or derivatives <https://ovirt.org/download/install_on_rhel.html> first. Documentation Be sure to follow instructions for oVirt 4.5! - 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.5.2 Release? This release is available now on x86_64 architecture for: - CentOS Stream 8 - RHEL 8.6 and derivatives This release supports Hypervisor Hosts on x86_64: - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 - RHEL 8.6 and derivatives This release also supports Hypervisor Hosts on x86_64 as tech preview without secure boot: - CentOS Stream 9 - RHEL 9.0 and derivatives - oVirt Node NG based on CentOS Stream 9 Builds are also available for ppc64le and aarch64. Known issues: - On EL9 with UEFI secure boot, vdsm fails to decode DMI data due to Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> - python-dmidecode module fails to decode DMI data Security fixes included in oVirt 4.5.2 compared to latest oVirt 4.5.1: Bug list <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> Some of the RFEs with high user impact are listed below: Bug list <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> Some of the Bugs with high user impact are listed below: Bug list <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> oVirt Node will be released shortly after the release will reach the CentOS mirrors. See the release notes for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.5.2 release highlights: https://www.ovirt.org/release/4.5.2/ - 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/ -- 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>

2 2

Q: libvirtd-tls startup failure on node (v4.4.10)
by Andrei Verovski 13 Aug '22

13 Aug '22

Hi, I have one problematic node, and identified a culprit why vdsmd service can't start: -- The unit libvirtd-tls.socket has entered the 'failed' state with result 'service-start-limit-hit'. Aug 13 15:00:45 node14.starlett.lv systemd[1]: Closed Libvirt TLS IP socket. -- Subject: Unit libvirtd-tls.socket has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support Node was installed on clean CentOS Stream from oVirt Web (not oVirt node disk image), and was working fine until recent problem with certificates. Can't reinstall/reconfigure node from oVirt Web since it is marked as non-responsive. How to fix this? Thanks in advance for any help. --------------------- [root@node14 vdsm]# cat /etc/centos-release CentOS Stream release 8 [root@node14 vdsm]# rpm -qa | grep vdsm vdsm-api-4.40.100.2-1.el8.noarch vdsm-hook-openstacknet-4.40.100.2-1.el8.noarch vdsm-client-4.40.100.2-1.el8.noarch vdsm-network-4.40.100.2-1.el8.x86_64 vdsm-hook-vhostmd-4.40.100.2-1.el8.noarch vdsm-4.40.100.2-1.el8.x86_64 vdsm-http-4.40.100.2-1.el8.noarch vdsm-common-4.40.100.2-1.el8.noarch vdsm-hook-fcoe-4.40.100.2-1.el8.noarch vdsm-python-4.40.100.2-1.el8.noarch vdsm-jsonrpc-4.40.100.2-1.el8.noarch vdsm-hook-ethtool-options-4.40.100.2-1.el8.noarch vdsm-yajsonrpc-4.40.100.2-1.el8.noarch [root@node14 vdsm]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts [root@node14 vdsm]# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● libvirtd.service loaded failed failed Virtualization daemon ● libvirtd-admin.socket loaded failed failed Libvirt admin socket ● libvirtd-ro.socket loaded failed failed Libvirt local read-only socket ● libvirtd-tls.socket loaded failed failed Libvirt TLS IP socket ● libvirtd.socket loaded failed failed Libvirt local socket

1 0