- Users - oVirt List Archives

Cannot change Cluster Compatibility Version after 4.4 upgrade
by paolo＠airaldi.it 28 Sep '20

28 Sep '20

Hi all, we have an oVirt 4.3 with 3 Hosts and 20 VMs. 2 Hosts are Dell PowerEdge R610 with 2 Intel(R) Xeon(R) CPU E5540 processor each (Intel Nehalem IBRS SSBD), while the third is an HP ProLiant ML350p Gen8 with 2 Intel(R) Xeon(R) CPU E5-2620 v2 processor (Intel SandyBridge IBRS SSBD MDS) They all are in the same Cluster. Some of the 20 VMs are Windows (Win 10, Win 2012 and Win 2016) We have upgraded to 4.4.2.6-1.el8 following the instruction https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3. We had some minor issues that have been fixed and now we need to change Cluster Compatibility Version, but it fails complaining about Win10 and Win2016 VMs. In agent.log, for each of them I have: WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-122) [292f1983] Validation of action 'UpdateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,CPU_TYPE_UNSUPPORTED_FOR_THE_GUEST_OS,$uns upportedCpus opteron_g1, conroe, nehalem, penryn The same messages appear even if the VMs are powered off. We tried to change the Operating System in one VM configuration and if we put Win2012 the VM is no more in the error list when we edit the Cluster, but we're not sure the VMs will restart once Cluster compatibility will be to 4.4 How can we proceed? Hosts: # rpm -qa|grep -i ovirt ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch ovirt-host-dependencies-4.4.1-4.el8.x86_64 ovirt-hosted-engine-setup-2.4.6-1.el8.noarch ovirt-python-openvswitch-2.11-0.2020061801.el8.noarch ovirt-imageio-daemon-2.0.10-1.el8.x86_64 ovirt-release44-4.4.2-1.el8.noarch ovirt-vmconsole-1.0.8-1.el8.noarch python3-ovirt-engine-sdk4-4.4.4-1.el8.x86_64 ovirt-imageio-client-2.0.10-1.el8.x86_64 cockpit-ovirt-dashboard-0.14.11-1.el8.noarch ovirt-provider-ovn-driver-1.2.30-1.el8.noarch ovirt-vmconsole-host-1.0.8-1.el8.noarch ovirt-openvswitch-2.11-0.2020061801.el8.noarch ovirt-openvswitch-ovn-common-2.11-0.2020061801.el8.noarch ovirt-openvswitch-ovn-host-2.11-0.2020061801.el8.noarch ovirt-openvswitch-ovn-2.11-0.2020061801.el8.noarch ovirt-ansible-engine-setup-1.2.4-1.el8.noarch ovirt-host-4.4.1-4.el8.x86_64 python3-ovirt-setup-lib-1.3.2-1.el8.noarch ovirt-imageio-common-2.0.10-1.el8.x86_64 ovirt-hosted-engine-ha-2.4.4-1.el8.noarch Engine: # rpm -qa|grep -i ovirt ovirt-engine-extension-aaa-jdbc-1.2.0-1.el8.noarch ovirt-engine-dbscripts-4.4.2.6-1.el8.noarch ovirt-engine-tools-4.4.2.6-1.el8.noarch ovirt-openvswitch-ovn-central-2.11-0.2020061801.el8.noarch ovirt-cockpit-sso-0.1.4-1.el8.noarch ovirt-ansible-infra-1.2.2-1.el8.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.4.2.6-1.el8.noarch ovirt-engine-tools-backup-4.4.2.6-1.el8.noarch ovirt-engine-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch ovirt-release44-4.4.2-1.el8.noarch python3-ovirt-setup-lib-1.3.2-1.el8.noarch ovirt-openvswitch-ovn-common-2.11-0.2020061801.el8.noarch ovirt-imageio-daemon-2.0.10-1.el8.x86_64 ovirt-python-openvswitch-2.11-0.2020061801.el8.noarch ovirt-ansible-image-template-1.2.2-1.el8.noarch ovirt-ansible-shutdown-env-1.1.0-1.el8.noarch python3-ovirt-engine-lib-4.4.2.6-1.el8.noarch ovirt-provider-ovn-1.2.30-1.el8.noarch ovirt-engine-dwh-grafana-integration-setup-4.4.2.1-1.el8.noarch ovirt-engine-dwh-setup-4.4.2.1-1.el8.noarch ovirt-openvswitch-ovn-2.11-0.2020061801.el8.noarch ovirt-vmconsole-proxy-1.0.8-1.el8.noarch ovirt-imageio-common-2.0.10-1.el8.x86_64 ovirt-ansible-engine-setup-1.2.4-1.el8.noarch ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch ovirt-ansible-repositories-1.2.5-1.el8.noarch ovirt-engine-setup-4.4.2.6-1.el8.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch ovirt-engine-webadmin-portal-4.4.2.6-1.el8.noarch ovirt-engine-extension-aaa-ldap-1.4.1-1.el8.noarch ovirt-engine-extension-aaa-misc-1.1.0-1.el8.noarch ovirt-engine-extensions-api-1.0.1-1.el8.noarch ovirt-engine-setup-plugin-websocket-proxy-4.4.2.6-1.el8.noarch ovirt-engine-api-explorer-0.0.6-1.el8.noarch ovirt-engine-setup-plugin-cinderlib-4.4.2.6-1.el8.noarch ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch ovirt-engine-wildfly-19.1.0-2.el8.x86_64 ovirt-engine-wildfly-overlay-19.1.0-2.el8.noarch ovirt-web-ui-1.6.4-1.el8.noarch ovirt-openvswitch-2.11-0.2020061801.el8.noarch python3-ovirt-engine-sdk4-4.4.4-1.el8.x86_64 ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch ovirt-engine-metrics-1.4.1.1-1.el8.noarch ovirt-ansible-manageiq-1.2.1-1.el8.noarch ovirt-engine-4.4.2.6-1.el8.noarch ovirt-engine-extension-logger-log4j-1.1.0-1.el8.noarch ovirt-engine-websocket-proxy-4.4.2.6-1.el8.noarch ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch ovirt-engine-backend-4.4.2.6-1.el8.noarch ovirt-vmconsole-1.0.8-1.el8.noarch ovirt-dependencies-4.4.2-1.el8.noarch ovirt-ansible-vm-infra-1.2.3-1.el8.noarch ovirt-ansible-roles-1.2.3-1.el8.noarch ovirt-engine-setup-base-4.4.2.6-1.el8.noarch ovirt-engine-dwh-4.4.2.1-1.el8.noarch ovirt-engine-restapi-4.4.2.6-1.el8.noarch ovirt-engine-ui-extensions-1.2.3-1.el8.noarch ovirt-engine-extension-aaa-ldap-setup-1.4.1-1.el8.noarch ovirt-ansible-disaster-recovery-1.3.0-1.el8.noarch

