- Users - oVirt List Archives

VM import doesn't see VMs on storage
by Dmitry Filonov 04 Jun '19

04 Jun '19

Hi, I have 2 independent oVirt datacenters. Need to move some of the VMs from DC1 to DC2. So far the strategy was as simple as this - 1) connect new storage domain (NFS) to DC1 2) move VM disks to that storage 3) shut down VMs 4) disconnect storage from DC1 5) import same storage into DC2 6) import VMs from that storage and optionally move VM disks to storage local to DC2. Works fine for a dozen VMs until last Friday when I tried to import another 13 VMs into DC2 and VM import shows only 6. I can see disks in Disk import tab, but not VMs. I guess this is related to the fact that some of the VMs to be moved are based on a template that is still on DC1. But how do I move these VMs then? I can't move the template as 1) I still need it in DC1 2) it doesn't have any disks attached, so I can't really do the same steps to move it. Any ideas are very welcome here. Thanks a lot. -- Dmitry Filonov Linux Administrator SBGrid Core | Harvard Medical School 250 Longwood Ave, SGM-114 Boston, MA 02115

2 3

Feature Request: oVirt to warn when VDO is getting full
by Strahil 04 Jun '19

04 Jun '19

Hello All, I would like to ask how many of you use VDO before asking the oVirt Devs to assess a feature in oVirt for monitoring the size of the VDOs on hyperconverged systems. I think such warning, will save a lot of headaches, but it will not be usefull if most of the community is not using VDO at all. Best Regards, Strahil Nikolov

3 2

SSO problem for Window 7 VM (64)
by Harry Conings 04 Jun '19

04 Jun '19

Hi i am new to oVirt so i think i am missing something. I my case ovirt-engine-extension-aaa-ldap-setup did not work and i am not a domain administrator so i had to set it up by hand I can login with my AD user into the VM portal but SSO to a windows 7 machine does not happen Thks for your help rgds Harry my files: in /etc/ovirt-engine/aaa/zkf200mut.prd.properties vars.user = CN=HARRY (Adm),OU=Administrative Accounts,OU=Operations,OU=203,DC=zkf200mut,DC=prd vars.password = password pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} pool.default.serverset.type = single pool.default.serverset.single.server = 10.63.123.22 pool.default.dc-resolve.default.serverset.type = single pool.default.dc-resolve.serverset.single.server = 10.63.123.22 pool.default.socketfactory.type = java /etc/ovirt-engine/extensions.d/zkf200mut.prd-authn.properties ovirt.engine.extension.name = zkf200mut.prd-authn ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.ldap ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.ldap.AuthnExtension ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Authn ovirt.engine.aaa.authn.profile.name = zkf200mut.prd ovirt.engine.aaa.authn.authz.plugin = zkf200mut.prd config.profile.file.1 = ../aaa/zkf200mut.prd.properties /etc/ovirt-engine/extensions.d/zkf200mut.prd.properties ovirt.engine.extension.name = zkf200mut.prd ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.ldap ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.ldap.AuthzExtension ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Authz config.profile.file.1 = ../aaa/zkf200mut.prd.properties engine.log -> when i login and click on the console of the VM 2019-06-04 12:24:30,442+02 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-8) [354a4756] Running command: TerminateSessionsForTokenCommand internal: true. 2019-06-04 12:24:46,247+02 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-7) [] User m203hcon(a)zkf200mut.prd successfully logged in with scopes: ovirt-app-admin ovirt-app-api ovirt-app-portal ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-06-04 12:24:46,316+02 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-7) [d7805c4] Running command: CreateUserSessionCommand internal: false. 2019-06-04 12:24:46,331+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-7) [d7805c4] EVENT_ID: USER_VDC_LOGIN(30), User m203hcon@zkf200mut.prd@zkf200mut.prd connecting from '10.63.120.199' using session 'CGIKs/CP4HQdLoUhWAzsq996BKkMcKDrqdfHT1x/kIBzixxbNl/hle8BZCZmS2L/ehVZdoStH2JByXragQxeqw==' logged in. 2019-06-04 12:24:47,015+02 ERROR [org.ovirt.engine.core.bll.GetPermissionsForObjectQuery] (default task-3) [1e271632-b9f4-4bcc-8205-ccd8ff1421f6] Query execution failed due to insufficient permissions. 2019-06-04 12:24:47,017+02 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-3) [] Operation Failed: query execution failed due to insufficient permissions. 2019-06-04 12:24:50,106+02 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (default task-8) [6f85887f] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 3985528e-5bd3-4d87-b766-361c7985788f Type: VMAction group CONNECT_TO_VM with role type USER 2019-06-04 12:24:50,118+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-8) [6f85887f] START, SetVmTicketVDSCommand(HostName = ovirtServer1.zkf200mut.prd, SetVmTicketVDSCommandParameters:{hostId='d28491ac-2c3b-4462-b24b-1c673155c644', vmId='3985528e-5bd3-4d87-b766-361c7985788f', protocol='SPICE', ticket='PzMAJhjN75ij', validTime='120', userName='m203hcon(a)zkf200mut.prd', userId='12f092ed-db4c-4ed0-b4bb-f3051c4fc677', disconnectAction='LOCK_SCREEN'}), log id: 103ea2 2019-06-04 12:24:50,150+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-8) [6f85887f] FINISH, SetVmTicketVDSCommand, return: , log id: 103ea2 2019-06-04 12:24:50,168+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [6f85887f] EVENT_ID: VM_SET_TICKET(164), User m203hcon@zkf200mut.prd@zkf200mut.prd initiated console session for VM W203YZ001V

1 0

Re: [External] Re: ovirt metrics - vm dashboard not working
by Jayme 04 Jun '19

04 Jun '19

