- Users - oVirt List Archives

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 01 Jun '19

01 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

Re: change he vm memoy size
by Strahil 30 May '19

30 May '19

Actually, you need to untar the OVF from the shared storage and check the configuration from the tar. Just keep it like that (running ) and tomorrow power down and then up the HostedEngine. Best Regards, Strahil NikolovOn May 30, 2019 12:06, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote: > > Hello, Strahil. I've just tried with engine-config -s OvfUpdateIntervalInMinutes=1 systemctl restart ovirt-engine.service After that, i changed Memory Size in manager UI. And waited about 30 minutes. Then checked memSize in /var/run/ovirt-hosted-engine-ha/vm.conf (which if i right understand syncronized with ovf every minute) and saw memSize have not been changed. And Memory Size property (in manager UI) also remains initial. Thus i think that ovf dont changes. I return OvfUpdateIntervalInMinutes=60 and will wait till tomorrow, may be the setting will be magically aplyed. > > -- > Best regards > Alexey > >> Hi Alexey, >> How much time did you check before rebooting. >> I have noticed ,that despite the default OVF update interval of 1 hour, it takes 5-6 hours for the engine to update the OVF. >> >> Best Regards, >> Strahil Nikolov >> >> On May 30, 2019 10:30, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote: >>> >>> I try to increase memory of HE VM (oVirt 4.2.8). If i do it from manager UI, i see that hot plug works - new memory devices appear and corresponding memory increase appeares inside engine guest. But 'Memory Size' property of hosted engine (in manager UI) don't reflect that new amount of memory. Also after reboot of engine vm, memory size changes back to initial value. Is it possible to change memory size of HE vm ( as far as i know the settings stored in ovf on HE domain) and how i can make this change to be persistent. >>> >>> -- >>> Best regards >>> Alexey >>> >> _______________________________________________ >> >> 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/IKID3B2TH3VR2… >> >>

4 3

[ANN] oVirt 4.3.4 Third Release Candidate is now available
by Sandro Bonazzola 30 May '19

30 May '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.4 Third Release Candidate, as of May 30th, 2019. This update is a release candidate of the fourth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used inproduction. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] Additional Resources: * Read more about the oVirt 4.3.4 release highlights: http://www.ovirt.org/release/4.3.4/ * 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.3.4/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

2 1

oVirt 3.6 SLA and QoS algorithm
by m.isaiev＠kwebbl.com 30 May '19

30 May '19

Hello! We are using oVirt 3.6 in our infrastructure and storage QoS in passive state (they are configured but not applie) for some of the servers. Last time we needed to activate QoS on high load servers and it caused storage load decrease. And this situation has raised some questions: 1. What happened to overlimit storage traffic, when QoS applying on high load virtual machine: a) All over traffic is pulling into some queue, where all disk transactions can be successfully finished with QoS throughput? b) All over-limitation data is dropped and opened transactions failed? c) All active transactions finishes on speed beyond QoS, but all new transactions immediately start to work based on configured limits? 2. How QoS mechanism actually works? Does it use some oVirt specific functions or it uses some system features to limit storage, network or CPU usage? If system one, then the QoS are provided by libvirt (using virsh or directly) or system kernel options and which one? Thanks in advance!

2 2

Re: change he vm memoy size
by Strahil 30 May '19

30 May '19

Hi Alexey, How much time did you check before rebooting. I have noticed ,that despite the default OVF update interval of 1 hour, it takes 5-6 hours for the engine to update the OVF. Best Regards, Strahil NikolovOn May 30, 2019 10:30, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote: > > I try to increase memory of HE VM (oVirt 4.2.8). If i do it from manager UI, i see that hot plug works - new memory devices appear and corresponding memory increase appeares inside engine guest. But 'Memory Size' property of hosted engine (in manager UI) don't reflect that new amount of memory. Also after reboot of engine vm, memory size changes back to initial value. Is it possible to change memory size of HE vm ( as far as i know the settings stored in ovf on HE domain) and how i can make this change to be persistent. > > -- > Best regards > Alexey >