2 1

Re: oVirt networking.
by dhanaraj.ramesh＠yahoo.com 28 Sep '20

28 Sep '20

Hi 1) trunk all the network including management, VM traffic subnets in both ports and tag the management network as native 2) configure the bonds with active/backup with management IP while installing the OS 3) proceed the hosted engine installation in the same management network 4) once hosted engine is up, add all hosts and create vm traffic network with VLAN tags

1 0

oVirt networking.
by Matthew.Stier＠fujitsu.com 28 Sep '20

28 Sep '20

oVirt newbie starting with 4.4.2. Any good documentation on setting up networking? I want to bond my two network interfaces. The native interface will be uses for management. All other traffic will be over tagged vlans.

1 0

MOM can't run
by duhongyu 27 Sep '20

27 Sep '20

hi I try to start momd by "systemctl restart momd" but it can't run , so I run momd by " /usr/sbin/momd -c /etc/momd.conf " [root@node0 mom]# /usr/sbin/momd -c /etc/momd.conf 2020-09-27 14:31:12,291 - mom - INFO - MOM starting 2020-09-27 14:31:12,381 - mom.HostMonitor - INFO - Host Monitor starting 2020-09-27 14:31:12,381 - mom - INFO - hypervisor interface vdsm 2020-09-27 14:31:12,690 - mom - ERROR - Unable to import hypervisor interface: vdsm 2020-09-27 14:31:12,707 - mom.GuestManager - INFO - Guest Manager starting: multi-thread 2020-09-27 14:31:12,708 - mom.GuestManager - INFO - Guest Manager ending 2020-09-27 14:31:12,708 - mom.PolicyEngine - INFO - Policy Engine starting 2020-09-27 14:31:12,709 - mom.RPCServer - INFO - RPC Server is disabled 2020-09-27 14:31:12,710 - mom - INFO - Shutting down RPC server. 2020-09-27 14:31:12,710 - mom.PolicyEngine - INFO - Policy Engine ending 2020-09-27 14:31:12,710 - mom - INFO - Waiting for RPC server thread. 2020-09-27 14:31:12,710 - mom - INFO - Waiting for policy engine thread. 2020-09-27 14:31:12,710 - mom - INFO - Waiting for guest manager thread. 2020-09-27 14:31:12,710 - mom - INFO - Waiting for host monitor thread. 2020-09-27 14:31:12,828 - mom.HostMonitor - INFO - HostMonitor is ready 2020-09-27 14:31:17,710 - mom - INFO - MOM ending /usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmInterface.py import sys sys.path.append('/usr/share/vdsm') import API import supervdsm import logging import traceback from mom.HypervisorInterfaces.HypervisorInterface import HypervisorInterface, \ HypervisorInterfaceError after I debug momd, I find not import API and supervdsm, can you give me some suggestion? -- Regards Hongyu Du

2 1

Re: Recreating ISO storage domain
by Strahil Nikolov 27 Sep '20

27 Sep '20

Actually ISO domain is not necessary. You can moutn it via FUSE to a system and either use the python script ( It was mentioned several times in the mailing list) or the API/UI to upload your ISOs to a data storage domain. I think it is about time to get rid of the deprecated ISO domain. Best Regards, Strahil NIkolov В събота, 26 септември 2020 г., 21:44:28 Гринуич+3, Matthew.Stier(a)fujitsu.com <matthew.stier(a)fujitsu.com> написа: I have created a three host oVirt cluster using 4.4.2. I created an ISO storage domain to hold my collection of ISO images, and then decided to migrate it to a better location. I placed the storage domain in maintenance mode, end then removed it. When I when to recreate it add the new location, I found that the ‘ISO’ storage domain was no longer an options. What do I need to do to re-enable it, so I can re-create the storage domain. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-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/4YVAUMRFWO7FN…

1 0

Re: Random hosts disconnects
by Artur Socha 27 Sep '20

27 Sep '20