I just get a blank output from that command. I'm running oVirt Node NG 4.3.3.1 hosts On Mon, Jun 3, 2019 at 3:48 PM Morris, Roy <roy.morris(a)ventura.org> wrote: > Jayme, > > > > Can you run the following command and report back with the results? > > > > #systemctl status selinux* -l > > > > Best regards, > > Roy Morris > > GSA Virtualization Systems Analyst > > County of Ventura > > (805) 654-3625 > > (805) 603-9403 > > [image: cid:7c03dd9d67a9cfb78447b56087323d91a66d7c29.camel@ventura.org] > > > > *From:* Jayme <jaymef(a)gmail.com> > *Sent:* Monday, June 3, 2019 11:40 AM > *To:* users <users(a)ovirt.org> > *Subject:* [External] [ovirt-users] Re: ovirt metrics - vm dashboard not > working > > > > *CAUTION: *This email contains links. If it looks suspicious or is not > expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org > . > > > > > I'm seeing this in the journal for collectd on all of my hosts: > > > > collectd[18380]: write_syslog plugin: error with wr_send_message > collectd[18380]: write_syslog plugin: Connecting to localhost:44514 > failed. The last error was: Connection refused > collectd[18380]: write_syslog plugin: wr_callback_init failed. > collectd[18380]: write_syslog plugin: error with wr_send_message > collectd[18380]: write_syslog plugin: send failed with status -1 > (Connection reset by peer) > collectd[18380]: write_syslog plugin: error with wr_send_message > collectd[18380]: write_syslog plugin: send failed with status -1 > (Connection reset by peer) > > > > collectd and rsyslog are running, I tried restarting both. I can also > telnet to port 44514 on localhost and it's responding. > > > > > > On Mon, Jun 3, 2019 at 3:12 PM Jayme <jaymef(a)gmail.com> wrote: > > I finally managed to get oVirt metrics store running. I loaded sample > dashboards, searches and visualizations in to Kibana from > /etc/ovirt-engine-metrics/dashboards-examples. When importing searches and > visualizations there are warnings about missing index patterns. > > > > It appears that the "VM" dashboard is completely broken, no stats are > showing on it at all including simple stats such as running VM count. > > > > The other two dashboards Hosts and System are working and showing all > stats (sans VM count on the host dashboard). > > > > I believe I have a cash here of either missing indexes or potentially an > issue with the example dashboards? I can see that collectd is running on > all hosts and has the virt plugin loaded. > > > > What part of the config is responsible for suppling the VM > information/indexes? > >

2 2

Uploading disk images (oVirt 4.3.3.1)
by adrianquintero＠gmail.com 03 Jun '19

03 Jun '19

Hi, I have an issue while trying to upload disk images thru the Web UI. "Connection to ovirt-imageio-proxy service has failed. Make sure the service is installed, configured, and ovirt-engine certificate is registered as a valid CA in the browser." My ovirt engine's fqdn is ovirt-engine.mydomain.com however due to network restrictions I had to set rules in order to reach our ovirt-engine ovirt-engine.mydomain.com = 192.168.0.45 For example ovirt-engine.mydomain.otherstuff.com - 192.168.10.109:80, 192.168.10.109:443, 192.168.0.45:80 So as you can see I need to hit the ovirt-engine using ovirt-engine.mydomain.otherstuff.com which I am able to by modifyting the 11-setup-sso.conf file and adding "SSO_ENGINE_URL="https://ovirt-engine.mydomain.otherstuff.com:443/ovirt-engine/" I am able to upload disk images when using http://ovirt-engine.mydomain.com but not able to http://ovirt-engine.mydomain.otherstuff.com I know it might be related to the certificates but I need to be able to upload disk images using both URLs. any ideas?

3 6

ovirt metrics - vm dashboard not working
by Jayme 03 Jun '19

03 Jun '19

I finally managed to get oVirt metrics store running. I loaded sample dashboards, searches and visualizations in to Kibana from /etc/ovirt-engine-metrics/dashboards-examples. When importing searches and visualizations there are warnings about missing index patterns. It appears that the "VM" dashboard is completely broken, no stats are showing on it at all including simple stats such as running VM count. The other two dashboards Hosts and System are working and showing all stats (sans VM count on the host dashboard). I believe I have a cash here of either missing indexes or potentially an issue with the example dashboards? I can see that collectd is running on all hosts and has the virt plugin loaded. What part of the config is responsible for suppling the VM information/indexes?

2 2

Re: option to remove a specific VM greyed out
by Strahil 03 Jun '19

03 Jun '19

Maybe, there is a deletion protection? Just go to edit and uncheck it. Best Regards, Strahil NikolovOn Jun 3, 2019 17:46, Jayme <jaymef(a)gmail.com> wrote: > > Running latest stable 4.3. I have one particular VM that is shutdown but options for removal are greyed out in the admin gui. I tried starting it and shutting it down again but still the options are not-selectable. However, they are for other VMs. > > Any idea what is different about this VM that is preventing removal from the GUI? > >

1 0

option to remove a specific VM greyed out
by Jayme 03 Jun '19

03 Jun '19

Running latest stable 4.3. I have one particular VM that is shutdown but options for removal are greyed out in the admin gui. I tried starting it and shutting it down again but still the options are not-selectable. However, they are for other VMs. Any idea what is different about this VM that is preventing removal from the GUI?

2 2

Re: Gluster Deployment Failed - No Medium Found
by Strahil 03 Jun '19

03 Jun '19

Aanother option - you do not have blacklist section in multipath (requires rebuild of initramfs + reboot). Best Regards, Strahil NikolovOn Jun 3, 2019 14:49, Sachidananda URS <surs(a)redhat.com> wrote: > > Hi Stephen, > > > On Mon, Jun 3, 2019 at 3:57 PM <smcintosh(a)tradeprint.co.uk> wrote: >> >> Good Morning, >> >> I'm completely new to this and I'm testing setting up a Gluster environment with Ovirt. However, my deployment keeps fails and I don't understand what it means. Any assistance would be much appreciated. Please see error below... >> >> Error Message >> >> TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** >> failed: [ov1.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} > > > One of the reasons for this is, the device could be having an existing partition table information. > > Can you please run the command: > > wipefs -a /dev/sdb > > On all the nodes and try again? > > -sachi >

1 0

Westmere CPU Family
by Vrgotic, Marko 03 Jun '19

03 Jun '19

Dear oVirt, For a strange reason I am convinced I have read somewhere that with 4.3 oVirt, the CPU family Westmere will not be supported any longer. Still, I see it in dropdown list after upgradingfrom 4.2 to 4.3, also after installing fresh 4.3. I also see it in oVirt documentation. Can someone tell me if its actually supported and if its going to be “discontinued” in 4.4 maybe? Thank you. Marko Vrgotic ActiveVideo

2 1

Gluster Deployment Failed - No Medium Found
by smcintosh＠tradeprint.co.uk 03 Jun '19

03 Jun '19

Good Morning, I'm completely new to this and I'm testing setting up a Gluster environment with Ovirt. However, my deployment keeps fails and I don't understand what it means. Any assistance would be much appreciated. Please see error below... Error Message TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** failed: [ov1.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} failed: [ov3.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} failed: [ov2.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* to retry, use: --limit @/usr/share/cockpit/ovirt-dashboard/ansible/hc_wizard.retry PLAY RECAP ********************************************************************* ov1.test1.lan : ok=10 changed=0 unreachable=0 failed=1 ov2.test1.lan : ok=10 changed=0 unreachable=0 failed=1 ov3.test1.lan : ok=10 changed=0 unreachable=0 failed=1 Any assistance would be much appreciated. Regards Stephen

2 1

Nvme over fabric array support through OVirt MANAGED_BLOCK_STORAGE Domain
by amit1.kumar＠intel.com 03 Jun '19

03 Jun '19

for an NVMe over fabric storage array that supports Cinder backend plugin, is it possible to use MANAGED_BLOCK_STORAGE domain to configure Virtual disk? in this case, is it required to have a single Virtual disk accessible from all the VDSM hosts (within the cluster) to support VM migration? Thanks, Amit

