- Users - oVirt List Archives

Re: oVirt 4.4.x step-by-step procedure to renew expired oVirt certificates
by Nathanaël Blanchet 17 Jun '22

17 Jun '22

Hello, If you refer to: 1. engine apache certificate expiration ("PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException:) to access to ovirt console. => engine-setup --offline 2. hosts certificate expiration? => https://access.redhat.com/solutions/3532921 I also wrote a playbook to do so there: https://galaxy.ansible.com/natman/ovirt_renew_certs In this case, don't forget to renew certificate with UI (into maintenance) when host is reponding, otherwise you may enconter issues with console or live migration or other SSL related stuff. tested and approved. Le 16/06/2022 à 12:34, Marko Vrgotic a écrit : > > Dear oVirt, > > The oVirt SSL certificated were changed to one-year renewal and we > have a problem now. > > We are running 4.4.x version with SHE on local storage cluster and we > have four more local storage clusters. > > One the cluster running SHE, the engine and host certificates have > expired. We found the procedure for renewal prior to expiration, but > we do not have a mnual one, required once certificates have expired. > > Would you be so kind to share the manual or steps needed to fix our > oVirt setup. > > Thank you in advance. > > ----- > > kind regards/met vriendelijke groeten > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174** > > *e:*m.vrgotic@activevideo.com <mailto:m.vrgotic@activevideo.com> > *w: *www.activevideo.com <http://www.activevideo.com> > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein > 1.1217 WJ Hilversum, The Netherlands. The information contained in > this message may be legally privileged and confidential. It is > intended to be read only by the individual or entity to whom it is > addressed or by their designee. If the reader of this message is not > the intended recipient, you are on notice that any distribution of > this message, in any form, is strictly prohibited. If you have > received this message in error, please immediately notify the sender > and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and > delete or destroy any copy of this message. > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-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/5LOT… -- 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

3 4

Cant fix network
by David Johnson 17 Jun '22

17 Jun '22

Good afternoon all, Welcome to the third part of my trilogy of disaster recovery woes. Much of my woe is self inflicted, but I have learned enough from this that I now know how to ask the right question about the original problem that got me here. After reinstalling the engine from the ground up, ovirt immediately recognized the first host (yay) whose network configuration I had manually fixed on the host console. I removed the host from the engine, stripped its system down to the bare OS, then attempted to reinstall ovirt. Apparently the original network configuration is still saved on the host, because reinstall kicks the host off of the management network, replacing the good configuration that I just made on the host with the bad one that was the original cause of my heartache. What is wrong with this configuration is that the storage network is on a 10 gbit sfp+ physical network, isolated from the 1 gbit ovirtmgt network with RJ12 connectors. There is no way to bridge the two networks Here is the original (bad) configuration: [image: image.png] Here is the corrected configuration. Note that it wont let me connect to the network. it's frustrating because I know that the engine is not communicating with the host, and I can map out the fix here, but I can't save it. [image: image.png] It will not allow me to remove the host or switch the host to inoperable or maintenance mode. Please advise.

2 2

1 Unsynced Entry
by Abe E 16 Jun '22

16 Jun '22

I am having an issue on 1 single node where it is reporting 1 unsynced entry and it is not healing by itself or by force. In the glustershd.log it is reporting the following: W [MSGID: 114031] [client-rpc-fops_v2.c:2620:client4_0_lookup_cbk] 0-data-client-2: remote operation failed. [{path=<gfid:a8769008-3658-400f-b3ba-c0df40e648a7>}, {gfid=a8769008-3658-400f-b3ba-c0df40e648a7}, {errno=2}, {error=No such file or directory}] I assume if it was missing it would look to other nodes for it but I understand from this that even other nodes do not have it?

1 0

OVIRT Package Upgrade Interrupted
by Abe E 16 Jun '22

16 Jun '22

It seems I haven't learned my lesson with upgrading via GUI. For some reason my server crashed during use of the GUI Upgrade method and it looks like maybe it did not complete or the like. 3NodeGluster I then noticed that I had actually upgrading a single node to the 4.5.1 Testing Version, that being said my glusterfs for this node is on 10.2 while other nodes are on 10.1. Is there a "cleaner" way of reverting the upgrade? I assume there are other packages that may have been upgraded that should be reverted.

2 4

Dead agent
by Valerio Luccio 16 Jun '22

16 Jun '22

Hello all, I have an ovirt 4.4 installation whit self-hosted engine where the agent seems to have died. The VMs are still running, so I assume that the engine itself is still running (is this a wrong assumption ?). Can I restart the agent without affecting the running VMs, that is how will restarting the agent affect the running VMs ? If I can restart the agent, what's the correct way of doing it ? Thanks, -- Valerio Luccio High Performance Computing 10 Astor Place, Room 416D New York University New York, NY 10003 "In an open world, who needs windows or gates ?"

2 2

oVirt 4.4.x step-by-step procedure to renew expired oVirt certificates
by Marko Vrgotic 16 Jun '22

16 Jun '22

Dear oVirt, The oVirt SSL certificated were changed to one-year renewal and we have a problem now. We are running 4.4.x version with SHE on local storage cluster and we have four more local storage clusters. One the cluster running SHE, the engine and host certificates have expired. We found the procedure for renewal prior to expiration, but we do not have a mnual one, required once certificates have expired. Would you be so kind to share the manual or steps needed to fix our oVirt setup. Thank you in advance. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.

1 0

libvirtd: dependencies is missing or not an array
by jb 16 Jun '22

16 Jun '22

Hello everybody, in the Protocols from node cockpit, I get some times a day this error: internal error: dependencies is missing or not an array CODE_FILE ../src/util/virjson.c CODE_FUNC virJSONValueObjectGetStringArray CODE_LINE 1324 LIBVIRT_CODE 1 LIBVIRT_DOMAIN 0 LIBVIRT_SOURCE util.error PRIORITY 3 SYSLOG_FACILITY 24 _BOOT_ID 0d6bdd9755d44dac8afe2207f6d69f8d _CAP_EFFECTIVE 1ffffffffff _CMDLINE /usr/sbin/libvirtd _COMM libvirtd _EXE /usr/sbin/libvirtd _GID 0 _HOSTNAME onode1.example.org _MACHINE_ID 977a6d184c604d42ad81ac03904ccba7 _PID 2505 _SELINUX_CONTEXT system_u:system_r:virtd_t:s0-s0:c0.c1023 _SOURCE_REALTIME_TIMESTAMP 1655362628796631 _SYSTEMD_CGROUP /system.slice/libvirtd.service _SYSTEMD_INVOCATION_ID f7685b24f045456aac53ce1673f143c7 _SYSTEMD_SLICE system.slice _SYSTEMD_UNIT libvirtd.service _TRANSPORT journal Is this something I have to worry about it?

1 0

Ovirt manager engine certificate expired
by Don Dupuis 16 Jun '22

16 Jun '22

Hello I have an older installation that was running just great and the certificate expired, it is version 4.2.8.2. I ran the engine-setup as per this "access.redhat.com/solutions/4780411". It didn't update the certificate or the dates and stil have the same issue. Any ideas to fix this issue? Thanks Don

1 2

oVirt 4.5 linux guest vm with host device added to it fails to start
by Don Dupuis 15 Jun '22

15 Jun '22

Hello I have a RHEL 8.6 based hypervisor with a Mellanox ConnectX-5 IB card installed with SRIOV enabled. The host device I am assigning is pci_0000_af_00_2. The card is working as I can talk to other infiniband interfaces on other servers. Below is the output of lspci. 3b:00.0 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5] 3b:00.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5] af:00.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5] af:00.1 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] af:00.2 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] af:00.3 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] af:00.4 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] The linux vm is configured as Q35 Chipset with UEFI, 16 cpus, numa enabled, and cpu pinning enabled. OS is RHEL 7.9. As soon as I start the vm, I get an immediate error message stating "Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host rvsh002 did not satisfy internal filter HostDevice because some of the required host devices are unavailable." If I remove the host device from the vm config, then it starts and runs fine. This setup was working just fine on RHEL8.4 and oVirt 4.4.7 using the proper driver for RHEL 8.4. Here is the engine.log after I press the run button. 2022-06-10 11:22:10,506-05 INFO [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [81144b66-e5f9-474e-a922-e2ce49cdc8ca] Lock Acquired to object 'EngineLock:{exclusiveLocks='[de54b903-7204-4966-95a3-05f64ed17f68=VM]', sharedLocks=''}' 2022-06-10 11:22:10,520-05 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [81144b66-e5f9-474e-a922-e2ce49cdc8ca] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='de54b903-7204-4966-95a3-05f64ed17f68'}), log id: 6faf22a5 2022-06-10 11:22:10,520-05 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [81144b66-e5f9-474e-a922-e2ce49cdc8ca] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 6faf22a5 2022-06-10 11:22:10,560-05 INFO [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-1) [] Candidate host 'rvsh002' ('f68352c2-6ddc-44ae-a19b-9262e92327f8') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'HostDevice' (correlation id: null) 2022-06-10 11:22:10,569-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM ws006 due to a failed validation: [Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host rvsh002 did not satisfy internal filter HostDevice because some of the required host devices are unavailable.] (User: admin@internal-authz). 2022-06-10 11:22:10,569-05 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName rvsh002,$filterName HostDevice,VAR__DETAIL__HOST_DEVICE_UNAVAILABLE,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL 2022-06-10 11:22:10,570-0 There was nothing in the vdsm.log on the hypervisor related to this issue that I could see after hitting the run button. Thanks Don