On Fri, Sep 18, 2020 at 1:54 PM Anton Louw <Anton.Louw(a)voxtelecom.co.za> wrote: > > > Hi Artur, > > > > Thanks for the reply. I have attached the system logs. There was a > disconnect at 10:54, but no error that is different to the rest. I do see a > whole lot of QEMU Guest Agent and block_io errors in the system logs. Not > entirely sure what this means. > After a very quick search on the internet the first one does not seem to be severe at all - this guest agent provides only some information to VMs about the host. *Sep 18 10:50:41 node05.kvm.voxvm.co.za <http://node05.kvm.voxvm.co.za> libvirtd[23603]: 2020-09-18 08:50:41.493+0000: 23729: error : qemuDomainAgentAvailable:9133 : Guest agent is not responding: QEMU guest agent is not connected* The second one is unknown to me at all: ISep 18 10:50:52 node05.kvm.voxvm.co.za libvirtd[23603]: 2020-09-18 08:50:52.802+0000: 23729: error : qemuMonitorJSONBlockIoThrottleInfo:5005 : internal error: block_io_throttle inserted entry was not in expected format Sep 18 Perhaps someone with more libvirt/qemu background will comment on that. > > Checking the vdsm logs at the time or the error, the only entry is the > below: > > > > “2020-09-18 10:55:57,081+0000 WARN (qgapoller/2) > [virt.periodic.VmDispatcher] could not run <function <lambda> at > 0x7f2170395578> on ['d3838612-70bb-4731-a0d4-8f65d31b40a6', > '59a2f394-48fe-4bd9-91d6-08115f2eec0a', > 'f81e3ab8-c1a9-4674-b238-7e229fd43e7c', > '42189fa1-4381-02c7-d830-20eac408da2c', > '423f1c57-f98e-707f-c0f9-d4958d3f0fec', > '64d1eabc-20ff-4288-98ff-dcfd120fe7d2', > '4218baf0-e2a1-42c7-2efd-077407f47b4d', > '42184650-5a60-5403-d758-840bdbf92dd8', > '492ea3fe-0a27-4dde-abf9-7d146ee1b988', > '4218df00-15cd-bdf9-efd9-c5ead49fd89c', > '9c373379-718b-4906-abc1-960fb1820c2d', > 'b9441c7a-0bfd-4d41-a8de-ee24e4259b36', > 'd810325a-1a45-4054-a870-c8c052a22354', > '42189d3f-4570-45ea-6e5a-94c85a5885a1'] (periodic:289)” > > This WARN does not seem to be the cause ... it may be be the result because VM failed to be dispatched (perhaps due to lack of suitable hosts that got disconnected at a moment) > > I am stumped. Do you think it is worth a shot increasing the vdsConnectionTimeout > and vdsHeartbeatInSeconds to 40 for testing purposes? > I still don't think it will change anything unless your network between those 2 DC is 'tcp over pigeons' kind of setup :) Now, more seriously. Even if increasing timeouts would fix the connectivity I suspect the core issue would still remain ... in the best case scenario it could be postponed a bit. Am I correct assuming those 2 DC are located in 2 different physical locations? If so then I would closely check the network itself first (including hardware like routers/switches). Artur > > > Thanks > > > > *Anton Louw* > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > [image: F] <https://www.facebook.com/voxtelecomZA> > [image: T] <https://www.twitter.com/voxtelecom> > [image: I] <https://www.instagram.com/voxtelecomza/> > [image: L] <https://www.linkedin.com/company/voxtelecom> > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > *From:* Artur Socha <asocha(a)redhat.com> > *Sent:* 18 September 2020 13:27 > *To:* Anton Louw <Anton.Louw(a)voxtelecom.co.za> > *Cc:* users(a)ovirt.org > *Subject:* Re: [ovirt-users] Re: Random hosts disconnects > > > > Hi Anton, > > I am not sure if changing this value would fix the issue. Defaults are > pretty high. For example vdsHeartbeatInSeconds=30seconds, > vdsTimeout=180seconds, vdsConnectionTimeout=20seconds. > > > > Do you still have relevant logs from the affected hosts: > > * /var/logs/vdsm/vdsm.log* > > * /var/logs/vdsm/supervdsm.log* > > Please look for any jsonrpc errors ie. write/read errors or (connection) > timeouts. Storage related warnings/errors might also be relevant. > > > > Plus system logs if possible: > > *journalctl -f /usr/share/vdsm/vdsmd* > > *journalctl -f /usr/sbin/libvirtd* > > > > In order to get system logs from particular time period please combine it > with the following example using -S -U options: > > *journalctl -S "2020-01-12 07:00:00" -U "2020-01-12 07:15:00" * > > I haven't a clue what to look there for besides any warnings/errors or > anything else that seems .... unusual. > > > > Artur > > > > > > On Thu, Sep 17, 2020 at 8:09 AM Anton Louw via Users <users(a)ovirt.org> > wrote: > > > > Hi Everybody, > > > > Did some digging around, and saw a few things regarding “vdsHeartbeatInSeconds” > > I had a look at the properties file located at /etc/ovirt-engine/engine-config/engine-config.properties, and do not see an entry for “vdsHeartbeatInSeconds.type=Integer”. > > Seeing as these data centers are geographically split, could the “vdsHeartbeatInSeconds” potentially be the issue? Is it safe to increase this value after I add “vdsHeartbeatInSeconds.type=Integer” into my engine-config.properties file? > > > > Thanks > > > > > > *Anton Louw* > > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > > > [image: F] <https://www.facebook.com/voxtelecomZA> > > > > [image: T] <https://www.twitter.com/voxtelecom> > > > > [image: I] <https://www.instagram.com/voxtelecomza/> > > > > [image: L] <https://www.linkedin.com/company/voxtelecom> > > > > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > > > > > *From:* Anton Louw via Users <users(a)ovirt.org> > *Sent:* 16 September 2020 09:01 > *To:* users(a)ovirt.org > *Subject:* [ovirt-users] Random hosts disconnects > > > > > > Hi All, > > > > I have a strange issue in my oVirt environment. I currently have a > standalone manager which is running in VMware. In my oVirt environment, I > have two Data Centers. The manager is currently sitting on the same subnet > as DC1. Randomly, hosts in DC2 will say “Not Responding” and then 2 seconds > later, the hosts will activate again. > > > > The strange thing is, when the manager was sitting on the same subnet as > DC2, hosts in DC1 will randomly say “Not Responding” > > > > I have tried going through the logs, but I cannot see anything out of the > ordinary regarding why the hosts would drop connection. I have attached the > engine.log for anybody that would like to do a spot check. > > > > Thanks > > > > *Anton Louw* > > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > > > [image: F] <https://www.facebook.com/voxtelecomZA> > > > > [image: T] <https://www.twitter.com/voxtelecom> > > > > [image: I] <https://www.instagram.com/voxtelecomza> > > > > [image: L] <https://www.linkedin.com/company/voxtelecom> > > > > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > > > > > [image: #VoxBrand] > <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > > > *Disclaimer* > > The contents of this email are confidential to the sender and the intended > recipient. Unless the contents are clearly and entirely of a personal > nature, they are subject to copyright in favour of the holding company of > the Vox group of companies. Any recipient who receives this email in error > should immediately report the error to the sender and permanently delete > this email from all storage devices. > > This email has been scanned for viruses and malware, and may have been > automatically archived by *Mimecast Ltd*, an innovator in Software as a > Service (SaaS) for business. Providing a *safer* and *more useful* place > for your human generated data. Specializing in; Security, archiving and > compliance. To find out more Click Here > <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > > > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/EJL246IPBGEHI… > > > > -- > > Artur Socha > Senior Software Engineer, RHV > Red Hat > > -- Artur Socha Senior Software Engineer, RHV Red Hat