3 4

Re: libvirt memory leak?
by Strahil 02 Jun '19

02 Jun '19

Hi Alex, As a sys admin - I would rexommend to thoroughly check the 'journalctl' if it is permanent. If not - check libvirt logs (/var/log/something/qemu/VM-name.log -> this is based on memory). Also, if you run out of memory - the OOM killer kicked in and it will be reporting details kn /var/log/messages. Best Regards, Strahil NikolovOn Jun 2, 2019 06:37, Alex McWhirter <alex(a)triadic.us> wrote: > > After moving from 4.2 -> 4.3 libvirtd seems to be leaking memory, it > recently crashed a host by eating 123GB of RAM. Seems to follow one > specific VM around, this is the only VM i have created since 4.3, the > others were all made in 4.2 them upgraded to 4.3 > > What logs would be applicable? > > Libvirt 4.5.0 > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SB75R63BMUEWC…

1 0

Re: Uploading disk images (oVirt 4.3.3.1)
by Strahil 02 Jun '19

02 Jun '19

If you can, edit your /etc/hosts (linux client browsing the web) to point 'engine.mydomain.otherstuff.com' to the IP of the engine. I'm using the same approach but from windows and it worka for me. I am not sure but a CNAME in DNS should also work, but someone more experienced should step in. Best Regards, Strahil NikolovOn May 31, 2019 23:55, adrianquintero(a)gmail.com wrote: > > Hi, > I have an issue while trying to upload disk images thru the Web UI. > "Connection to ovirt-imageio-proxy service has failed. Make sure the service is installed, configured, and ovirt-engine certificate is registered as a valid CA in the browser." > > My ovirt engine's fqdn is ovirt-engine.mydomain.com however due to network restrictions I had to set rules in order to reach our ovirt-engine > ovirt-engine.mydomain.com = 192.168.0.45 > > For example ovirt-engine.mydomain.otherstuff.com - 192.168.10.109:80, 192.168.10.109:443, 192.168.0.45:80 > So as you can see I need to hit the ovirt-engine using ovirt-engine.mydomain.otherstuff.com which I am able to by modifyting the 11-setup-sso.conf file and adding "SSO_ENGINE_URL="https://ovirt-engine.mydomain.otherstuff.com:443/ovirt-engine/" > > I am able to upload disk images when using http://ovirt-engine.mydomain.com but not able to http://ovirt-engine.mydomain.otherstuff.com > I know it might be related to the certificates but I need to be able to upload disk images using both URLs. > > any ideas? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QSQKTZ6YCD7XB…

1 0

Re: possible to clear vm started under different name warning in gui?
by Strahil 02 Jun '19

02 Jun '19

KVM allows the config to be updated when the feature cannot be done live. The 'poweron' is the only time KVM reads the configuration files. In our case, vdsm completely destroys the VM (virsh undefine) during poweroff and creates the VM (virsh define) during poweron. When using 'reboot' the KVM process never stops - so from Virtualization perspective , the VM never stops and thus no reread of the config. Best Regards, Strahil NikolovOn May 31, 2019 16:58, Jayme <jaymef(a)gmail.com> wrote: > > Thanks, I feel silly for not figuring that out but it looks like a full shutdown/power-off resolved it. I was only doing reboots previously. > > On Fri, May 31, 2019 at 10:47 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Have you tried to power off and then power on the VM ? >> >> Best Regards, >> Strahil Nikolov >> >> В петък, 31 май 2019 г., 8:59:54 ч. Гринуич-4, Jayme <jaymef(a)gmail.com> написа: >> >> >> When a VM is renamed a warning in engine gui appears with an exclamation point stating "vm was started with a different name". Is there a way to clear this warning? The VM has been restarted a few times since but it doesn't go away. >> >> Thanks! >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FLA643IOFHYXZ…

1 0

libvirt memory leak?
by Alex McWhirter 02 Jun '19

02 Jun '19

After moving from 4.2 -> 4.3 libvirtd seems to be leaking memory, it recently crashed a host by eating 123GB of RAM. Seems to follow one specific VM around, this is the only VM i have created since 4.3, the others were all made in 4.2 them upgraded to 4.3 What logs would be applicable? Libvirt 4.5.0

1 0

Ovirt-egine integration with OpenLDAP can't seem to find any users on Web-UI
by rubennunes12＠gmail.com 31 May '19

31 May '19