2 4

dnf update fails on ovirt node 4.5.0-2022052513
by pat＠patfruth.com 14 Jun '22

14 Jun '22

I have freshly install ovirt node 4.5 from the iso download here; https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5.0… The installation appears to have been successful. Now, when I attempt apply the latest updates with 'dnf update', I get an error [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 Here is the entire output of the dnf update command; Last metadata expiration check: 0:47:08 ago on Mon 13 Jun 2022 10:55:35 PM MDT. Dependencies resolved. ======================================================================================================================================================================= Package Architecture Version Repository Size ======================================================================================================================================================================= Installing: ovirt-node-ng-image-update noarch 4.5.1-0.1.el8 ovirt-45-upstream-testing 1.1 G replacing ovirt-node-ng-image-update-placeholder.noarch 4.5.0.3-1.el8 Transaction Summary ======================================================================================================================================================================= Install 1 Package Total download size: 1.1 G Is this ok [y/N]: y Downloading Packages: [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [MIRROR] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 1180431893 but expected size is: 1180857942 [FAILED] ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch.rpm: No more mirrors to try - All mirrors were already tried without success The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Error downloading packages: ovirt-node-ng-image-update-4.5.1-0.1.el8.noarch: Cannot download, all mirrors were already tried without success How can I fix this error, and get the latest updates for 4.5 installed?

5 13

Initramfs and vmlinuz corrupted, how to recover?
by douglasddr8＠gmail.com 14 Jun '22

14 Jun '22

I have a Dell server with a BIOS bug, it corrupted the files during a UEFI boot. I noticed that the initramfs and vmlinuz files are zero-sized How can I retrieve or generate new ones?

3 2

4.4.10 -> 4.5 upgrade on gluster based setups
by Gilboa Davara 14 Jun '22

14 Jun '22

Hello all, I've more or less finished upgrading all my "small" oVirt setups (single hosts, multiple hosts + NFS, etc) and I'm now ready to start upgrading my main production setups. (All using 3 x nodes / gluster setup). A couple of questions: 1. Should I use the normal sequence, as in: engine, hosts, hosts, hosts? 2. Was the gluster bug below still open in the latest oVirt 4.5 release? https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4LGBUOEBV7YNES… Thanks, Gilboa

2 2

Reinstall standalone node without vms loss
by douglasddr8＠gmail.com 14 Jun '22

14 Jun '22

My server failed and I can't boot via UEFI How can I reinstall this node (standalone) without losing my virtual machines?. I checked the filesystem and it's completely intact, I couldn't figure out what caused the UEFI to fail.

2 1

Install Ovirt 4.4.10 to standalone system from iso fails
by David Johnson 14 Jun '22

14 Jun '22

Hi everyone, I am attempting to reinstall as a clean system, and the install is failing silently. At the point where I should be able to run engine-setup, the engine setup utility is absent. Installation medium: iso downloaded from https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.1… As I attempt to install the missing dependencies, I keep getting deeper into missing rpm land. If this iso is no longer any good, even though it is only 4 months old, it should probably be documented as bad or art least superceded by a fixed iso.

3 12

can't use vmconsole anymore
by Nathanaël Blanchet 13 Jun '22

13 Jun '22

Hi, I was used to use the vmconsole proxy, but since a while, I'm getting this issue (currently 4.4.5): # ssh -t -p 2222 ovirt-vmconsole(a)air.v100.abes.fr connect ovirt-vmconsole(a)air.v100.abes.fr: Permission denied (publickey). I found following in the engine.log 2021-04-15 17:55:43,094+02 ERROR [org.ovirt.engine.core.services.VMConsoleProxyServlet] (default task-4) [] Error validating ticket: : sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297) at org.ovirt.engine.core.uutils//org.ovirt.engine.core.uutils.crypto.CertificateChain.buildCertPath(CertificateChain.java:128) at org.ovirt.engine.core.uutils//org.ovirt.engine.core.uutils.crypto.ticket.TicketDecoder.decode(TicketDecoder.java:89) at deployment.engine.ear.services.war//org.ovirt.engine.core.services.VMConsoleProxyServlet.validateTicket(VMConsoleProxyServlet.java:175) at deployment.engine.ear.services.war//org.ovirt.engine.core.services.VMConsoleProxyServlet.doPost(VMConsoleProxyServlet.java:225) The user key is the good one, I use the same with my other engines and I can successfully connect to vm consoles. Thank you for helping -- 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

5 16

Host fails to activate
by David Johnson 12 Jun '22

12 Jun '22

Good afternoon all, Ovirt version: 4.14.4.10.7-1.el8 Centos version: Linux version 4.18.0-365.el8.x86_64 ( mockbuild(a)kbuilder.bsys.centos.org) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-10) (GCC)) #1 SMP Thu Feb 10 16:11:23 UTC 2022 Background: We had a mother board fail in our storage device. I was able to migrate the storage domain to the backup device before it failed completely, and have been running on the backup device for several weeks while we purchased a replacement main storage. Today I shut everything down cleanly, replaced the main storage, and restarted the cluster. We did disconnect and reconnect the network on all of the devices as we shuffled equipment in the rack. One of the hosts in the cluster refuses to come back up.I am able to connect to the host via putty. Ovirt gui reporting: Setting Host ovirt-host-03.maxisinc.net to Non-Operational mode. Completed: Jun 11, 2022, 4:59:57 PM Activating Host ovirt-host-03.maxisinc.net Completed: Jun 11, 2022, 4:59:57 PM Invoking Activate Host ovirt-host-03.maxisinc.net Completed: Jun 11, 2022, 4:57:40 PM Installing Host ovirt-host-03.maxisinc.net log from host is 5:09 PM GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. pulseaudio 4:55 PM bondscan-DGwC1l: option lacp_active: mode dependency failed, not supported in mode balance-alb(6) kernel 4:55 PM bondscan-DGwC1l: option arp_all_targets: invalid value (2) kernel 4:55 PM bondscan-DGwC1l: option fail_over_mac: invalid value (3) kernel 4:55 PM bondscan-DGwC1l: option primary_reselect: invalid value (3) kernel 4:55 PM bondscan-DGwC1l: option ad_select: invalid value (3) kernel 4:55 PM