2 1

Re: Populating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

It is being mounted under /rhev/data-center/mnt/ on the hosts, but is not being self-hosted engine. From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Saturday, September 26, 2020 4:17 PM To: Edward Berger <edwberger(a)gmail.com> Cc: users(a)ovirt.org Subject: [ovirt-users] Re: Populating ISO storage domain I setup the folder and the files with 36:36 with a mode of 775 on the directory and 644 on the files. Hours later, still not being read. From: Edward Berger <edwberger(a)gmail.com<mailto:edwberger@gmail.com>> Sent: Saturday, September 26, 2020 2:01 PM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org> Subject: Re: [ovirt-users] Populating ISO storage domain If its in an NFS folder, make sure the ownership is vdsm:kvm (36:36) On Sat, Sep 26, 2020 at 2:57 PM Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com> <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> wrote: I’ve created and ISO storage domain, and placed ISO’s in the export path do not show up under Storage > Storage Domains > iso > images; nor as available images which creating a new VM. Haven’t located method get them noticed. There is a greyed out ‘scan disk’ option. What is the proper method to install ISO images. _______________________________________________ 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 oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/M6QYBMNT43MTW…

1 0

Re: Populating ISO storage domain
by Edward Berger 26 Sep '20

26 Sep '20

If its in an NFS folder, make sure the ownership is vdsm:kvm (36:36) On Sat, Sep 26, 2020 at 2:57 PM Matthew.Stier(a)fujitsu.com < Matthew.Stier(a)fujitsu.com> wrote: > I’ve created and ISO storage domain, and placed ISO’s in the export path > do not show up under Storage > Storage Domains > iso > images; nor as > available images which creating a new VM. > > > > Haven’t located method get them noticed. There is a greyed out ‘scan > disk’ option. > > > > What is the proper method to install ISO images. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/M6QYBMNT43MTW… >

2 1

Populating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

I've created and ISO storage domain, and placed ISO's in the export path do not show up under Storage > Storage Domains > iso > images; nor as available images which creating a new VM. Haven't located method get them noticed. There is a greyed out 'scan disk' option. What is the proper method to install ISO images.

1 0

Re: Recreating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

Got this fixed. Ignore. From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Saturday, September 26, 2020 1:39 PM To: users(a)ovirt.org Subject: [ovirt-users] Recreating ISO storage domain I have created a three host oVirt cluster using 4.4.2. I created an ISO storage domain to hold my collection of ISO images, and then decided to migrate it to a better location. I placed the storage domain in maintenance mode, end then removed it. When I when to recreate it add the new location, I found that the 'ISO' storage domain was no longer an options. What do I need to do to re-enable it, so I can re-create the storage domain.

1 0

Recreating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

I have created a three host oVirt cluster using 4.4.2. I created an ISO storage domain to hold my collection of ISO images, and then decided to migrate it to a better location. I placed the storage domain in maintenance mode, end then removed it. When I when to recreate it add the new location, I found that the 'ISO' storage domain was no longer an options. What do I need to do to re-enable it, so I can re-create the storage domain.

1 0

Node upgrade to 4.4
by Vincent Royer 26 Sep '20

26 Sep '20

I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How do I upgrade to 4.4? Is there a guide?

6 11

oVirt - Engine - VM Reconstitute
by Jeremey Wise 26 Sep '20

26 Sep '20

As expected... this is a learning curve. My three node cluster.. in an attempt to learn how to do admin work on it, debug it... I have now redeployed the engine and even added second one on a node in cluster. But..... I now realize that my "production vms" are gone. In the past, on a manual build with KVM + Gluster .. when I repaired a damaged cluster I would just then browse to the xml file and import. I think with oVirt, those days are gone. As the PostGres engine knows the links to the disk / thin provision volumes / network / VM definition files. ###### Question: 1) Can someone point me to the manual on how to re-constitute a VM and bring it back into oVirt where all "oVirt-engines" were redeployed. It is only three or four VMs I typically care about (HA cluster and OCP ignition/ Ansible tower VM). 2) How do I make sure these core VMs are able to be reconstituted. Can I create a dedicated volume where the VMs are full provisioned, and the path structure is "human understandable". 3) I know that you can backup the engine. If I had been a smart person, how does one backup and recover from this kind of situation. Does anyone have any guides or good articles on this? Thanks, -- p <jeremey.wise(a)gmail.com>enguinpages