Hello everyone. So i don't know what i'm doing wrong but this doesn't seem to work, i already made the confgurations needed on the ovirt-engine-extension-aaa-ldap i'm a little desperate here. I'm going to put all the commands that i already made and the errors that they give: - ovirt-engine-extension-aaa-ldap-setup Stage: Setup validation NOTE: It is highly recommended to test drive the configuration before applying it into engine. Login sequence is executed automatically, but it is recommended to also execute Search sequence manually after successful Login sequence. Please provide credentials to test login flow: Enter user name: node1 Enter user password: [ INFO ] Executing login sequence... Login output: 2019-05-29 03:45:59,261+01 INFO ======================================================================== 2019-05-29 03:45:59,301+01 INFO ============================ Initialization ============================ 2019-05-29 03:45:59,301+01 INFO ======================================================================== 2019-05-29 03:45:59,385+01 INFO Loading extension '192.168.16.114-authn' 2019-05-29 03:45:59,540+01 INFO Extension '192.168.16.114-authn' loaded 2019-05-29 03:45:59,571+01 INFO Loading extension '192.168.16.114' 2019-05-29 03:45:59,585+01 INFO Extension '192.168.16.114' loaded 2019-05-29 03:45:59,585+01 INFO Initializing extension '192.168.16.114-authn' 2019-05-29 03:45:59,588+01 INFO [ovirt-engine-extension-aaa-ldap.authn::192.168.16.114-authn] Creating LDAP pool 'authz' 2019-05-29 03:45:59,734+01 INFO [ovirt-engine-extension-aaa-ldap.authn::192.168.16.114-authn] LDAP pool 'authz' information: vendor='null' version='null' 2019-05-29 03:45:59,736+01 INFO [ovirt-engine-extension-aaa-ldap.authn::192.168.16.114-authn] Creating LDAP pool 'authn' 2019-05-29 03:45:59,754+01 INFO [ovirt-engine-extension-aaa-ldap.authn::192.168.16.114-authn] LDAP pool 'authn' information: vendor='null' version='null' 2019-05-29 03:45:59,754+01 INFO Extension '192.168.16.114-authn' initialized 2019-05-29 03:45:59,755+01 INFO Initializing extension '192.168.16.114' 2019-05-29 03:45:59,756+01 INFO [ovirt-engine-extension-aaa-ldap.authz::192.168.16.114] Creating LDAP pool 'authz' 2019-05-29 03:45:59,775+01 INFO [ovirt-engine-extension-aaa-ldap.authz::192.168.16.114] LDAP pool 'authz' information: vendor='null' version='null' 2019-05-29 03:45:59,776+01 INFO [ovirt-engine-extension-aaa-ldap.authz::192.168.16.114] Available Namespaces: [ou=People,dc=lab,dc=local] 2019-05-29 03:45:59,777+01 INFO Extension '192.168.16.114' initialized 2019-05-29 03:45:59,777+01 INFO Start of enabled extensions list 2019-05-29 03:45:59,777+01 INFO Instance name: '192.168.16.114-authn', Extension name: 'ovirt-engine-extension-aaa-ldap.authn', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmp7wX6s6/extensions.d/192.168.16.114-authn.properties', Initialized: 'true' 2019-05-29 03:45:59,778+01 INFO Instance name: '192.168.16.114', Extension name: 'ovirt-engine-extension-aaa-ldap.authz', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmp7wX6s6/extensions.d/192.168.16.114.properties', Initialized: 'true' 2019-05-29 03:45:59,778+01 INFO End of enabled extensions list 2019-05-29 03:45:59,778+01 INFO ======================================================================== 2019-05-29 03:45:59,778+01 INFO ============================== Execution =============================== 2019-05-29 03:45:59,778+01 INFO ======================================================================== 2019-05-29 03:45:59,779+01 INFO Iteration: 0 2019-05-29 03:45:59,780+01 INFO Profile='192.168.16.114' authn='192.168.16.114-authn' authz='192.168.16.114' mapping='null' 2019-05-29 03:45:59,780+01 INFO API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='192.168.16.114' user='node1' 2019-05-29 03:45:59,835+01 INFO API: <--Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='192.168.16.114' result=CREDENTIALS_INVALID 2019-05-29 03:45:59,843+01 SEVERE Authn.Result code is: CREDENTIALS_INVALID [ ERROR ] Login sequence failed Please investigate details of the failure (search for lines containing SEVERE log level). Select test sequence to execute (Done, Abort, Login, Search) [Abort]: - ovirt-engine-extensions-tool aaa login-user --profile=lab.local --user-name=node1 2019-05-29 03:57:35,194+01 INFO ======================================================================== 2019-05-29 03:57:35,224+01 INFO ============================ Initialization ============================ 2019-05-29 03:57:35,224+01 INFO ======================================================================== 2019-05-29 03:57:35,298+01 INFO Loading extension 'internal-authz' 2019-05-29 03:57:35,325+01 INFO Extension 'internal-authz' loaded 2019-05-29 03:57:35,334+01 INFO Loading extension 'internal-authn' 2019-05-29 03:57:35,336+01 INFO Extension 'internal-authn' loaded 2019-05-29 03:57:35,360+01 INFO Loading extension 'profile2-authz' 2019-05-29 03:57:35,510+01 INFO Extension 'profile2-authz' loaded 2019-05-29 03:57:35,516+01 INFO Loading extension 'profile1-authz' 2019-05-29 03:57:35,527+01 INFO Extension 'profile1-authz' loaded 2019-05-29 03:57:35,546+01 INFO Loading extension 'profile1-authn' 2019-05-29 03:57:35,558+01 INFO Extension 'profile1-authn' loaded 2019-05-29 03:57:35,586+01 INFO Loading extension 'profile2-authn' 2019-05-29 03:57:35,592+01 INFO Extension 'profile2-authn' loaded 2019-05-29 03:57:35,592+01 INFO Initializing extension 'internal-authz' 2019-05-29 03:57:35,754+01 INFO Extension 'internal-authz' initialized 2019-05-29 03:57:35,755+01 INFO Initializing extension 'internal-authn' 2019-05-29 03:57:35,771+01 INFO Extension 'internal-authn' initialized 2019-05-29 03:57:35,771+01 INFO Initializing extension 'profile2-authz' 2019-05-29 03:57:35,772+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile2-authz] Creating LDAP pool 'authz' 2019-05-29 03:57:35,859+01 WARNING Exception: An error occurred while attempting to connect to server ldap.lab.local:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap.lab.local/192.168.16.114:389: UnknownHostException(ldap.lab.local), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58')) 2019-05-29 03:57:35,861+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile2-authz] Available Namespaces: [dc=lab,dc=local] 2019-05-29 03:57:35,861+01 INFO Extension 'profile2-authz' initialized 2019-05-29 03:57:35,861+01 INFO Initializing extension 'profile1-authz' 2019-05-29 03:57:35,862+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile1-authz] Creating LDAP pool 'authz' 2019-05-29 03:57:35,873+01 WARNING Exception: An error occurred while attempting to connect to server 40.127.205.63:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server /40.127.205.63:389: IllegalArgumentException(trace='checkAddress(ResolverSocketFactory.java:35) / createSocket(ResolverSocketFactory.java:73) / run(ConnectThread.java:139)', ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58)')) 2019-05-29 03:57:35,874+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile1-authz] Available Namespaces: [dc=sybase,dc=pt] 2019-05-29 03:57:35,874+01 INFO Extension 'profile1-authz' initialized 2019-05-29 03:57:35,874+01 INFO Initializing extension 'profile1-authn' 2019-05-29 03:57:35,875+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile1-authn] Creating LDAP pool 'authz' 2019-05-29 03:57:35,888+01 WARNING Exception: An error occurred while attempting to connect to server 40.127.205.63:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server /40.127.205.63:389: IllegalArgumentException(trace='checkAddress(ResolverSocketFactory.java:35) / createSocket(ResolverSocketFactory.java:73) / run(ConnectThread.java:139)', ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58)')) 2019-05-29 03:57:35,889+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile1-authn] Creating LDAP pool 'authn' 2019-05-29 03:57:35,894+01 WARNING Exception: An error occurred while attempting to connect to server 40.127.205.63:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server /40.127.205.63:389: IllegalArgumentException(trace='checkAddress(ResolverSocketFactory.java:35) / createSocket(ResolverSocketFactory.java:73) / run(ConnectThread.java:139)', ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58)')) 2019-05-29 03:57:35,894+01 INFO Extension 'profile1-authn' initialized 2019-05-29 03:57:35,894+01 INFO Initializing extension 'profile2-authn' 2019-05-29 03:57:35,895+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile2-authn] Creating LDAP pool 'authz' ^C2019-05-29 03:57:35,906+01 WARNING Exception: An error occurred while attempting to connect to server ldap.lab.local:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap.lab.local/192.168.16.114:389: UnknownHostException(ldap.lab.local), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58')) 2019-05-29 03:57:35,907+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile2-authn] Creating LDAP pool 'authn' [root@ovirt ~]# ovirt-engine-extensions-tool aaa login-user --profile=lab.local --user-name=node1 2019-05-29 03:57:41,227+01 INFO ======================================================================== 2019-05-29 03:57:41,259+01 INFO ============================ Initialization ============================ 2019-05-29 03:57:41,260+01 INFO ======================================================================== 2019-05-29 03:57:41,311+01 INFO Loading extension 'internal-authz' 2019-05-29 03:57:41,331+01 INFO Extension 'internal-authz' loaded 2019-05-29 03:57:41,333+01 INFO Loading extension 'internal-authn' 2019-05-29 03:57:41,334+01 INFO Extension 'internal-authn' loaded 2019-05-29 03:57:41,345+01 INFO Loading extension 'profile2-authz' 2019-05-29 03:57:41,508+01 INFO Extension 'profile2-authz' loaded 2019-05-29 03:57:41,510+01 INFO Loading extension 'profile1-authz' 2019-05-29 03:57:41,551+01 INFO Extension 'profile1-authz' loaded 2019-05-29 03:57:41,552+01 INFO Loading extension 'profile1-authn' 2019-05-29 03:57:41,562+01 INFO Extension 'profile1-authn' loaded 2019-05-29 03:57:41,564+01 INFO Loading extension 'profile2-authn' 2019-05-29 03:57:41,602+01 INFO Extension 'profile2-authn' loaded 2019-05-29 03:57:41,602+01 INFO Initializing extension 'internal-authz' 2019-05-29 03:57:41,782+01 INFO Extension 'internal-authz' initialized 2019-05-29 03:57:41,783+01 INFO Initializing extension 'internal-authn' 2019-05-29 03:57:41,800+01 INFO Extension 'internal-authn' initialized 2019-05-29 03:57:41,801+01 INFO Initializing extension 'profile2-authz' 2019-05-29 03:57:41,801+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile2-authz] Creating LDAP pool 'authz' 2019-05-29 03:57:41,885+01 WARNING Exception: An error occurred while attempting to connect to server ldap.lab.local:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap.lab.local/192.168.16.114:389: UnknownHostException(ldap.lab.local), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58')) 2019-05-29 03:57:41,886+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile2-authz] Available Namespaces: [dc=lab,dc=local] 2019-05-29 03:57:41,887+01 INFO Extension 'profile2-authz' initialized 2019-05-29 03:57:41,887+01 INFO Initializing extension 'profile1-authz' 2019-05-29 03:57:41,887+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile1-authz] Creating LDAP pool 'authz' 2019-05-29 03:57:41,901+01 WARNING Exception: An error occurred while attempting to connect to server 40.127.205.63:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server /40.127.205.63:389: IllegalArgumentException(trace='checkAddress(ResolverSocketFactory.java:35) / createSocket(ResolverSocketFactory.java:73) / run(ConnectThread.java:139)', ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58)')) 2019-05-29 03:57:41,901+01 INFO [ovirt-engine-extension-aaa-ldap.authz::profile1-authz] Available Namespaces: [dc=sybase,dc=pt] 2019-05-29 03:57:41,902+01 INFO Extension 'profile1-authz' initialized 2019-05-29 03:57:41,902+01 INFO Initializing extension 'profile1-authn' 2019-05-29 03:57:41,902+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile1-authn] Creating LDAP pool 'authz' 2019-05-29 03:57:41,909+01 WARNING Exception: An error occurred while attempting to connect to server 40.127.205.63:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server /40.127.205.63:389: IllegalArgumentException(trace='checkAddress(ResolverSocketFactory.java:35) / createSocket(ResolverSocketFactory.java:73) / run(ConnectThread.java:139)', ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58)')) 2019-05-29 03:57:41,910+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile1-authn] Creating LDAP pool 'authn' 2019-05-29 03:57:41,915+01 WARNING Exception: An error occurred while attempting to connect to server 40.127.205.63:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server /40.127.205.63:389: IllegalArgumentException(trace='checkAddress(ResolverSocketFactory.java:35) / createSocket(ResolverSocketFactory.java:73) / run(ConnectThread.java:139)', ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58)')) 2019-05-29 03:57:41,916+01 INFO Extension 'profile1-authn' initialized 2019-05-29 03:57:41,916+01 INFO Initializing extension 'profile2-authn' 2019-05-29 03:57:41,917+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile2-authn] Creating LDAP pool 'authz' 2019-05-29 03:57:41,962+01 WARNING Exception: An error occurred while attempting to connect to server ldap.lab.local:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap.lab.local/192.168.16.114:389: UnknownHostException(ldap.lab.local), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58')) 2019-05-29 03:57:41,963+01 INFO [ovirt-engine-extension-aaa-ldap.authn::profile2-authn] Creating LDAP pool 'authn' 2019-05-29 03:57:42,010+01 WARNING Exception: An error occurred while attempting to connect to server ldap.lab.local:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap.lab.local/192.168.16.114:389: UnknownHostException(ldap.lab.local), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58')) 2019-05-29 03:57:42,011+01 INFO Extension 'profile2-authn' initialized 2019-05-29 03:57:42,011+01 INFO Start of enabled extensions list 2019-05-29 03:57:42,012+01 INFO Instance name: 'internal-authn', Extension name: '"ovirt-engine-extension-aaa-jdbc".authn', Version: '"1.1.7_master"', Notes: 'Display name: "ovirt-engine-extension-aaa-jdbc"', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/etc/ovirt-engine/extensions.d/internal-authn.properties', Initialized: 'true' 2019-05-29 03:57:42,013+01 INFO Instance name: 'profile1-authn', Extension name: 'ovirt-engine-extension-aaa-ldap.authn', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/etc/ovirt-engine/extensions.d/profile1-authn.properties', Initialized: 'true' 2019-05-29 03:57:42,013+01 INFO Instance name: 'profile2-authz', Extension name: 'ovirt-engine-extension-aaa-ldap.authz', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/etc/ovirt-engine/extensions.d/profile2-authz.properties', Initialized: 'true' 2019-05-29 03:57:42,014+01 INFO Instance name: 'internal-authz', Extension name: '"ovirt-engine-extension-aaa-jdbc".authz', Version: '"1.1.7_master"', Notes: 'Display name: "ovirt-engine-extension-aaa-jdbc"', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/etc/ovirt-engine/extensions.d/internal-authz.properties', Initialized: 'true' 2019-05-29 03:57:42,014+01 INFO Instance name: 'profile1-authz', Extension name: 'ovirt-engine-extension-aaa-ldap.authz', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/etc/ovirt-engine/extensions.d/profile1-authz.properties', Initialized: 'true' 2019-05-29 03:57:42,014+01 INFO Instance name: 'profile2-authn', Extension name: 'ovirt-engine-extension-aaa-ldap.authn', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/etc/ovirt-engine/extensions.d/profile2-authn.properties', Initialized: 'true' 2019-05-29 03:57:42,014+01 INFO End of enabled extensions list 2019-05-29 03:57:42,014+01 INFO ======================================================================== 2019-05-29 03:57:42,014+01 INFO ============================== Execution =============================== 2019-05-29 03:57:42,015+01 INFO ======================================================================== 2019-05-29 03:57:42,015+01 INFO Iteration: 0 2019-05-29 03:57:42,018+01 INFO Profile='lab.local' authn='profile2-authn' authz='profile2-authz' mapping='null' 2019-05-29 03:57:42,018+01 INFO API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='lab.local' user='node1' Password: 2019-05-29 03:57:45,905+01 WARNING Ignoring records from pool: 'authz' 2019-05-29 03:57:45,906+01 INFO API: <--Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='lab.local' result=CREDENTIALS_INVALID 2019-05-29 03:57:45,922+01 SEVERE Authn.Result code is: CREDENTIALS_INVALID - ldapsearch -x -h 192.168.16.114 -b "dc=ldap,dc=local" -D "cn=ldapadm,dc=lab,dc=local" -W Enter LDAP Password: # extended LDIF # # LDAPv3 # base <dc=ldap,dc=local> with scope subtree # filter: (objectclass=*) # requesting: ALL # # search result search: 2 result: 32 No such object # numResponses: 1 - [root@ovirt ~]# cat /etc/ovirt-engine/aaa/profile2.properties # # Select one # include = <openldap.properties> #include = <389ds.properties> #include = <rhds.properties> #include = <ipa.properties> #include = <iplanet.properties> #include = <rfc2307-389ds.properties> #include = <rfc2307-rhds.properties> #include = <rfc2307-openldap.properties> #include = <rfc2307-edir.properties> #include = <rfc2307-generic.properties> # # Server # vars.server = ldap.lab.local # # Search user and its password. # vars.user = ou=People,dc=lab,dc=local vars.password = abc # Uncomment in case you don't have allowed anonymous bind, # because we use anonymous bind for authn pool: pool.default.auth.type = simple pool.default.serverset.srvrecord.service = ldap pool.default.serverset.srvrecord.protocol = tcp pool.default.serverset.single.server = ${global:vars.server} pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} #pool.default.ssl.startTLS = false #pool.default.socketfactory.type = java sequence-init.init.100-my-basedn-init-vars = my-basedn-init-vars sequence.my-basedn-init-vars.010.description = set baseDN sequence.my-basedn-init-vars.010.type = var-set sequence.my-basedn-init-vars.010.var-set.variable = simple_baseDN sequence.my-basedn-init-vars.010.var-set.value = dc=lab,dc=local search.default.search-request.derefPolicy = ALWAYS # Create keystore, import root certificate and uncomment # if using ssl/tls. #pool.default.ssl.startTLS = true #pool.default.ssl.truststore.file = ${local:_basedir}/${global:vars.server}.jks #pool.default.ssl.truststore.password = changeit - [root@ovirt ~]# cat /etc/ovirt-engine/extensions.d/profile2-authn.properties ovirt.engine.extension.name = profile2-authn ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.ldap ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.ldap.AuthnExtension ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Authn ovirt.engine.aaa.authn.profile.name = lab.local ovirt.engine.aaa.authn.authz.plugin = profile2-authz config.profile.file.1 = /etc/ovirt-engine/aaa/profile2.properties config.globals.baseDN.simple_baseDN = ou=People,dc=lab,dc=local - [root@ovirt ~]# cat /etc/ovirt-engine/extensions.d/profile2-authz.properties ovirt.engine.extension.name = profile2-authz ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.ldap ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.ldap.AuthzExtension ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Authz config.profile.file.1 = /etc/ovirt-engine/aaa/profile2.properties config.globals.baseDN.simple_baseDN = ou=People,dc=lab,dc=local Thanks all for the help!