2 6

oVirt SSH rate limit and disable SSH passwd auth
by tasnadi.peter＠kifu.gov.hu 10 Jun '22

10 Jun '22

Hello, 1. Is it possible to disable ssh root password authentication in a working oVirt cluster without any problems? (host and ovirt-engine) /etc/ssh/sshd_config PasswordAuthentication no The SSH public authentication key is set on the host. 2. I tried setting ssh rate limit using firewall-cmd but it doesn't work for some reason. I can log in more than once. firewall-cmd --permanent --add-rich-rule='rule family="ipv4" priority="-1" service name=ssh limit value=3/m accept' There is best practice for this? Thanks Peter

2 1

[ANN] oVirt 4.5.1 First Release Candidate is now available for testing
by Lev Veyde 09 Jun '22

09 Jun '22

oVirt 4.5.1 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.5.1 First Release Candidate for testing, as of June 9th, 2022. This update is the first in a series of stabilization updates to the 4.5 series. 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>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: - CentOS Stream 8 - RHEL 8.6 Beta and derivatives This release supports Hypervisor Hosts on x86_64: - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 - RHEL 8.6 Beta and derivatives Builds are also available for ppc64le and aarch64. Experimental builds for CentOS Stream 9 are also provided for Hypervisor Hosts. See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.5.1 pre-release highlights: http://www.ovirt.org/release/4.5.1/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.5.1/ [2] http://resources.ovirt.org/pub/ovirt-4.5-pre/iso/ Thanks in advance, -- 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