3 5

Re: Node 4.4.1 gluster bricks
by Strahil Nikolov 26 Sep '20

26 Sep '20

Since oVirt 4.4 , the stage that deploys the oVirt node/host is adding an lvm filter in /etc/lvm/lvm.conf which is the reason behind that. Best Regards, Strahil Nikolov В петък, 25 септември 2020 г., 20:52:13 Гринуич+3, Staniforth, Paul <p.staniforth(a)leedsbeckett.ac.uk> написа: Thanks, the gluster volume is just a test and the main reason was to test the upgrade of a node with gluster bricks. I don't know why lvm doesn\t work which is what oVirt is using. Regards, Paul S. ________________________________ From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: 25 September 2020 18:28 To: Users <users(a)ovirt.org>; Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> Subject: Re: [ovirt-users] Node 4.4.1 gluster bricks Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. >1 node I wiped it clean and the other I left the 3 gluster brick drives untouch. If the last node from the original is untouched you can: 1. Go to the old host and use 'gluster volume remove-brick <VOL> replica 1 wiped_host:/path/to-brick untouched_bricks_host:/path/to-brick force' 2. Remove the 2 nodes that you have kicked away: gluster peer detach node2 gluster peer detach node3 3. Reinstall the wiped node and install gluster there 4. Create the filesystem on the brick: mkfs.xfs -i size=512 /dev/mapper/brick_block_device 5. Mount the Gluster (you can copy the fstab entry from the working node and adapt it) Here is an example: /dev/data/data1 /gluster_bricks/data1 xfs inode64,noatime,nodiratime,inode64,nouuid,context="system_u:object_r:glusterd_brick_t:s0" 0 0 6. Create the selinux label via 'semanage fcontext -a -t glusterd_brick_t "/gluster_bricks/data1(/.*)?"' (remove only the single quotes) and run 'restorecon -RFvv /gluster_bricks/data1' 7. Mount the FS and create a dir inside the mount point 8. Extend the gluster volume: 'gluster volume add-brick <VOL> replica 2 new_host:/gluster_bricks/<dir>/<subdir> 9. Run a full heal gluster volume heal <VOL> full 10. Repeat again and remember to never wipe 2 nodes at a time :) Good luck and take a look at Quick Start Guide - Gluster Docs Best Regards, Strahil Nikolov To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

1 0

Re: Node 4.4.1 gluster bricks
by Strahil Nikolov 25 Sep '20

25 Sep '20

>1 node I wiped it clean and the other I left the 3 gluster brick drives untouch. If the last node from the original is untouched you can: 1. Go to the old host and use 'gluster volume remove-brick <VOL> replica 1 wiped_host:/path/to-brick untouched_bricks_host:/path/to-brick force' 2. Remove the 2 nodes that you have kicked away: gluster peer detach node2 gluster peer detach node3 3. Reinstall the wiped node and install gluster there 4. Create the filesystem on the brick: mkfs.xfs -i size=512 /dev/mapper/brick_block_device 5. Mount the Gluster (you can copy the fstab entry from the working node and adapt it) Here is an example: /dev/data/data1 /gluster_bricks/data1 xfs inode64,noatime,nodiratime,inode64,nouuid,context="system_u:object_r:glusterd_brick_t:s0" 0 0 6. Create the selinux label via 'semanage fcontext -a -t glusterd_brick_t "/gluster_bricks/data1(/.*)?"' (remove only the single quotes) and run 'restorecon -RFvv /gluster_bricks/data1' 7. Mount the FS and create a dir inside the mount point 8. Extend the gluster volume: 'gluster volume add-brick <VOL> replica 2 new_host:/gluster_bricks/<dir>/<subdir> 9. Run a full heal gluster volume heal <VOL> full 10. Repeat again and remember to never wipe 2 nodes at a time :) Good luck and take a look at Quick Start Guide - Gluster Docs Best Regards, Strahil Nikolov

2 1

oVirt host "unregistered"
by Jeremey Wise 25 Sep '20

25 Sep '20