3 20

possible to clear vm started under different name warning in gui?
by Jayme 31 May '19

31 May '19

When a VM is renamed a warning in engine gui appears with an exclamation point stating "vm was started with a different name". Is there a way to clear this warning? The VM has been restarted a few times since but it doesn't go away. Thanks!

2 2

Storage HA for manager on DR environment
by raul.caballero.girol＠gmail.com 31 May '19

31 May '19

Hi, I'm reading this guide to provide Active-Active DR for my environment (2 sites): https://ovirt.org/documentation/disaster-recovery-guide/active_active_overv… I have a sef-hosted environment with a storage domains per site with synchronous replication. I can put all my VM with a storage lease on the other storage site but i can't put the lease on the manager (the option is disable). How I configure the storage HA of my manager?. Regards,

2 5

Re: Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko 31 May '19

31 May '19

Roy, It came down to manually mounting ovirt-storage domains and executing chown command. Still, I took you advice and did NFS3-only and NFS4-only tests. Here are the results: Test1: Protocol NFS3 / ExportPolicy NFS3 with Default (allow all) * ERROR: [ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."} * Volume is mounted as: 172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs (rw,relatime,vers=3,rsize=65536,wsize=655 36,namlen=255,soft,nolock,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=172.17.28.5,mountvers=3,mountport=635,mountproto=udp,loc al_lock=all,addr=172.17.28.5) * ls -la /rhev/data-center/mnt: [root@ovirt-hv-01 mnt]# ls -la total 4 drwxr-xr-x. 3 vdsm kvm 48 May 31 07:55 . drwxr-xr-x. 3 vdsm kvm 17 May 31 07:50 .. drwxrwxr-x. 2 root root 4096 May 29 10:12 172.17.28.5:_ovirt__hosted__engine * change ownership of mounted volume to vdsm:kvm * umount Reran deployment script and deployment completed successfully. Test2: Protocol NFS4 / ExportPolicy NFS with Default (allow all) Deployment went through without single issue. Seems that even though vddm:vm group with an ID 36 are created and added to NetApp volume, they are not applicable. It still required to mount manually, execute “chown -R vdsm:kvm <mounted_location>”, amount and rerun the deployment script or rather reenter storage information for deployment to proceed. Adding next storage domain, fro example for all other test VMs, will again fail from UI, unless the manual mount and chow are executed previously. Then I tried just mount second storage domain, and it failed reporting permission issue (which it was). After executing manual mount actions, adding domain from UI worked flawlessly. Output of mount: 172.17.28.5:/ovirt_production on /rhev/data-center/mnt/172.17.28.5:_ovirt__production type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft, nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.12,local_lock=none,addr=172.17.28.5) 172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=25 5,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.12,local_lock=none,addr=172.17.28.5) Test3: Protocol NFS4 / ExportPolicy NFS with limited IP group access In progress, but I have high hopes now. Will keep you posted. BTW.I was not able to find location in NetApp Volume where squashing is being defined, so I can not answer that one yet. Thank you. Kind regards, Marko Vrgotic ActiveVideo From: "Morris, Roy" <roy.morris(a)ventura.org> Date: Thursday, 30 May 2019 at 21:29 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, "users(a)ovirt.org" <users(a)ovirt.org> Cc: "Stojchev, Darko" <D.Stojchev(a)activevideo.com> Subject: RE: Install fresh 4.3 fails with mounting shared storage Marko, No problem, here are some other things to check as well. NetApp is weird about allowing changes done to the root directory of a share. I would recommend creating a folder on the NetApp share like “rhevstor” or something so that you can chown that folder and mount the folder for the storage domain. I never had much luck mounting and using the root level of the NetApp NFS share. I also have in my notes that I set “sec=sys” as a property of my NetApp data domain which wouldn’t allow me to mount it until I input it into the RHEV manager. However, you aren’t at a point of having the RHEV manager up and running so I’m not sure how much use this would be at the moment. #mount -o sec=sys 172.17.28.5:/rhevstor /mnt/temp NFS share will fail if it isn’t accessible from all hosts, so make sure to go into each host to run #showmount -e 172.17.28.5 The ownership of the NFS share needs to be owned by vdsm:kvm. To do this, you have to manually mount the NFS share to one of the hosts temporarily then run the following command to get ownership settings setup. #mkdir /mnt/temp #mount -o sec=sys 172.17.28.5:/rhevstor /mnt/temp #chown 36:36 /mnt/temp #umount /mnt/temp Then try and run the install again. If it fails, disable NFSv3 and run again to see if it is related to NFSv4 security settings. Best regards, Roy Morris From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com> Sent: Thursday, May 30, 2019 12:07 PM To: Morris, Roy <roy.morris(a)ventura.org>; users(a)ovirt.org Cc: Stojchev, Darko <D.Stojchev(a)activevideo.com> Subject: [External] Re: Install fresh 4.3 fails with mounting shared storage Hi Roy, I will run all those tests tomorrow morning (Amsterdam TimeZone) and reply back with results. Regarding NetApp documentation you mentioned below, I assume it should be enough to just “google” for it. Thank you very much for jumping in, we really appreciate it. Kind regards, Marko Vrgotic From: "Morris, Roy" <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>> Date: Thursday, 30 May 2019 at 18:46 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>> Cc: "users-request(a)ovirt.org<mailto:users-request@ovirt.org>" <users-request(a)ovirt.org<mailto:users-request@ovirt.org>>, "Stojchev, Darko" <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>> Subject: RE: Install fresh 4.3 fails with mounting shared storage Marko, Can you try disabling NFSv4 on the NetApp side for testing and rerun the installer? I don’t advise leaving it at NFSv3 but just for testing we can try it out. Also, there is some documentation on NetApp support regarding manually mounting the NFS share to change permissions then unmount. It has to be done once but after that the mounting should be fine. Do you have root squash set on NetApp? Best regards, Roy Morris GSA Virtualization Systems Analyst County of Ventura (805) 654-3625 (805) 603-9403 [cid:7c03dd9d67a9cfb78447b56087323d91a66d7c29.camel@ventura.org] From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> Sent: Thursday, May 30, 2019 1:34 AM To: Morris, Roy <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>>; users(a)ovirt.org<mailto:users@ovirt.org> Cc: users-request(a)ovirt.org<mailto:users-request@ovirt.org>; Stojchev, Darko <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>> Subject: [External] Re: Install fresh 4.3 fails with mounting shared storage Hi Roy, Sure, here is the output: Last login: Wed May 29 17:25:30 2019 from ovirt-engine.avinity.tv [root@ovirt-hv-03 ~]# showmount -e 172.17.28.5 Export list for 172.17.28.5: / (everyone) [root@ovirt-hv-03 ~]# ls -la /rhev/data-center/mnt/ total 0 drwxr-xr-x. 2 vdsm kvm 6 May 29 17:14 . drwxr-xr-x. 3 vdsm kvm 17 May 29 17:11 .. [root@ovirt-hv-03 ~]# In addition, if it helps, here is the list of shares/mount points from Netapp side, behind the 172.17.28.5 IP: [cid:image003.png@01D516CC.8548AE10] Kind regards Marko Vrgotic From: "Morris, Roy" <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>> Date: Thursday, 30 May 2019 at 00:57 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>> Cc: "users-request(a)ovirt.org<mailto:users-request@ovirt.org>" <users-request(a)ovirt.org<mailto:users-request@ovirt.org>> Subject: RE: Install fresh 4.3 fails with mounting shared storage Marko, Can you run the following commands and let us know the results. showmount -e 172.17.28.5 ls -la /rhev/data-center/mnt/ Best regards, Roy Morris From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> Sent: Wednesday, May 29, 2019 4:07 AM To: users(a)ovirt.org<mailto:users@ovirt.org> Cc: users-request(a)ovirt.org<mailto:users-request@ovirt.org> Subject: [External] [ovirt-users] Install fresh 4.3 fails with mounting shared storage CAUTION: This email contains links. If it looks suspicious or is not expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org<mailto:Spam.Manager@ventura.org>. Dear oVIrt, We are trying to deploy new setup with Hosted-Engine , oVirt version 4.3. Volume is on the Netapp, protocol NFS v4. Upon populating shared storage information and path: Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]: auto Please specify the full shared storage connection path to use (example: host:/path): 172.17.28.5:/ovirt_hosted_engine Following is displayed on the screen: [ INFO ] Creating Storage Domain [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."} Even with this error – storage gets mounted on the Host: 172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5) But playbook execution fails and we can not proceed with install. Please advise. Kindly awaiting your reply. Marko Vrgotic