3 2

change he vm memoy size
by Valkov, Alexey 30 May '19

30 May '19

1 0

Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko 29 May '19

29 May '19

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: ovirt metrics ansible error
by Jayme 29 May '19

29 May '19

I just tried again from scratch this time making sure a proper wildcard DNS entry existed and without using the set /etc/hosts option and am still running in to the pods issue. Can anyone confirm if this requires a public external IP to work? I am working on an internal DNS zone here and natted ips. On Tue, May 28, 2019 at 3:28 PM Edward Berger <edwberger(a)gmail.com> wrote: > In my case it was a single bare metal host, so that would be equivalent to > disabling iptables on the master0 VM you're installing to, in your ovirt > scenario. > > On Tue, May 28, 2019 at 1:25 PM Jayme <jaymef(a)gmail.com> wrote: > >> Do you mean the iptables firewall on the server being installed to i.e. >> master0 or the actual oVirt host that the master0 VM is running on? I did >> try flushing iptables rules on master0 VM then ran plays again from >> installer VM but fail at the same point. >> >> Does this log message have anything to do with the issue, /etc/cni >> directory does not even exist on master0 VM. >> >> May 28 17:23:35 master0 origin-node: W0528 17:23:35.012902 10434 >> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >> May 28 17:23:35 master0 origin-node: E0528 17:23:35.013398 10434 >> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >> cni config uninitialized >> >> >> >> On Tue, May 28, 2019 at 1:19 PM Edward Berger <edwberger(a)gmail.com> >> wrote: >> >>> > TASK [openshift_control_plane : Wait for control plane pods to appear] >>> ********* >>> > Monday 27 May 2019 13:31:54 +0000 (0:00:00.180) 0:14:33.857 >>> ************ >>> > FAILED - RETRYING: Wait for control plane pods to appear (60 retries >>> left). >>> > FAILED - RETRYING: Wait for control plane pods to appear (59 retries >>> left). >>> > It eventually counts all the way down to zero and fails. >>> >>> This looks a lot like the issues I saw when the host firewall (iptables) >>> was blocking another OKD all-in-one-host install script [1]. >>> Disabling iptables allowed the installation to continue for my proof of >>> concept "cluster". >>> >>> [1]https://github.com/gshipley/installcentos >>> >>> The other error I had with [1] was it was trying to install a couple of >>> packages (zile and python2-pip) from EPEL with the repo disabled. >>> >>> >>> >>> On Tue, May 28, 2019 at 10:41 AM Jayme <jaymef(a)gmail.com> wrote: >>> >>>> Shirly, >>>> >>>> Oh and I should mention that I did verify that NetworkManager was >>>> installed on the master0 VM and enabled/started the second go around. So >>>> that service is there and running. >>>> >>>> # systemctl list-unit-files | grep Network >>>> dbus-org.freedesktop.NetworkManager.service >>>> enabled >>>> NetworkManager-dispatcher.service >>>> enabled >>>> NetworkManager-wait-online.service >>>> enabled >>>> NetworkManager.service >>>> enabled >>>> >>>> On Tue, May 28, 2019 at 11:13 AM Jayme <jaymef(a)gmail.com> wrote: >>>> >>>>> Shirly, >>>>> >>>>> I appreciate the help with this. Unfortunately I am still running in >>>>> to the same problem. So far I've tried to install/enable/start >>>>> NetworkManager on the existing "master0" server and re-ran the plans from >>>>> the installer VM. I ran in to the same problem waiting for control plane >>>>> pods and same errors in syslog. >>>>> >>>>> So I wiped everything out, killed the template along with the >>>>> installer and master VMs. On oVirt engine (I am running 4.3.3.7-1 stable) >>>>> I did have ovirt-engine-metrics-1.3.0x rpm installed, no yum updates >>>>> available on an update check. So I installed >>>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release43-pre.rpm then >>>>> proceeded to install the latest version of ovirt-engine-metrics which gave >>>>> me: ovirt-engine-metrics-1.3.1-1.el7.noarch on hosted engine. >>>>> >>>>> After that package was installed I proceeded to follow steps from >>>>> beginning outlined at: >>>>> https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_St… -- >>>>> I ran in to the docker check issue again (same as my initial email) so I >>>>> disabled that and again got as far as starting control plane pods before >>>>> failure. >>>>> >>>>> Not sure where to go from here at this point. The only thing I can >>>>> think of that I did differently vs the instructions outlined above is that >>>>> I have not crated the wildcard DNS record, however I did set configs to >>>>> create /etc/hosts entries and they /etc/hosts on the machines have the >>>>> proper IPs assigned for all hostnames (automatically added by the ansible >>>>> plays). >>>>> >>>>> Any ideas how I can get past the plane pods issue? >>>>> >>>>> Thanks! >>>>> >>>>> On Tue, May 28, 2019 at 4:23 AM Shirly Radco <sradco(a)redhat.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The latest release of 4.3.z should already include a fix for this >>>>>> issue, ovirt-engine-metrics-1.3.1 rpm. >>>>>> >>>>>> The issue is that it requires the NetworkManagar to be installed, >>>>>> running and enabled for it to work. >>>>>> >>>>>> You can install it manually on the master0 vm , start and enable it >>>>>> or you can also install the updated rpm from the nightly builds if your >>>>>> environment is oVirt 4.2.z: >>>>>> >>>>>> https://resources.ovirt.org/pub/ovirt-4.2-snapshot/rpm/el7/noarch/ovirt-eng… >>>>>> >>>>>> Relevant patches are: >>>>>> https://gerrit.ovirt.org/#/c/99959/ >>>>>> https://gerrit.ovirt.org/#/c/99718/ >>>>>> >>>>>> Best regards, >>>>>> >>>>>> -- >>>>>> >>>>>> Shirly Radco >>>>>> >>>>>> BI Senior Software Engineer >>>>>> >>>>>> Red Hat <https://www.redhat.com/> >>>>>> >>>>>> <https://www.redhat.com/> >>>>>> >>>>>> >>>>>> On Mon, May 27, 2019 at 4:41 PM Jayme <jaymef(a)gmail.com> wrote: >>>>>> >>>>>>> I managed to get past that but am running in to another problem >>>>>>> later in the process on the control plane pods to appear task. I thought >>>>>>> perhaps a glitch in the process from the failed docker step previously so >>>>>>> after a few more runs I tried killing everything and restarting the metrics >>>>>>> process again from the very beginning and end up hitting the same issue >>>>>>> with control plane pods even though all other steps/tasks seem to be >>>>>>> working. >>>>>>> >>>>>>> I'm just getting this: >>>>>>> >>>>>>> TASK [openshift_control_plane : Wait for control plane pods to >>>>>>> appear] ********* >>>>>>> Monday 27 May 2019 13:31:54 +0000 (0:00:00.180) 0:14:33.857 >>>>>>> ************ >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (60 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (59 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (58 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (57 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (56 retries >>>>>>> left). >>>>>>> >>>>>>> It eventually counts all the way down to zero and fails. >>>>>>> >>>>>>> In syslog of the master0 server I'm seeing some errors related to >>>>>>> cni config >>>>>>> >>>>>>> May 27 13:39:07 master0 ansible-oc_obj: Invoked with files=None >>>>>>> kind=pod force=False all_namespaces=None field_selector=None >>>>>>> namespace=kube-system delete_after=False >>>>>>> kubeconfig=/etc/origin/master/admin.kubeconfig content=None state=list >>>>>>> debug=False selector=None name=master-api-master0.xxxxxx.com >>>>>>> May 27 13:39:09 master0 origin-node: W0527 13:39:09.064230 20150 >>>>>>> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >>>>>>> May 27 13:39:09 master0 origin-node: E0527 13:39:09.064670 20150 >>>>>>> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >>>>>>> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >>>>>>> cni config uninitialized >>>>>>> May 27 13:39:13 master0 ansible-oc_obj: Invoked with files=None >>>>>>> kind=pod force=False all_namespaces=None field_selector=None >>>>>>> namespace=kube-system delete_after=False >>>>>>> kubeconfig=/etc/origin/master/admin.kubeconfig content=None state=list >>>>>>> debug=False selector=None name=master-api-master0.xxxxxx.com >>>>>>> May 27 13:39:14 master0 origin-node: W0527 13:39:14.066911 20150 >>>>>>> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >>>>>>> May 27 13:39:14 master0 origin-node: E0527 13:39:14.067321 20150 >>>>>>> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >>>>>>> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >>>>>>> cni config uninitialized >>>>>>> May 27 13:39:14 master0 origin-node: E0527 13:39:14.814705 20150 >>>>>>> summary.go:102] Failed to get system container stats for >>>>>>> "/system.slice/origin-node.service": failed to get cgroup stats for >>>>>>> "/system.slice/origin-node.service": failed to get container info for >>>>>>> "/system.slice/origin-node.service": unknown container >>>>>>> "/system.slice/origin-node.service" >>>>>>> May 27 13:39:19 master0 origin-node: W0527 13:39:19.069450 20150 >>>>>>> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >>>>>>> May 27 13:39:19 master0 origin-node: E0527 13:39:19.069850 20150 >>>>>>> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >>>>>>> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >>>>>>> cni config uninitialized >>>>>>> >>>>>>> On Mon, May 27, 2019 at 9:35 AM Shirly Radco <sradco(a)redhat.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Jayme, >>>>>>>> >>>>>>>> Thank you for reaching out. >>>>>>>> Please try rerunning the ansible playbook. >>>>>>>> If this doesn't work, try adding to the integ.ini in the metrics vm >>>>>>>> openshift_disable_check=docker_storage >>>>>>>> and rerun the ansible playbook again. >>>>>>>> >>>>>>>> Please update how it goes. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Shirly Radco >>>>>>>> >>>>>>>> BI Senior Software Engineer >>>>>>>> >>>>>>>> Red Hat <https://www.redhat.com/> >>>>>>>> >>>>>>>> <https://www.redhat.com/> >>>>>>>> >>>>>>>> >>>>>>>> On Sun, May 26, 2019 at 9:34 PM Jayme <jaymef(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> I'm running in to this ansible error during oVirt metrics >>>>>>>>> installation (following procedures at: >>>>>>>>> https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_St… >>>>>>>>> ) >>>>>>>>> >>>>>>>>> This is happening late in the process, after successfully >>>>>>>>> deploying the installation VM and then running second step from the metrics >>>>>>>>> VM. >>>>>>>>> >>>>>>>>> CHECK [memory_availability : master0.xxxxxx.com] >>>>>>>>> ************************************************************************************************* >>>>>>>>> fatal: [master0.xxxxxxx.com] FAILED! => {"changed": true, >>>>>>>>> "checks": {"disk_availability": {}, "docker_image_availability": >>>>>>>>> {"changed": true}, "docker_storage": {"failed": true, "failures": >>>>>>>>> [["OpenShiftCheckException", "Could not find imported module support code >>>>>>>>> for docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\nTraceback (most recent call last):\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py\", >>>>>>>>> line 225, in run_check\n result = check.run()\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py\", >>>>>>>>> line 53, in run\n docker_info = self.execute_module(\"docker_info\", >>>>>>>>> {})\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py\", >>>>>>>>> line 211, in execute_module\n result = self._execute_module(module_name, >>>>>>>>> module_args, self.tmp, self.task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 809, in _execute_module\n (module_style, shebang, module_data, >>>>>>>>> module_path) = self._configure_module(module_name=module_name, >>>>>>>>> module_args=module_args, task_vars=task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 203, in _configure_module\n environment=final_environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 1023, in modify_module\n environment=environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 859, in _find_module_utils\n recursive_finder(module_name, >>>>>>>>> b_module_data, py_module_names, py_module_cache, zf)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 621, in recursive_finder\n raise AnsibleError(' >>>>>>>>> '.join(msg))\nAnsibleError: Could not find imported module support code for >>>>>>>>> docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\n"]], "msg": "Could not find imported module support code >>>>>>>>> for docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\nTraceback (most recent call last):\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py\", >>>>>>>>> line 225, in run_check\n result = check.run()\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py\", >>>>>>>>> line 53, in run\n docker_info = self.execute_module(\"docker_info\", >>>>>>>>> {})\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py\", >>>>>>>>> line 211, in execute_module\n result = self._execute_module(module_name, >>>>>>>>> module_args, self.tmp, self.task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 809, in _execute_module\n (module_style, shebang, module_data, >>>>>>>>> module_path) = self._configure_module(module_name=module_name, >>>>>>>>> module_args=module_args, task_vars=task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 203, in _configure_module\n environment=final_environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 1023, in modify_module\n environment=environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 859, in _find_module_utils\n recursive_finder(module_name, >>>>>>>>> b_module_data, py_module_names, py_module_cache, zf)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 621, in recursive_finder\n raise AnsibleError(' >>>>>>>>> '.join(msg))\nAnsibleError: Could not find imported module support code for >>>>>>>>> docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\n"}, "memory_availability": {}, "package_availability": >>>>>>>>> {"changed": false, "invocation": {"module_args": {"packages": ["PyYAML", >>>>>>>>> "bash-completion", "bind", "ceph-common", "dnsmasq", "docker", "firewalld", >>>>>>>>> "flannel", "glusterfs-fuse", "httpd-tools", "iptables", >>>>>>>>> "iptables-services", "iscsi-initiator-utils", "libselinux-python", >>>>>>>>> "nfs-utils", "ntp", "openssl", "origin", "origin-clients", >>>>>>>>> "origin-hyperkube", "origin-node", "pyparted", "python-httplib2", >>>>>>>>> "yum-utils"]}}}, "package_version": {"changed": false, "invocation": >>>>>>>>> {"module_args": {"package_list": [{"check_multi": false, "name": "origin", >>>>>>>>> "version": ""}, {"check_multi": false, "name": "origin-master", "version": >>>>>>>>> ""}, {"check_multi": false, "name": "origin-node", "version": ""}], >>>>>>>>> "package_mgr": "yum"}}}}, "msg": "One or more checks failed", >>>>>>>>> "playbook_context": "install"} >>>>>>>>> >>>>>>>>> NO MORE HOSTS LEFT >>>>>>>>> ******************************************************************************************************************************************* >>>>>>>>> >>>>>>>>> PLAY RECAP >>>>>>>>> *************************************************************************************************************************************************** >>>>>>>>> localhost : ok=35 changed=1 unreachable=0 >>>>>>>>> failed=0 skipped=16 rescued=0 ignored=0 >>>>>>>>> master0.xxxxxxx.com : ok=96 changed=6 unreachable=0 >>>>>>>>> failed=1 skipped=165 rescued=0 ignored=0 >>>>>>>>> >>>>>>>>> >>>>>>>>> INSTALLER STATUS >>>>>>>>> ********************************************************************************************************************************************* >>>>>>>>> Initialization : Complete (0:00:16) >>>>>>>>> Health Check : In Progress (0:00:36) >>>>>>>>> This phase can be restarted by running: >>>>>>>>> playbooks/openshift-checks/pre-install.yml >>>>>>>>> Sunday 26 May 2019 16:36:25 +0000 (0:00:36.151) 0:01:56.339 >>>>>>>>> ************ >>>>>>>>> >>>>>>>>> =============================================================================== >>>>>>>>> Run health checks (install) - EL >>>>>>>>> --------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 36.15s >>>>>>>>> os_firewall : Ensure iptables services are not enabled >>>>>>>>> ------------------------------------------------------------------------------------------------ >>>>>>>>> 2.74s >>>>>>>>> openshift_repos : Ensure libselinux-python is installed >>>>>>>>> ----------------------------------------------------------------------------------------------- >>>>>>>>> 1.77s >>>>>>>>> openshift_repos : refresh cache >>>>>>>>> ----------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.60s >>>>>>>>> Gather Cluster facts >>>>>>>>> ---------------------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.51s >>>>>>>>> container_runtime : Fixup SELinux permissions for docker >>>>>>>>> ---------------------------------------------------------------------------------------------- >>>>>>>>> 1.33s >>>>>>>>> container_runtime : Place additional/blocked/insecure registries >>>>>>>>> in /etc/containers/registries.conf >>>>>>>>> --------------------------------------------------- 1.30s >>>>>>>>> Ensure openshift-ansible installer package deps are installed >>>>>>>>> ----------------------------------------------------------------------------------------- >>>>>>>>> 1.29s >>>>>>>>> container_runtime : Install Docker >>>>>>>>> -------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.17s >>>>>>>>> Initialize openshift.node.sdn_mtu >>>>>>>>> --------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.13s >>>>>>>>> os_firewall : Install firewalld packages >>>>>>>>> -------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.13s >>>>>>>>> container_runtime : Set various Docker options >>>>>>>>> -------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.11s >>>>>>>>> install NetworkManager >>>>>>>>> -------------------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.10s >>>>>>>>> openshift_repos : Configure correct origin release repository >>>>>>>>> ----------------------------------------------------------------------------------------- >>>>>>>>> 1.05s >>>>>>>>> container_runtime : Get current installed Docker version >>>>>>>>> ---------------------------------------------------------------------------------------------- >>>>>>>>> 1.04s >>>>>>>>> openshift_repos : Configure origin gpg keys >>>>>>>>> ----------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.04s >>>>>>>>> openshift_repos : Remove openshift_additional.repo file >>>>>>>>> ----------------------------------------------------------------------------------------------- >>>>>>>>> 0.99s >>>>>>>>> container_runtime : Setup the docker-storage for overlay >>>>>>>>> ---------------------------------------------------------------------------------------------- >>>>>>>>> 0.96s >>>>>>>>> Detecting Operating System from ostree_booted >>>>>>>>> --------------------------------------------------------------------------------------------------------- >>>>>>>>> 0.95s >>>>>>>>> Gather Cluster facts >>>>>>>>> ---------------------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 0.92s >>>>>>>>> >>>>>>>>> >>>>>>>>> Failure summary: >>>>>>>>> >>>>>>>>> >>>>>>>>> 1. Hosts: master0.xxxxxxx.com >>>>>>>>> Play: OpenShift Health Checks >>>>>>>>> Task: Run health checks (install) - EL >>>>>>>>> Message: One or more checks failed >>>>>>>>> Details: check "docker_storage": >>>>>>>>> Could not find imported module support code for >>>>>>>>> docker_info. Looked for either AnsibleDockerClient.py or docker_common.py >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py", >>>>>>>>> line 225, in run_check >>>>>>>>> result = check.run() >>>>>>>>> File >>>>>>>>> "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py", >>>>>>>>> line 53, in run >>>>>>>>> docker_info = >>>>>>>>> self.execute_module("docker_info", {}) >>>>>>>>> File >>>>>>>>> "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py", >>>>>>>>> line 211, in execute_module >>>>>>>>> result = self._execute_module(module_name, >>>>>>>>> module_args, self.tmp, self.task_vars) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py", line >>>>>>>>> 809, in _execute_module >>>>>>>>> (module_style, shebang, module_data, >>>>>>>>> module_path) = self._configure_module(module_name=module_name, >>>>>>>>> module_args=module_args, task_vars=task_vars) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py", line >>>>>>>>> 203, in _configure_module >>>>>>>>> environment=final_environment) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line >>>>>>>>> 1023, in modify_module >>>>>>>>> environment=environment) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line >>>>>>>>> 859, in _find_module_utils >>>>>>>>> recursive_finder(module_name, b_module_data, >>>>>>>>> py_module_names, py_module_cache, zf) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line >>>>>>>>> 621, in recursive_finder >>>>>>>>> raise AnsibleError(' '.join(msg)) >>>>>>>>> AnsibleError: Could not find imported module >>>>>>>>> support code for docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py >>>>>>>>> >>>>>>>>> >>>>>>>>> The execution of "install_okd.yaml" includes checks designed to >>>>>>>>> fail early if the requirements of the playbook are not met. One or more of >>>>>>>>> these checks failed. To disregard these results,explicitly disable checks >>>>>>>>> by setting an Ansible variable: >>>>>>>>> openshift_disable_check=docker_storage >>>>>>>>> Failing check names are shown in the failure details above. Some >>>>>>>>> checks may be configurable by variables if your requirements are different >>>>>>>>> from the defaults; consult check documentation. >>>>>>>>> Variables can be set in the inventory or passed on the command >>>>>>>>> line using the -e flag to ansible-playbook. >>>>>>>>> _______________________________________________ >>>>>>>>> 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/SEFPOF36T7G4G… >>>>>>>>> >>>>>>>> _______________________________________________ >>>> 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/CN6G76Z7MVNK6… >>>> >>>