Trying to get all the 3 node cluster back fully working... clearing out all the errors. I noted that the HCI wizard.. I thing SHOULD have deployed a hosted engine on the nodes, but this is not the case .. Only thor... the first node in cluster has hosted engine. I tried to redeploy this via the Cockpit wizard to add engine to host.. but I think this may not have been correct repair path. Now node in cluster shows all bricks... green (so it detects after reboot that host is back up and working.. but hosts lists it as "red triangle" with error "unregistered" I also just tried on third node to "edit" -> Host Engine -> and click drop box and choose "deploy" only log in event is "Host medusa configuration was updated by admin@internal-authz. 9/24/208:49:24 PM" but nothing changes. I then ran on odin (node with error) ovirt-hosted-engine-cleanup but no change ################ [root@odin ~]# ovirt-hosted-engine-cleanup This will de-configure the host to run ovirt-hosted-engine-setup from scratch. Caution, this operation should be used with care. Are you sure you want to proceed? [y/n] y -=== Destroy hosted-engine VM ===- You must run deploy first error: failed to get domain 'HostedEngine' -=== Stop HA services ===- -=== Shutdown sanlock ===- shutdown force 1 wait 0 shutdown done 0 -=== Disconnecting the hosted-engine storage domain ===- You must run deploy first -=== De-configure VDSM networks ===- ovirtmgmt ovirtmgmt A previously configured management bridge has been found on the system, this will try to de-configure it. Under certain circumstances you can loose network connection. Caution, this operation should be used with care. Are you sure you want to proceed? [y/n] y -=== Stop other services ===- Warning: Stopping libvirtd.service, but it can still be activated by: libvirtd-ro.socket libvirtd.socket libvirtd-admin.socket -=== De-configure external daemons ===- Removing database file /var/lib/vdsm/storage/managedvolume.db -=== Removing configuration files ===- ? /etc/init/libvirtd.conf already missing - removing /etc/libvirt/nwfilter/vdsm-no-mac-spoofing.xml ? /etc/ovirt-hosted-engine/answers.conf already missing ? /etc/ovirt-hosted-engine/hosted-engine.conf already missing - removing /etc/vdsm/vdsm.conf - removing /etc/pki/vdsm/certs/cacert.pem - removing /etc/pki/vdsm/certs/vdsmcert.pem - removing /etc/pki/vdsm/keys/vdsmkey.pem - removing /etc/pki/vdsm/libvirt-migrate/ca-cert.pem - removing /etc/pki/vdsm/libvirt-migrate/server-cert.pem - removing /etc/pki/vdsm/libvirt-migrate/server-key.pem - removing /etc/pki/vdsm/libvirt-spice/ca-cert.pem - removing /etc/pki/vdsm/libvirt-spice/server-cert.pem - removing /etc/pki/vdsm/libvirt-spice/server-key.pem - removing /etc/pki/vdsm/libvirt-vnc/ca-cert.pem - removing /etc/pki/vdsm/libvirt-vnc/server-cert.pem - removing /etc/pki/vdsm/libvirt-vnc/server-key.pem - removing /etc/pki/CA/cacert.pem - removing /etc/pki/libvirt/clientcert.pem - removing /etc/pki/libvirt/private/clientkey.pem ? /etc/pki/ovirt-vmconsole/*.pem already missing - removing /var/cache/libvirt/qemu ? /var/run/ovirt-hosted-engine-ha/* already missing - removing /var/tmp/localvm69i1jxnd - removing /var/tmp/localvmfyg59713 - removing /var/tmp/localvmmg5y6g52 -=== Removing IP Rules ===- [root@odin ~]# [root@odin ~]# ################ Ideas on how to repair engine install issues on nodes? -- penguinpages

3 3

Re: Node 4.4.1 gluster bricks
by Jayme 25 Sep '20

25 Sep '20

Assuming you don't care about data on the drive you may just need to use wipefs on the device i.e. wipefs -a /dev/sdb On Fri, Sep 25, 2020 at 12:53 PM Staniforth, Paul < P.Staniforth(a)leedsbeckett.ac.uk> wrote: > Hello, > how do you manage a gluster host when upgrading a node? > > I upgraded/replaced 2 nodes with the new install and can't recreate any > gluster bricks. > 1 node I wiped it clean and the other I left the 3 gluster brick drives > untouched. > > If I try to create bricks using the UI on the nodes, I get an internal > server error. When I try to create a PV from the clean disk, I get device > excluded by filter. > > e.g. > > pvcreate /dev/sdb > > Device /dev/sdb excluded by a filter. > > pvcreate /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN > > Device /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN excluded by a > filter. > > > > > Thanks, > > > Paul S. > > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/27IUR3H54G2FR… >

2 1

Node 4.4.1 gluster bricks
by Staniforth, Paul 25 Sep '20

25 Sep '20

Hello, how do you manage a gluster host when upgrading a node? I upgraded/replaced 2 nodes with the new install and can't recreate any gluster bricks. 1 node I wiped it clean and the other I left the 3 gluster brick drives untouched. If I try to create bricks using the UI on the nodes, I get an internal server error. When I try to create a PV from the clean disk, I get device excluded by filter. e.g. pvcreate /dev/sdb Device /dev/sdb excluded by a filter. pvcreate /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN Device /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN excluded by a filter. Thanks, Paul S. To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

1 0

oVirt 4.4.2 is now generally available
by Lev Veyde 25 Sep '20

25 Sep '20

The oVirt project is excited to announce the general availability of oVirt 4.4.2 , as of September 17th, 2020. 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.2 Release? This update is the second 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.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) will be released separately due to a blocker issue (Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864>). oVirt Node and Appliance have been updated, including: - oVirt 4.4.2: http://www.ovirt.org/release/4.4.2/ - Ansible 2.9.13: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ 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 will be available soon for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ - 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.4.2/ [2] http://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>

3 5

[ANN] oVirt 4.4.3 Second Release Candidate is now available for testing
by Lev Veyde 25 Sep '20

25 Sep '20

oVirt 4.4.3 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Second Release Candidate for testing, as of September 25th, 2020. This update is the third in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) 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.3 release highlights: http://www.ovirt.org/release/4.4.3/ * 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.4.3/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/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

export to ova
by Tommaso - Shellrent 25 Sep '20

25 Sep '20

Hi to all. Hi try to ank another time the same question: in our tests ovirt seems to be able to make only one export to ova at time. also on different hosts and datacenter. Someone can explain to us why?? this is for us a big issue, because we use it in a backup script of more than 50 VMs and counting.... We also already opened a bug without any useful response: https://bugzilla.redhat.com/show_bug.cgi?id=1855782 Regards, -- -- Shellrent - Il primo hosting italiano Security First *Tommaso De Marchi* /COO - Chief Operating Officer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155> | Fax 04441492177

2 1

oVirt 4.3 HCI ovirtmgmt vlan problem
by wodel youchi 24 Sep '20

24 Sep '20