1 0

oVirt Node Blocks VirtViewer/SPICE connections (Did Not Auto-Configure Firewall?)
by Zachary Winter 31 May '19

31 May '19

I am unable to connect via SPICE (Windows VirtViewer) to VM's running on my compute node. It appears the node did not auto-configure the firewall because the .vv files appear to point to the correct IP address and common ports. Is there a way to re-run/re-execute the firewall auto-configuration now that the node has already been installed? If not, does anyone happen to have firewall-cmd commands handy that I can run to resolve this quickly? Which ports need to be opened? The specs on the node are as follows: OS Version: RHEL - 7 - 6.1810.2.el7.centos OS Description: oVirt Node 4.3.3.1 Kernel Version: 3.10.0 - 957.10.1.el7.x86_64 KVM Version: 2.12.0 - 18.el7_6.3.1 LIBVIRT Version: libvirt-4.5.0-10.el7_6.6 VDSM Version: vdsm-4.30.13-1.el7 SPICE Version: 0.14.0 - 6.el7_6.1 GlusterFS Version: glusterfs-5.5-1.el7 CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.10.1-3.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Enabled

3 2

oVirtSimpleBackup
by Tommaso - Shellrent 31 May '19

31 May '19

Hi to all. I was looking for install oVirtSimpleBackup, but now i see: " no longer use oVirt, so I wont be furthering this project. oVirt is >>Awesome<< however, I decided to move all of my VMs into a large managed datacentre that uses vmware. I want to thank the oVirt community and all of the people over on IRC for thier awesome support. Feel free to use this code for your own ovirt backups or future oVirt backup software." Anyone kown if the projec will be mainted? There is an alternative projet to look for? -- Shellrent Logo *Tommaso De Marchi* COO Chief Operating Officer - Shellrent S.r.l. Tel. 0444321155 <tel:+390444321155> | Fax 04441492177 Via dell'Edilizia, 19 - 36100 Vicenza