2 3

Dashboard error after upgrade to 4.3.2
by Mikhail Krasnobaev 29 May '19

29 May '19

3 3

Re: nested attributes of structs
by Nathanaël Blanchet 29 May '19

29 May '19

Hello Lucie, Can you give me the BZ number so I can follow the ticket? I'd like to test the ansible patch as soon as it's available. De: "Lucie Leistnerova" <lleistne(a)redhat.com> À: "Nathanaël Blanchet" <blanchet(a)abes.fr>, "users" <users(a)ovirt.org> Envoyé: Mercredi 29 Mai 2019 08:31:16 Objet: Re: [ovirt-users] nested attributes of structs Hi Nathanaël, On 5/28/19 5:21 PM, Nathanaël Blanchet wrote: Hello, Considering: https://bugzilla.redhat.com/show_bug.cgi?id=1653743 and https://github.com/ansible/ansible/issues/30624 I installed latest 4.3 sdk and ansible 2.8 but I still can't get the name of the href link doing this: - name : disk facts ovirt_disk_facts : auth : "{{ ovirt_auth }}" fetch_nested: true it still gives: "storage_domains": [ { "href": "/ovirt-engine/api/storagedomains/0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88", "id": "0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88" } If I understand, I should get the storage_domain name instead of its id, shouldn't I? The change seems to not work perfectly. When I run playbook with fetch_nested: True nested_attributes: - name I get "quota": { "href": "/ovirt-engine/api/datacenters/87bc2e30-f3b1-11e8-aa7d-001a4a013f36/quotas/96f2a2e4-f3b1-11e8-82b6-001a4a013f36", "id": "96f2a2e4-f3b1-11e8-82b6-001a4a013f36", "name": "Default" }, "disk_profile": { "href": "/ovirt-engine/api/storagedomains/82ceb4c9-e844-4fc7-b0ff-559052e6301f/diskprofiles/30cc8a74-4b99-4aab-8193-28826bbecbb9", "id": "30cc8a74-4b99-4aab-8193-28826bbecbb9", "name": "ll-03s1-43-3" }, So for direct link <quota href="/ovirt-engine/api/datacenters/87bc2e30-f3b1-11e8-aa7d-001a4a013f36/quotas/96f2a2e4-f3b1-11e8-82b6-001a4a013f36" id="96f2a2e4-f3b1-11e8-82b6-001a4a013f36"/> it works fine. But storage domains are different, it is a list of links. <storage_domains> <storage_domain href="/ovirt-engine/api/storagedomains/82ceb4c9-e844-4fc7-b0ff-559052e6301f" id="82ceb4c9-e844-4fc7-b0ff-559052e6301f"/> </storage_domains> I'll check it with developer and update by verifying the BZ. Thanks for catching that issue. BQ_BEGIN -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr _______________________________________________ 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/L4ZHNR6YWLBQH… BQ_END Best regards, -- Lucie Leistnerova Senior Quality Engineer, QE Cloud, RHVM Red Hat EMEA IRC: lleistne @ #rhev-qe

1 0