Hi, I deployed an HCI of three nodes using ovirt 4.3 on a flat network at the beginning, now we need to use VLAN on the management network. I have ovirtmgmt over bond2, this bond will have three vlans : vlan 10 for management, vlan20 for DMZ and vlan30 for DMZ2. On the switch, I did configure the concerned ports to support ; the native vlan (untagged), the vlan10 (tagged), ...etc. Then I activated the tag on the ovirtmgmt network on the web UI, I did lose connexion to the hypervisors and things got weird, I then put my machine on vlan10, I saw that two of my hypervisors had their network configuration modified to use the vlan10, but not the hypervisor where the VM-engine was running. I created the vlan manually on that hypervisor, then I started the VM-Manager, all hosts were recognized. Then I stopped, then started the platforme again. Still the same problem, two hosts are correct with their vlan : bond2.10 created, but the third no vlan. Doing the configuration manually works, but it does not survive reboot, is there a way to force vdsm to accept the new configuration on that faulty host? Regards.

2 1

LVM-Thin error node instalation
by Jorge Visentini 24 Sep '20

24 Sep '20

Hello. I'm having trouble installing 4.4.2. The same problem happened in the 4.4.1 media. At the time of post installation, it gives error of LVM Thin Provisioning. I tried to switch from LVM Thin to LVM and the same error happened. In version 4.3 this error does not happen. I was unable to copy the error text, so I am attaching the images. [image: ovirt_installer01.jpg] [image: ovirt_installer02.jpg] Thank you all! -- Att, Jorge Visentini +55 55 98432-9868

2 1

ISO Repo
by Jeremey Wise 24 Sep '20

24 Sep '20

I saw notes about oVirt 4.4 may no longer support ISO images... but there are times like now I need to build based on specific ISO images. I tried to do a cycle to create an image file 8GB then do dd if=blah.iso of=/<random disk ID image file name> Created a new vm with this as boot disk and it fails to boot... so.. back to "create volume for iso images" But when I do that I get error New Domain -> "Domain function" =iso Storage type = glusterFs Use Managed Gluster volume -> Select already working gluster file space "thor.penguinpages.local:/iso VFS Type: glusterfs mount options: backup-volfile-servers=odin.penguinpages.local:medusa.penguinpages.local Error: Error while executing action: Cannot add Storage Connection. Performance o_direct option is not enabled for storage domain. Questions: 1) Why did the image and dd of iso to boot disk not work? 2) Any ideas about create of iso mount volume? -- penguinpages

5 8

Adding host fails with Ansible host-deploy role: Internal server error.
by Andrey Andrey 24 Sep '20

24 Sep '20