1 0

4.3 hosted-engine setup & yum-utils RPM installation
by Simon Coter 31 May '19

31 May '19

Hi, is there any particular reason to get “yum-utils” (and its dependency) RPM installed during the hosted-engine deployment ? I mean, why don’t we get yum-utils RPM part of the hosted-engine image ? This “yum” process, executed during the deployment, could fail (or wait forever) if the host/engine is behind a proxy — while trying to install the RPMs. I see two options: get all the required RPMs part of the hosted-engine image add the option to supply a proxy for yum during the hosted-engine setup Could this be a request for enhancement ? Thanks Simon

2 1

Re: Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko 30 May '19

30 May '19

Hi Roy, I will run all those tests tomorrow morning (Amsterdam TimeZone) and reply back with results. Regarding NetApp documentation you mentioned below, I assume it should be enough to just “google” for it. Thank you very much for jumping in, we really appreciate it. Kind regards, Marko Vrgotic From: "Morris, Roy" <roy.morris(a)ventura.org> Date: Thursday, 30 May 2019 at 18:46 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, "users(a)ovirt.org" <users(a)ovirt.org> Cc: "users-request(a)ovirt.org" <users-request(a)ovirt.org>, "Stojchev, Darko" <D.Stojchev(a)activevideo.com> Subject: RE: Install fresh 4.3 fails with mounting shared storage Marko, Can you try disabling NFSv4 on the NetApp side for testing and rerun the installer? I don’t advise leaving it at NFSv3 but just for testing we can try it out. Also, there is some documentation on NetApp support regarding manually mounting the NFS share to change permissions then unmount. It has to be done once but after that the mounting should be fine. Do you have root squash set on NetApp? Best regards, Roy Morris GSA Virtualization Systems Analyst County of Ventura (805) 654-3625 (805) 603-9403 [cid:7c03dd9d67a9cfb78447b56087323d91a66d7c29.camel@ventura.org] From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com> Sent: Thursday, May 30, 2019 1:34 AM To: Morris, Roy <roy.morris(a)ventura.org>; users(a)ovirt.org Cc: users-request(a)ovirt.org; Stojchev, Darko <D.Stojchev(a)activevideo.com> Subject: [External] Re: Install fresh 4.3 fails with mounting shared storage Hi Roy, Sure, here is the output: Last login: Wed May 29 17:25:30 2019 from ovirt-engine.avinity.tv [root@ovirt-hv-03 ~]# showmount -e 172.17.28.5 Export list for 172.17.28.5: / (everyone) [root@ovirt-hv-03 ~]# ls -la /rhev/data-center/mnt/ total 0 drwxr-xr-x. 2 vdsm kvm 6 May 29 17:14 . drwxr-xr-x. 3 vdsm kvm 17 May 29 17:11 .. [root@ovirt-hv-03 ~]# In addition, if it helps, here is the list of shares/mount points from Netapp side, behind the 172.17.28.5 IP: [cid:image003.png@01D516CC.8548AE10] Kind regards Marko Vrgotic From: "Morris, Roy" <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>> Date: Thursday, 30 May 2019 at 00:57 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>> Cc: "users-request(a)ovirt.org<mailto:users-request@ovirt.org>" <users-request(a)ovirt.org<mailto:users-request@ovirt.org>> Subject: RE: Install fresh 4.3 fails with mounting shared storage Marko, Can you run the following commands and let us know the results. showmount -e 172.17.28.5 ls -la /rhev/data-center/mnt/ Best regards, Roy Morris From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> Sent: Wednesday, May 29, 2019 4:07 AM To: users(a)ovirt.org<mailto:users@ovirt.org> Cc: users-request(a)ovirt.org<mailto:users-request@ovirt.org> Subject: [External] [ovirt-users] Install fresh 4.3 fails with mounting shared storage CAUTION: This email contains links. If it looks suspicious or is not expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org<mailto:Spam.Manager@ventura.org>. Dear oVIrt, We are trying to deploy new setup with Hosted-Engine , oVirt version 4.3. Volume is on the Netapp, protocol NFS v4. Upon populating shared storage information and path: Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]: auto Please specify the full shared storage connection path to use (example: host:/path): 172.17.28.5:/ovirt_hosted_engine Following is displayed on the screen: [ INFO ] Creating Storage Domain [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."} Even with this error – storage gets mounted on the Host: 172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5) But playbook execution fails and we can not proceed with install. Please advise. Kindly awaiting your reply. Marko Vrgotic