VmMediatedDevices help for vGPU in overt 4.5
by Don Dupuis 09 Jun '22

09 Jun '22

Hello I am looking for an example on how to use the new VmMediatedDevices service to add an Nvidia vGPU in ovirt to guest vms. I had it working just fine in oVirt 4.4 when using the custom_properties method. Just need to understand the new method/way of doing it correctly using the python3-ovirt-engine-sdk. Thanks Don

2 2

Re: list-view instead of tiled-view in oVirt VM Portal?
by Frank Coons 09 Jun '22

09 Jun '22

Please note that (a) there are people that use more than 20 VM's that do not need admin access, and (b) some people do not LIKE looking at big gaudy buttons, even if there are only 15 of them. I put in an RFE to bring back the list view YEARS ago and was basically told that "we know what you want better than you do." I am willing to bet that many more people want the list view than you realize, but you don't seem to be willing to listen. Disgruntled.

2 1

ovirt 4.4.10 ansible version
by Kapetanakis Giannis 09 Jun '22

09 Jun '22

Could someone verify the correct ansible version for ovirt 4.4.10 ? I'm having dependencies problem: # rpm -q ansible ansible-2.9.27-3.el8.noarch # dnf update Last metadata expiration check: 1:14:38 ago on Thu 09 Jun 2022 10:59:53 EEST. Error: Problem: package ovirt-engine-4.4.10.7-1.el8.noarch requires ansible < 2.10.0, but none of the providers can be installed - cannot install both ansible-5.4.0-2.el8.noarch and ansible-2.9.27-3.el8.noarch - cannot install both ansible-2.9.17-1.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.18-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.20-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.21-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.23-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.24-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install both ansible-2.9.27-2.el8.noarch and ansible-5.4.0-2.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.27-3.el8.noarch - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) # dnf list --showduplicates ansible Last metadata expiration check: 1:15:11 ago on Thu 09 Jun 2022 10:59:53 EEST. Installed Packages ansible.noarch 2.9.27-3.el8 @epel Available Packages ansible.noarch 2.9.17-1.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.18-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.20-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.21-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.23-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.24-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 2.9.27-2.el8 ovirt-4.4-centos-ovirt44 ansible.noarch 5.4.0-2.el8 epel ansible.noarch 5.4.0-2.el8 ovirt-4.4-epel thanks, G