Hello! Updated host engine to version 4.4.2. I am trying to add a new host and I get the Host node2.kvm.test.s1.eirc installation failed error. Failed to execute Ansible host-deploy role: Internal server error. Please check logs for more details: /var/log/ovirt-engine/ansible-runner-service.log. Also updated Hosted Engine to version 4.4.3.3-1.el8, I get the same error. Only old entries are in the logs. New does not appear [root@admin ovirt-engine]# tail /var/log/ovirt-engine/ansible-runner-service.log 2020-09-22 18:02:13,943 - runner_service.controllers.jobs - INFO - 127.0.0.1 - GET /api/v1/jobs/8e369e4c-fce4-11ea-b893-00163e4843d7/events 2020-09-22 18:02:13,943 - runner_service.controllers.jobs - INFO - 127.0.0.1 - GET /api/v1/jobs/8e3cba7a-fce4-11ea-b893-00163e4843d7/events 2020-09-22 18:02:13,944 - runner_service.services.jobs - DEBUG - Job events for play 8e369e4c-fce4-11ea-b893-00163e4843d7: 25 2020-09-22 18:02:13,944 - runner_service.services.jobs - DEBUG - Job events for play 8e3cba7a-fce4-11ea-b893-00163e4843d7: 25 2020-09-22 18:02:13,944 - runner_service.services.jobs - DEBUG - Active filter is :{} 2020-09-22 18:02:13,944 - runner_service.services.jobs - DEBUG - Active filter is :{} 2020-09-22 18:02:13,948 - runner_service.controllers.jobs - DEBUG - Request received, content-type :None 2020-09-22 18:02:13,949 - runner_service.controllers.jobs - INFO - 127.0.0.1 - GET /api/v1/jobs/8e369e4c-fce4-11ea-b893-00163e4843d7/events 2020-09-22 18:02:13,949 - runner_service.services.jobs - DEBUG - Job events for play 8e369e4c-fce4-11ea-b893-00163e4843d7: 25 2020-09-22 18:02:13,949 - runner_service.services.jobs - DEBUG - Active filter is :{} In file /var/log/ovirt-engine/engine.log 2020-09-24 10:36:36,645+03 INFO [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-23) [de214fcc-31fc-464c-8ac1-6e111889cd20] Running command: AddVdsCommand internal: false. Entities affected : ID: 8e827912-a0ef-11ea-826c-00163e4843d7 Type: ClusterAction group CREATE_HOST with role type ADMIN 2020-09-24 10:36:36,666+03 INFO [org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-23) [7b77f4da] Before acquiring and wait lock 'EngineLock:{exclusiveLocks='[8e7c3f2a-a0ef-11ea-971b-00163e4843d7=REGISTER_VDS]', sharedLocks=''}' 2020-09-24 10:36:36,666+03 INFO [org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-23) [7b77f4da] Lock-wait acquired to object 'EngineLock:{exclusiveLocks='[8e7c3f2a-a0ef-11ea-971b-00163e4843d7=REGISTER_VDS]', sharedLocks=''}' 2020-09-24 10:36:36,667+03 INFO [org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-23) [7b77f4da] Running command: AddVdsSpmIdCommand internal: true. Entities affected : ID: 3a5cbd19-82b7-41ce-870b-5b65184934c9 Type: VDS 2020-09-24 10:36:36,674+03 INFO [org.ovirt.engine.core.bll.AddVdsSpmIdCommand] (default task-23) [7b77f4da] Lock freed to object 'EngineLock:{exclusiveLocks='[8e7c3f2a-a0ef-11ea-971b-00163e4843d7=REGISTER_VDS]', sharedLocks=''}' 2020-09-24 10:36:36,678+03 INFO [org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-23) [7b77f4da] START, RemoveVdsVDSCommand(HostName = node2.kvm.test.s1.eirc, RemoveVdsVDSCommandParameters:{hostId='3a5cbd19-82b7-41ce-870b-5b65184934c9'}), log id: 7b990f6d 2020-09-24 10:36:36,678+03 INFO [org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-23) [7b77f4da] FINISH, RemoveVdsVDSCommand, return: , log id: 7b990f6d 2020-09-24 10:36:36,680+03 INFO [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-23) [7b77f4da] START, AddVdsVDSCommand(HostName = node2.kvm.test.s1.eirc, AddVdsVDSCommandParameters:{hostId='3a5cbd19-82b7-41ce-870b-5b65184934c9'}), log id: 20f7b449 2020-09-24 10:36:36,682+03 INFO [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-23) [7b77f4da] AddVds - entered , starting logic to add VDS '3a5cbd19-82b7-41ce-870b-5b65184934c9' 2020-09-24 10:36:36,684+03 INFO [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-23) [7b77f4da] AddVds - VDS '3a5cbd19-82b7-41ce-870b-5b65184934c9' was added, will try to add it to the resource manager 2020-09-24 10:36:36,684+03 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (default task-23) [7b77f4da] Entered VdsManager constructor 2020-09-24 10:36:36,693+03 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (default task-23) [7b77f4da] Initialize vdsBroker 'node2.kvm.test.s1.eirc:54321' 2020-09-24 10:36:36,783+03 INFO [org.ovirt.engine.core.vdsbroker.ResourceManager] (default task-23) [7b77f4da] VDS '3a5cbd19-82b7-41ce-870b-5b65184934c9' was added to the Resource Manager 2020-09-24 10:36:36,783+03 INFO [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-23) [7b77f4da] FINISH, AddVdsVDSCommand, return: , log id: 20f7b449 2020-09-24 10:36:36,790+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-23) [7b77f4da] EVENT_ID: VDS_ALERT_FENCE_IS_NOT_CONFIGURED(9,000), Failed to verify Power Management configuration for Host node2.kvm.test.s1.eirc. 2020-09-24 10:36:36,805+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-23) [7b77f4da] EVENT_ID: USER_ADD_VDS(42), Host node2.kvm.test.s1.eirc was added by admin@internal-authz. 2020-09-24 10:36:36,824+03 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Lock Acquired to object 'EngineLock:{exclusiveLocks='[3a5cbd19-82b7-41ce-870b-5b65184934c9=VDS]', sharedLocks=''}' 2020-09-24 10:36:36,830+03 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Running command: InstallVdsInternalCommand internal: true. Entities affected : ID: 3a5cbd19-82b7-41ce-870b-5b65184934c9 Type: VDS 2020-09-24 10:36:36,830+03 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Before Installation host 3a5cbd19-82b7-41ce-870b-5b65184934c9, node2.kvm.test.s1.eirc 2020-09-24 10:36:36,832+03 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] START, SetVdsStatusVDSCommand(HostName = node2.kvm.test.s1.eirc, SetVdsStatusVDSCommandParameters:{hostId='3a5cbd19-82b7-41ce-870b-5b65184934c9', status='Installing', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2b846a38 2020-09-24 10:36:36,835+03 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] FINISH, SetVdsStatusVDSCommand, return: , log id: 2b846a38 2020-09-24 10:36:36,842+03 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Opening ssh-copy-id session on host node2.kvm.test.s1.eirc 2020-09-24 10:36:37,058+03 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Executing ssh-copy-id command on host node2.kvm.test.s1.eirc 2020-09-24 10:36:37,969+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] EVENT_ID: VDS_ANSIBLE_INSTALL_STARTED(560), Ansible host-deploy playbook execution has started on host node2.kvm.test.s1.eirc. 2020-09-24 10:36:37,986+03 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Exception: Internal server error 2020-09-24 10:36:37,987+03 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Host installation failed for host '3a5cbd19-82b7-41ce-870b-5b65184934c9', 'node2.kvm.test.s1.eirc': Failed to execute Ansible host-deploy role: Internal server error. Please check logs for more details: /var/log/ovirt-engine/ansible-runner-service.log 2020-09-24 10:36:37,989+03 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] START, SetVdsStatusVDSCommand(HostName = node2.kvm.test.s1.eirc, SetVdsStatusVDSCommandParameters:{hostId='3a5cbd19-82b7-41ce-870b-5b65184934c9', status='InstallFailed', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 3f5bca62 2020-09-24 10:36:37,994+03 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] FINISH, SetVdsStatusVDSCommand, return: , log id: 3f5bca62 2020-09-24 10:36:37,997+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] EVENT_ID: VDS_INSTALL_FAILED(505), Host node2.kvm.test.s1.eirc installation failed. Failed to execute Ansible host-deploy role: Internal server error. Please check logs for more details: /var/log/ovirt-engine/ansible-runner-service.log. 2020-09-24 10:36:38,001+03 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1271) [5459582a] Lock freed to object 'EngineLock:{exclusiveLocks='[3a5cbd19-82b7-41ce-870b-5b65184934c9=VDS]', sharedLocks=''}' P.S. Sorry. This is google translate..

3 4