2 1

Re: Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko 30 May '19

30 May '19

Hi Roy, Sure, here is the output: Last login: Wed May 29 17:25:30 2019 from ovirt-engine.avinity.tv [root@ovirt-hv-03 ~]# showmount -e 172.17.28.5 Export list for 172.17.28.5: / (everyone) [root@ovirt-hv-03 ~]# ls -la /rhev/data-center/mnt/ total 0 drwxr-xr-x. 2 vdsm kvm 6 May 29 17:14 . drwxr-xr-x. 3 vdsm kvm 17 May 29 17:11 .. [root@ovirt-hv-03 ~]# In addition, if it helps, here is the list of shares/mount points from Netapp side, behind the 172.17.28.5 IP: [cid:image001.png@01D516D3.205660E0] Kind regards Marko Vrgotic From: "Morris, Roy" <roy.morris(a)ventura.org> Date: Thursday, 30 May 2019 at 00:57 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, "users(a)ovirt.org" <users(a)ovirt.org> Cc: "users-request(a)ovirt.org" <users-request(a)ovirt.org> Subject: RE: Install fresh 4.3 fails with mounting shared storage Marko, Can you run the following commands and let us know the results. showmount -e 172.17.28.5 ls -la /rhev/data-center/mnt/ Best regards, Roy Morris From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com> Sent: Wednesday, May 29, 2019 4:07 AM To: users(a)ovirt.org Cc: users-request(a)ovirt.org Subject: [External] [ovirt-users] Install fresh 4.3 fails with mounting shared storage CAUTION: This email contains links. If it looks suspicious or is not expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org<mailto:Spam.Manager@ventura.org>. Dear oVIrt, We are trying to deploy new setup with Hosted-Engine , oVirt version 4.3. Volume is on the Netapp, protocol NFS v4. Upon populating shared storage information and path: Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]: auto Please specify the full shared storage connection path to use (example: host:/path): 172.17.28.5:/ovirt_hosted_engine Following is displayed on the screen: [ INFO ] Creating Storage Domain [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."} Even with this error – storage gets mounted on the Host: 172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5) But playbook execution fails and we can not proceed with install. Please advise. Kindly awaiting your reply. Marko Vrgotic

2 2