2 1

Re: Self-hosted engine failing liveliness check
by McNamara, Bradley 09 Jun '22

09 Jun '22

When a run "hosted-engine --check-liveliness" it returns "Hosted Engine is not up!" When I run this command and can see it hitting the httpd server, with success, in the httpd logs. Accessing the URL returns this: "DB Up!Welcome to Health Status!". ________________________________ From: McNamara, Bradley <Bradley.McNamara(a)seattle.gov> Sent: Wednesday, June 8, 2022 12:54 PM To: users(a)ovirt.org <users(a)ovirt.org> Subject: [ovirt-users] Self-hosted engine failing liveliness check CAUTION: External Email Hello, and thank you all for your help. I'm running Oracle's rebranded oVirt 4.3.10. All has been good until I patched my self-hosted engine. I ran through the normal process: backup, global maintenance mode, update the oVirt packages, run engine-setup, etc. All completed normally without issues. I rebooted the self-hosted engine VM, and now it constantly fails liveliness checks and the HA agent reboots it every five minutes, or so. I put it in back in global maintenance so the HA agent would not reboot it. The VM is up and works correctly. I can do everything normally. From what I can tell the HA agent liveliness check is just a http get to the web portal. I can see that happening with success. What is the lilveliness check actually doing? All services on the VM are up and running without issue. Where can I look to figure this out? Here is the output of hosted-engine --vm-status: [root@itdlolv101 ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host itdlolv100.ci.seattle.wa.us (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv100.ci.seattle.wa.us Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 855e161f local_conf_timestamp : 55128 Host timestamp : 55128 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=55128 (Wed Jun 8 12:52:20 2022) host-id=1 score=3400 vm_conf_refresh_time=55128 (Wed Jun 8 12:52:20 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host itdlolv101.ci.seattle.wa.us (id: 2) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv101.ci.seattle.wa.us Host ID : 2 Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : cc1c2261 local_conf_timestamp : 45453 Host timestamp : 45453 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=45453 (Wed Jun 8 12:55:15 2022) host-id=2 score=3400 vm_conf_refresh_time=45453 (Wed Jun 8 12:55:15 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !! [root@itdlolv101 ~]#

1 0

Re: storage high latency, sanlock errors, cluster instability
by Nir Soffer 08 Jun '22

08 Jun '22

On Sun, May 29, 2022 at 9:03 PM Jonathan Baecker <jonbae77(a)gmail.com> wrote: > > Am 29.05.22 um 19:24 schrieb Nir Soffer: > > On Sun, May 29, 2022 at 7:50 PM Jonathan Baecker <jonbae77(a)gmail.com> wrote: > > Hello everybody, > > we run a 3 node self hosted cluster with GlusterFS. I had a lot of problem upgrading ovirt from 4.4.10 to 4.5.0.2 and now we have cluster instability. > > First I will write down the problems I had with upgrading, so you get a bigger picture: > > engine update when fine > But nodes I could not update because of wrong version of imgbase, so I did a manual update to 4.5.0.1 and later to 4.5.0.2. First time after updating it was still booting into 4.4.10, so I did a reinstall. > Then after second reboot I ended up in the emergency mode. After a long searching I figure out that lvm.conf using use_devicesfile now but there it uses the wrong filters. So I comment out this and add the old filters back. This procedure I have done on all 3 nodes. > > When use_devicesfile (default in 4.5) is enabled, lvm filter is not > used. During installation > the old lvm filter is removed. > > Can you share more info on why it does not work for you? > > The problem was, that the node could not mount the gluster volumes anymore and ended up in emergency mode. > > - output of lsblk > > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 1.8T 0 disk > `-XA1920LE10063_HKS028AV 253:0 0 1.8T 0 mpath > |-gluster_vg_sda-gluster_thinpool_gluster_vg_sda_tmeta 253:16 0 9G 0 lvm > | `-gluster_vg_sda-gluster_thinpool_gluster_vg_sda-tpool 253:18 0 1.7T 0 lvm > | |-gluster_vg_sda-gluster_thinpool_gluster_vg_sda 253:19 0 1.7T 1 lvm > | |-gluster_vg_sda-gluster_lv_data 253:20 0 100G 0 lvm /gluster_bricks/data > | `-gluster_vg_sda-gluster_lv_vmstore 253:21 0 1.6T 0 lvm /gluster_bricks/vmstore > `-gluster_vg_sda-gluster_thinpool_gluster_vg_sda_tdata 253:17 0 1.7T 0 lvm > `-gluster_vg_sda-gluster_thinpool_gluster_vg_sda-tpool 253:18 0 1.7T 0 lvm > |-gluster_vg_sda-gluster_thinpool_gluster_vg_sda 253:19 0 1.7T 1 lvm > |-gluster_vg_sda-gluster_lv_data 253:20 0 100G 0 lvm /gluster_bricks/data > `-gluster_vg_sda-gluster_lv_vmstore 253:21 0 1.6T 0 lvm /gluster_bricks/vmstore > sr0 11:0 1 1024M 0 rom > nvme0n1 259:0 0 238.5G 0 disk > |-nvme0n1p1 259:1 0 1G 0 part /boot > |-nvme0n1p2 259:2 0 134G 0 part > | |-onn-pool00_tmeta 253:1 0 1G 0 lvm > | | `-onn-pool00-tpool 253:3 0 87G 0 lvm > | | |-onn-ovirt--node--ng--4.5.0.2--0.20220513.0+1 253:4 0 50G 0 lvm / > | | |-onn-pool00 253:7 0 87G 1 lvm > | | |-onn-home 253:8 0 1G 0 lvm /home > | | |-onn-tmp 253:9 0 1G 0 lvm /tmp > | | |-onn-var 253:10 0 15G 0 lvm /var > | | |-onn-var_crash 253:11 0 10G 0 lvm /var/crash > | | |-onn-var_log 253:12 0 8G 0 lvm /var/log > | | |-onn-var_log_audit 253:13 0 2G 0 lvm /var/log/audit > | | |-onn-ovirt--node--ng--4.5.0.1--0.20220511.0+1 253:14 0 50G 0 lvm > | | `-onn-var_tmp 253:15 0 10G 0 lvm /var/tmp > | |-onn-pool00_tdata 253:2 0 87G 0 lvm > | | `-onn-pool00-tpool 253:3 0 87G 0 lvm > | | |-onn-ovirt--node--ng--4.5.0.2--0.20220513.0+1 253:4 0 50G 0 lvm / > | | |-onn-pool00 253:7 0 87G 1 lvm > | | |-onn-home 253:8 0 1G 0 lvm /home > | | |-onn-tmp 253:9 0 1G 0 lvm /tmp > | | |-onn-var 253:10 0 15G 0 lvm /var > | | |-onn-var_crash 253:11 0 10G 0 lvm /var/crash > | | |-onn-var_log 253:12 0 8G 0 lvm /var/log > | | |-onn-var_log_audit 253:13 0 2G 0 lvm /var/log/audit > | | |-onn-ovirt--node--ng--4.5.0.1--0.20220511.0+1 253:14 0 50G 0 lvm > | | `-onn-var_tmp 253:15 0 10G 0 lvm /var/tmp > | `-onn-swap 253:5 0 20G 0 lvm [SWAP] > `-nvme0n1p3 259:3 0 95G 0 part > `-gluster_vg_nvme0n1p3-gluster_lv_engine 253:6 0 94G 0 lvm /gluster_bricks/engine > > - The old lvm filter used, and why it was needed > > filter = ["a|^/dev/disk/by-id/lvm-pv-uuid-Nn7tZl-TFdY-BujO-VZG5-EaGW-5YFd-Lo5pwa$|", "a|^/dev/disk/by-id/lvm-pv-uuid-Wcbxnx-2RhC-s1Re-s148-nLj9-Tr3f-jj4VvE$|", "a|^/dev/disk/by-id/lvm-pv-uuid-lX51wm-H7V4-3CTn-qYob-Rkpx-Tptd-t94jNL$|", "r|.*|"] > > I don't remember exactly any more why it was needed, but without the node was not working correctly. I think I even used vdsm-tool config-lvm-filter. I think that if you list the devices in this filter: ls -lh /dev/disk/by-id/lvm-pv-uuid-Nn7tZl-TFdY-BujO-VZG5-EaGW-5YFd-Lo5pwa \ /dev/disk/by-id/lvm-pv-uuid-Wcbxnx-2RhC-s1Re-s148-nLj9-Tr3f-jj4VvE \ /dev/disk/by-id/lvm-pv-uuid-lX51wm-H7V4-3CTn-qYob-Rkpx-Tptd-t94jNL You will see that these are the devices used by these vgs: gluster_vg_sda, gluster_vg_nvme0n1p3, onn > > - output of vdsm-tool config-lvm-filter > > Analyzing host... > Found these mounted logical volumes on this host: > > logical volume: /dev/mapper/gluster_vg_nvme0n1p3-gluster_lv_engine > mountpoint: /gluster_bricks/engine > devices: /dev/nvme0n1p3 > > logical volume: /dev/mapper/gluster_vg_sda-gluster_lv_data > mountpoint: /gluster_bricks/data > devices: /dev/mapper/XA1920LE10063_HKS028AV > > logical volume: /dev/mapper/gluster_vg_sda-gluster_lv_vmstore > mountpoint: /gluster_bricks/vmstore > devices: /dev/mapper/XA1920LE10063_HKS028AV > > logical volume: /dev/mapper/onn-home > mountpoint: /home > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-ovirt--node--ng--4.5.0.2--0.20220513.0+1 > mountpoint: / > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-swap > mountpoint: [SWAP] > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-tmp > mountpoint: /tmp > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var > mountpoint: /var > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_crash > mountpoint: /var/crash > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_log > mountpoint: /var/log > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_log_audit > mountpoint: /var/log/audit > devices: /dev/nvme0n1p2 > > logical volume: /dev/mapper/onn-var_tmp > mountpoint: /var/tmp > devices: /dev/nvme0n1p2 > > Configuring LVM system.devices. > Devices for following VGs will be imported: > > gluster_vg_sda, gluster_vg_nvme0n1p3, onn > > To properly configure the host, we need to add multipath > blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf: > > blacklist { > wwid "eui.0025388901b1e26f" > } > > > Configure host? [yes,NO] If you run "vdsm-tool config-lvm-filter" and confirm with "yes", I think all the vgs will be imported properly into lvm devices file. I don't think it will solve the storage issues you have since Feb 2022, but at least you will have a standard configuration and the next upgrade will not revert your local settings. > If using lvm devices does not work for you, you can enable the lvm > filter in vdsm configuration > by adding a drop-in file: > > $ cat /etc/vdsm/vdsm.conf.d/99-local.conf > [lvm] > config_method = filter > > And run: > > vdsm-tool config-lvm-filter > > to configure the lvm filter in the best way for vdsm. If this does not create > the right filter we would like to know why, but in general you should use > lvm devices since it avoids the trouble of maintaining the filter and dealing > with upgrades and user edited lvm filter. > > If you disable use_devicesfile, the next vdsm upgrade will enable it > back unless > you change the configuration. > > I would be happy to just use the default, when there is a way to make use_devicesfile to wok. > > Also even if you disable use_devicesfile in lvm.conf, vdsm still use > --devices instead > of filter when running lvm commands, and lvm commands run by vdsm ignore your > lvm filter since the --devices option overrides the system settings. > > ... > > I notice some unsync volume warning, but because I had this in the past to, after upgrading, I though after some time they will disappear. The next day there still where there, so I decided to put the nodes again in the maintenance mode and restart the glusterd service. After some time the sync warnings where gone. > > Not clear what these warnings are, I guess Gluster warning? > > Yes was Gluster warnings under Storage -> Volumes it was saying that some entries are unsync. > > So now the actual problem: > > Since this time the cluster is unstable. I get different errors and warning, like: > > VM [name] is not responding > out of nothing HA VM gets migrated > VM migration can fail > VM backup with snapshoting and export take very long > > How do you backup the vms? do you sue a backup application? how is it > configured? > > I use a self made plython script, which uses the rest api. I create a snapshot from the VM, build a new VM from that snapshot and move the new one to the export domain. This is not very efficient - this copy the entire vm at the point of time of the snapshot and then copy it again to the export domain. If you use a backup application supporting the incremental backup API, the first full backup will copy the entire vm once, but later incremental backup will copy only the changes since the last backup. > > VMs are getting very slow some times > Storage domain vmstore experienced a high latency of 9.14251 > ovs|00001|db_ctl_base|ERR|no key "dpdk-init" in Open_vSwitch record "." column other_config > 489279 [1064359]: s8 renewal error -202 delta_length 10 last_success 489249 > 444853 [2243175]: s27 delta_renew read timeout 10 sec offset 0 /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/ids > 471099 [2243175]: s27 delta_renew read timeout 10 sec offset 0 /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/ids > many of: 424035 [2243175]: s27 delta_renew long write time XX sec > > All these issues tell use that your storage is not working correctly. > > sanlock.log is full of renewal errors form May: > > $ grep 2022-05- sanlock.log | wc -l > 4844 > > $ grep 2022-05- sanlock.log | grep 'renewal error' | wc -l > 631 > > But there is lot of trouble from earlier months: > > $ grep 2022-04- sanlock.log | wc -l > 844 > $ grep 2022-04- sanlock.log | grep 'renewal error' | wc -l > 29 > > $ grep 2022-03- sanlock.log | wc -l > 1609 > $ grep 2022-03- sanlock.log | grep 'renewal error' | wc -l > 483 > > $ grep 2022-02- sanlock.log | wc -l > 826 > $ grep 2022-02- sanlock.log | grep 'renewal error' | wc -l > 242 > > Here sanlock log looks healthy: > > $ grep 2022-01- sanlock.log | wc -l > 3 > $ grep 2022-01- sanlock.log | grep 'renewal error' | wc -l > 0 > > $ grep 2021-12- sanlock.log | wc -l > 48 > $ grep 2021-12- sanlock.log | grep 'renewal error' | wc -l > 0 > > vdsm log shows that 2 domains are not accessible: > > $ grep ERROR vdsm.log > 2022-05-29 15:07:19,048+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 16:33:59,049+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 16:34:39,049+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 17:21:39,050+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 17:55:59,712+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/metadata > (monitor:511) > 2022-05-29 17:56:19,711+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/metadata > (monitor:511) > 2022-05-29 17:56:39,050+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_data/de5f4123-0fac-4238-abcf-a329c142bd47/dom_md/metadata > (monitor:511) > 2022-05-29 17:56:39,711+0200 ERROR (check/loop) [storage.monitor] > Error checking path > /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/dom_md/metadata > (monitor:511) > > You need to find what is the issue with your Gluster storage. > > I hope that Ritesh can help debug the issue with Gluster. > > Nir > > I'm worry that I do something, that it makes it even more worst, and I hove not idea what's the problem. To me it looks not exactly like a problem with data inconsistencies. The problem is that your Gluster storage is not healthy, and reading and writing to it times out. Please keep users(a)ovirt.org CC when you reply. Gluster storage is very popular in this mailing list and you may get useful help from other users. Nir

4 3

Self-hosted engine failing liveliness check
by McNamara, Bradley 08 Jun '22

08 Jun '22

Hello, and thank you all for your help. I'm running Oracle's rebranded oVirt 4.3.10. All has been good until I patched my self-hosted engine. I ran through the normal process: backup, global maintenance mode, update the oVirt packages, run engine-setup, etc. All completed normally without issues. I rebooted the self-hosted engine VM, and now it constantly fails liveliness checks and the HA agent reboots it every five minutes, or so. I put it in back in global maintenance so the HA agent would not reboot it. The VM is up and works correctly. I can do everything normally. From what I can tell the HA agent liveliness check is just a http get to the web portal. I can see that happening with success. What is the lilveliness check actually doing? All services on the VM are up and running without issue. Where can I look to figure this out? Here is the output of hosted-engine --vm-status: [root@itdlolv101 ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host itdlolv100.ci.seattle.wa.us (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv100.ci.seattle.wa.us Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 855e161f local_conf_timestamp : 55128 Host timestamp : 55128 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=55128 (Wed Jun 8 12:52:20 2022) host-id=1 score=3400 vm_conf_refresh_time=55128 (Wed Jun 8 12:52:20 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host itdlolv101.ci.seattle.wa.us (id: 2) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : itdlolv101.ci.seattle.wa.us Host ID : 2 Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : cc1c2261 local_conf_timestamp : 45453 Host timestamp : 45453 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=45453 (Wed Jun 8 12:55:15 2022) host-id=2 score=3400 vm_conf_refresh_time=45453 (Wed Jun 8 12:55:15 2022) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !! [root@itdlolv101 ~]#

1 0

How to run virt-sysprep / How to troubleshoot template creation failure
by jeremy_tourville＠hotmail.com 08 Jun '22

08 Jun '22

When attempting to create a template the process fails. It has been suggested to run virt-sysprep manually and see why it it failed. Specifically, I have an Ubuntu 20.04 machine that doesn't boot properly even if the the template process does finish without error. I have tried creating the template several times as a test. about 80% of the time the template creation fails outright for qemu errors. The other 20% "appear" to work but the system boots to a grub emergency prompt Can someone clarify the process? I know you can run the command: virt-sysprep -d <name_of_vm> 1. Where do you run it from? The hypervisor host or the management engine? 2. What account do you need to use? What is the authentication username and password? I also think I read somewhere that you should refrain from using root. Anything else to know? Anything else to try regarding the grub prompt? Thanks.

2 5