- Users - oVirt List Archives

Update to Ovirt 4.3.10-4-1 causes XFS issue
by Chaz Vidal 19 Jun '20

19 Jun '20

Hi All I think I have come across this bug: https://access.redhat.com/solutions/5075561 Updating Ovirt to 4.3.10 shows that the kernel installed on the hosts is the version that has the issue: 3.10.0-1127.8.2.el7.x86_64 The RedHat article suggests updating to kernel-3.10.0-1127.10.1.el7 but running engine-upgrade-check now shows no updates available from my engine manager. Is this something I can fix myself or would the updated kernel be available? Appreciate the advice as new to Ovirt. Normally I would point the hosts to the new kernel but I think it should be updated through Ovirt manager, correct? Thanks! Chaz

3 4

Host has time-drift of xxx seconds
by Strahil Nikolov 19 Jun '20

19 Jun '20

Hello All, I have a strange error that should be fixed but the event log is still filling with the following after the latest patching (4.3.10): Host ovirt2.localdomain has time-drift of 2909848 seconds while maximum configured value is 300 seconds. Host ovirt3.localdomain has time-drift of 2909848 seconds while maximum configured value is 300 seconds. As it blamed only 2 out of 3 systems, I checked what has happened on ovirt1 and that one was far behind the other servers. Once I fixed the issue, I kept receiving those errors despite tthe fact that I fixed the time drift on ovirt1 several days ago. Currently the hosts and the engine are OK, but I got no idea how to 'fix' the issue. I have also noticed that the 2 errors had a date of 2 PM which is not possible with my current timezone. Here is a one-shot query from all nodes: [root@ovirt1 ~]# for i in ovirt{1..3}; do ssh $i "ntpdate -q office.ipacct.com"; done server 195.85.215.8, stratum 1, offset 0.001233, delay 0.03105 11 Jun 05:48:16 ntpdate[5224]: adjust time server 195.85.215.8 offset 0.001233 sec server 195.85.215.8, stratum 1, offset -0.000200, delay 0.02821 11 Jun 05:48:23 ntpdate[6637]: adjust time server 195.85.215.8 offset -0.000200 sec server 195.85.215.8, stratum 1, offset 0.000243, delay 0.02914 11 Jun 05:48:30 ntpdate[14215]: adjust time server 195.85.215.8 offset 0.000243 sec [root@ovirt1 ~]# ssh engine 'ntpdate -q office.ipacct.com' root@engine's password: server 195.85.215.8, stratum 1, offset 0.000291, delay 0.02888 11 Jun 05:49:15 ntpdate[13911]: adjust time server 195.85.215.8 offset 0.000291 sec Any ideas ? Best Regards, Strahil Nikolov

2 3

Fwd: Issues with Gluster Domain
by C Williams 18 Jun '20

18 Jun '20

Resending to deal with possible email issues ---------- Forwarded message --------- From: C Williams <cwilliams3320(a)gmail.com> Date: Thu, Jun 18, 2020 at 2:07 PM Subject: Re: [ovirt-users] Issues with Gluster Domain To: Strahil Nikolov <hunter86_bg(a)yahoo.com> More [root@ov06 ~]# for i in $(gluster volume list); do echo $i;echo; gluster volume info $i; echo;echo;gluster volume status $i;echo;echo;echo;done images3 Volume Name: images3 Type: Replicate Volume ID: 0243d439-1b29-47d0-ab39-d61c2f15ae8b Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: 192.168.24.18:/bricks/brick04/images3 Brick2: 192.168.24.19:/bricks/brick05/images3 Brick3: 192.168.24.20:/bricks/brick06/images3 Options Reconfigured: performance.client-io-threads: on nfs.disable: on transport.address-family: inet user.cifs: off auth.allow: * performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.low-prio-threads: 32 network.remote-dio: off cluster.eager-lock: enable cluster.quorum-type: auto cluster.server-quorum-type: server cluster.data-self-heal-algorithm: full cluster.locking-scheme: granular cluster.shd-max-threads: 8 cluster.shd-wait-qlength: 10000 features.shard: on cluster.choose-local: off client.event-threads: 4 server.event-threads: 4 storage.owner-uid: 36 storage.owner-gid: 36 performance.strict-o-direct: on network.ping-timeout: 30 cluster.granular-entry-heal: enable Status of volume: images3 Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 192.168.24.18:/bricks/brick04/images3 49152 0 Y 6666 Brick 192.168.24.19:/bricks/brick05/images3 49152 0 Y 6779 Brick 192.168.24.20:/bricks/brick06/images3 49152 0 Y 7227 Self-heal Daemon on localhost N/A N/A Y 6689 Self-heal Daemon on ov07.ntc.srcle.com N/A N/A Y 6802 Self-heal Daemon on ov08.ntc.srcle.com N/A N/A Y 7250 Task Status of Volume images3 ------------------------------------------------------------------------------ There are no active volume tasks [root@ov06 ~]# ls -l /rhev/data-center/mnt/glusterSD/ total 16 drwxr-xr-x. 5 vdsm kvm 8192 Jun 18 14:04 192.168.24.15:_images drwxr-xr-x. 5 vdsm kvm 8192 Jun 18 14:05 192.168.24.18:_images3 [root@ov06 ~]# On Thu, Jun 18, 2020 at 2:03 PM C Williams <cwilliams3320(a)gmail.com> wrote: > Strahil, > > Here you go -- Thank You For Your Help ! > > BTW -- I can write a test file to gluster and it replicates properly. > Thinking something about the oVirt Storage Domain ? > > [root@ov08 ~]# gluster pool list > UUID Hostname State > 5b40c659-d9ab-43c3-9af8-18b074ea0b83 ov06 Connected > 36ce5a00-6f65-4926-8438-696944ebadb5 ov07.ntc.srcle.com Connected > c7e7abdb-a8f4-4842-924c-e227f0db1b29 localhost Connected > [root@ov08 ~]# gluster volume list > images3 > > On Thu, Jun 18, 2020 at 1:13 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> > wrote: > >> Log to the oVirt cluster and provide the output of: >> gluster pool list >> gluster volume list >> for i in $(gluster volume list); do echo $i;echo; gluster volume info >> $i; echo;echo;gluster volume status $i;echo;echo;echo;done >> >> ls -l /rhev/data-center/mnt/glusterSD/ >> >> Best Regards, >> Strahil Nikolov >> >> >> На 18 юни 2020 г. 19:17:46 GMT+03:00, C Williams <cwilliams3320(a)gmail.com> >> написа: >> >Hello, >> > >> >I recently added 6 hosts to an existing oVirt compute/gluster cluster. >> > >> >Prior to this attempted addition, my cluster had 3 Hypervisor hosts and >> >3 >> >gluster bricks which made up a single gluster volume (replica 3 volume) >> >. I >> >added the additional hosts and made a brick on 3 of the new hosts and >> >attempted to make a new replica 3 volume. I had difficulty creating >> >the >> >new volume. So, I decided that I would make a new compute/gluster >> >cluster >> >for each set of 3 new hosts. >> > >> >I removed the 6 new hosts from the existing oVirt Compute/Gluster >> >Cluster >> >leaving the 3 original hosts in place with their bricks. At that point >> >my >> >original bricks went down and came back up . The volume showed entries >> >that >> >needed healing. At that point I ran gluster volume heal images3 full, >> >etc. >> >The volume shows no unhealed entries. I also corrected some peer >> >errors. >> > >> >However, I am unable to copy disks, move disks to another domain, >> >export >> >disks, etc. It appears that the engine cannot locate disks properly and >> >I >> >get storage I/O errors. >> > >> >I have detached and removed the oVirt Storage Domain. I reimported the >> >domain and imported 2 VMs, But the VM disks exhibit the same behaviour >> >and >> >won't run from the hard disk. >> > >> > >> >I get errors such as this >> > >> >VDSM ov05 command HSMGetAllTasksStatusesVDS failed: low level Image >> >copy >> >failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', >> >'-T', 'none', '-f', 'raw', >> >u'/rhev/data-center/mnt/glusterSD/192.168.24.18: >> _images3/5fe3ad3f-2d21-404c-832e-4dc7318ca10d/images/3ea5afbd-0fe0-4c09-8d39-e556c66a8b3d/fe6eab63-3b22-4815-bfe6-4a0ade292510', >> >'-O', 'raw', >> >u'/rhev/data-center/mnt/192.168.24.13: >> _stor_import1/1ab89386-a2ba-448b-90ab-bc816f55a328/images/f707a218-9db7-4e23-8bbd-9b12972012b6/d6591ec5-3ede-443d-bd40-93119ca7c7d5'] >> >failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading >> >sector 135168: Transport endpoint is not connected\\nqemu-img: error >> >while >> >reading sector 131072: Transport endpoint is not connected\\nqemu-img: >> >error while reading sector 139264: Transport endpoint is not >> >connected\\nqemu-img: error while reading sector 143360: Transport >> >endpoint >> >is not connected\\nqemu-img: error while reading sector 147456: >> >Transport >> >endpoint is not connected\\nqemu-img: error while reading sector >> >155648: >> >Transport endpoint is not connected\\nqemu-img: error while reading >> >sector >> >151552: Transport endpoint is not connected\\nqemu-img: error while >> >reading >> >sector 159744: Transport endpoint is not connected\\n')",) >> > >> >oVirt version is 4.3.82-1.el7 >> >OS CentOS Linux release 7.7.1908 (Core) >> > >> >The Gluster Cluster has been working very well until this incident. >> > >> >Please help. >> > >> >Thank You >> > >> >Charles Williams >> >

2 1

Fwd: Issues with Gluster Domain
by C Williams 18 Jun '20

18 Jun '20

Resending to deal with possible email issues Thank You For Your Help !! ---------- Forwarded message --------- From: C Williams <cwilliams3320(a)gmail.com> Date: Thu, Jun 18, 2020 at 2:03 PM Subject: Re: [ovirt-users] Issues with Gluster Domain To: Strahil Nikolov <hunter86_bg(a)yahoo.com> Strahil, Here you go -- Thank You For Your Help ! BTW -- I can write a test file to gluster and it replicates properly. Thinking something about the oVirt Storage Domain ? [root@ov08 ~]# gluster pool list UUID Hostname State 5b40c659-d9ab-43c3-9af8-18b074ea0b83 ov06 Connected 36ce5a00-6f65-4926-8438-696944ebadb5 ov07.ntc.srcle.com Connected c7e7abdb-a8f4-4842-924c-e227f0db1b29 localhost Connected [root@ov08 ~]# gluster volume list images3 On Thu, Jun 18, 2020 at 1:13 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > Log to the oVirt cluster and provide the output of: > gluster pool list > gluster volume list > for i in $(gluster volume list); do echo $i;echo; gluster volume info > $i; echo;echo;gluster volume status $i;echo;echo;echo;done > > ls -l /rhev/data-center/mnt/glusterSD/ > > Best Regards, > Strahil Nikolov > > > На 18 юни 2020 г. 19:17:46 GMT+03:00, C Williams <cwilliams3320(a)gmail.com> > написа: > >Hello, > > > >I recently added 6 hosts to an existing oVirt compute/gluster cluster. > > > >Prior to this attempted addition, my cluster had 3 Hypervisor hosts and > >3 > >gluster bricks which made up a single gluster volume (replica 3 volume) > >. I > >added the additional hosts and made a brick on 3 of the new hosts and > >attempted to make a new replica 3 volume. I had difficulty creating > >the > >new volume. So, I decided that I would make a new compute/gluster > >cluster > >for each set of 3 new hosts. > > > >I removed the 6 new hosts from the existing oVirt Compute/Gluster > >Cluster > >leaving the 3 original hosts in place with their bricks. At that point > >my > >original bricks went down and came back up . The volume showed entries > >that > >needed healing. At that point I ran gluster volume heal images3 full, > >etc. > >The volume shows no unhealed entries. I also corrected some peer > >errors. > > > >However, I am unable to copy disks, move disks to another domain, > >export > >disks, etc. It appears that the engine cannot locate disks properly and > >I > >get storage I/O errors. > > > >I have detached and removed the oVirt Storage Domain. I reimported the > >domain and imported 2 VMs, But the VM disks exhibit the same behaviour > >and > >won't run from the hard disk. > > > > > >I get errors such as this > > > >VDSM ov05 command HSMGetAllTasksStatusesVDS failed: low level Image > >copy > >failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', > >'-T', 'none', '-f', 'raw', > >u'/rhev/data-center/mnt/glusterSD/192.168.24.18: > _images3/5fe3ad3f-2d21-404c-832e-4dc7318ca10d/images/3ea5afbd-0fe0-4c09-8d39-e556c66a8b3d/fe6eab63-3b22-4815-bfe6-4a0ade292510', > >'-O', 'raw', > >u'/rhev/data-center/mnt/192.168.24.13: > _stor_import1/1ab89386-a2ba-448b-90ab-bc816f55a328/images/f707a218-9db7-4e23-8bbd-9b12972012b6/d6591ec5-3ede-443d-bd40-93119ca7c7d5'] > >failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading > >sector 135168: Transport endpoint is not connected\\nqemu-img: error > >while > >reading sector 131072: Transport endpoint is not connected\\nqemu-img: > >error while reading sector 139264: Transport endpoint is not > >connected\\nqemu-img: error while reading sector 143360: Transport > >endpoint > >is not connected\\nqemu-img: error while reading sector 147456: > >Transport > >endpoint is not connected\\nqemu-img: error while reading sector > >155648: > >Transport endpoint is not connected\\nqemu-img: error while reading > >sector > >151552: Transport endpoint is not connected\\nqemu-img: error while > >reading > >sector 159744: Transport endpoint is not connected\\n')",) > > > >oVirt version is 4.3.82-1.el7 > >OS CentOS Linux release 7.7.1908 (Core) > > > >The Gluster Cluster has been working very well until this incident. > > > >Please help. > > > >Thank You > > > >Charles Williams >

1 0

Issues with Gluster Domain
by C Williams 18 Jun '20

18 Jun '20

Hello, I recently added 6 hosts to an existing oVirt compute/gluster cluster. Prior to this attempted addition, my cluster had 3 Hypervisor hosts and 3 gluster bricks which made up a single gluster volume (replica 3 volume) . I added the additional hosts and made a brick on 3 of the new hosts and attempted to make a new replica 3 volume. I had difficulty creating the new volume. So, I decided that I would make a new compute/gluster cluster for each set of 3 new hosts. I removed the 6 new hosts from the existing oVirt Compute/Gluster Cluster leaving the 3 original hosts in place with their bricks. At that point my original bricks went down and came back up . The volume showed entries that needed healing. At that point I ran gluster volume heal images3 full, etc. The volume shows no unhealed entries. I also corrected some peer errors. However, I am unable to copy disks, move disks to another domain, export disks, etc. It appears that the engine cannot locate disks properly and I get storage I/O errors. I have detached and removed the oVirt Storage Domain. I reimported the domain and imported 2 VMs, But the VM disks exhibit the same behaviour and won't run from the hard disk. I get errors such as this VDSM ov05 command HSMGetAllTasksStatusesVDS failed: low level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.24.18:_images3/5fe3ad3f-2d21-404c-832e-4dc7318ca10d/images/3ea5afbd-0fe0-4c09-8d39-e556c66a8b3d/fe6eab63-3b22-4815-bfe6-4a0ade292510', '-O', 'raw', u'/rhev/data-center/mnt/192.168.24.13:_stor_import1/1ab89386-a2ba-448b-90ab-bc816f55a328/images/f707a218-9db7-4e23-8bbd-9b12972012b6/d6591ec5-3ede-443d-bd40-93119ca7c7d5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 135168: Transport endpoint is not connected\\nqemu-img: error while reading sector 131072: Transport endpoint is not connected\\nqemu-img: error while reading sector 139264: Transport endpoint is not connected\\nqemu-img: error while reading sector 143360: Transport endpoint is not connected\\nqemu-img: error while reading sector 147456: Transport endpoint is not connected\\nqemu-img: error while reading sector 155648: Transport endpoint is not connected\\nqemu-img: error while reading sector 151552: Transport endpoint is not connected\\nqemu-img: error while reading sector 159744: Transport endpoint is not connected\\n')",) oVirt version is 4.3.82-1.el7 OS CentOS Linux release 7.7.1908 (Core) The Gluster Cluster has been working very well until this incident. Please help. Thank You Charles Williams

2 1

Ovirt fails to retrieve iSCSI targets during installation
by Ricardo Alonso 18 Jun '20

18 Jun '20

Trying to connect to a an iSCSI target (no chap/secrets) is failing with the message: 2020-06-17 05:25:40,050-0300 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "connection": "close", "content": "{\n \"detail\" : \"For correct usage, see: https://ovirt.<removed>/ovirt-engine/apidoc#services/host/methods/iscsi_discover\",\n \"reason\" : \"Request syntactically incorrect.\"\n}", "content_encoding": "identity", "content_type": "application/json", "correlation_id": "a5ba94a7-b22b-4ed6-9a47-87a87186c341", "date": "Wed, 17 Jun 2020 08:25:38 GMT", "elapsed": 0, "invocation": { "module_args": { "attributes": null, "backup": null, "body": "{\"iscsi\": {\"address\": \"192.168.6.1\", \"port\": \"3260,3260\", \"username\": null, \"password\": \"\"}}", "body_format": "json", "client_cert": null, "client_key": null, "content": null, "creates": null, "delimiter": null, "dest": null, "directory_mode": null, "follow": false, "follow_redirects": "safe", "force": false, "force_basic_auth": false, "group": null, "headers": { "Accept": "application/json", "Authorization": "Basic YWRtaW5AaW50ZXJuYWw6cGQyMDAx", "Content-Type": "application/json" }, "http_agent": "ansible-httpget", "method": "POST", "mode": null, "owner": null, "regexp": null, "remote_src": null, "removes": null, "return_content": true, "selevel": null, "serole": null, "setype": null, "seuser": null, "src": null, "status_code": [ "200" ], "timeout": 30, "unix_socket": null, "unsafe_writes": null, "url": "https://ovirt.<removed>/ovirt-engine/api/hosts/2c173b7f-9f9e-4046-890a-ab16d1babc35/iscsidiscover", "url_password": null, "url_username": null, "use_proxy": true, "validate_certs": false } }, "json": { "detail": "For correct usage, see: https://ovirt.<removed>/ovirt-engine/apidoc#services/host/methods/iscsi_discover", "reason": "Request syntactically incorrect." }, "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1c mod_wsgi/4.6.4 Python/3.6", "status": 400, "transfer_encoding": "chunked", "url": "https://ovirt.<removed>/ovirt-engine/api/hosts/2c173b7f-9f9e-4046-890a-ab16d1babc35/iscsidiscover" }, "ansible_task": "iSCSI discover with REST API", "ansible_type": "task", "status": "FAILED", "task_duration": 4 } I found this old bug, but doesn't seams to have a resolution. Any clue/tips?

3 4

Re: Cannot authenticate user Invalid scopes: ovirt-app-api
by Anton Louw 18 Jun '20

18 Jun '20

So I think I have narrowed it down to the OVN settings. The only problem now is, is that when I want to update the OVN settings, it fails with “Failed to communicate with External Provider. See logs for details” When checking the logs, I see an error stating the “root hostname does not match” (In the OVN settings via the WebUI, I see that it also points to the old hostname) A bit of background on this, when the engine was initially built, it was configured with a different hostname, which was then changed, but somehow it is still referencing the old hostname. When I run the change hostname scripts (/usr/share/ovirt-engine/setup/bin/ovirt-engine-rename) it runs through everything, until it needs to modify the certs. (I have attached the screenshot) I am really not sure where to go from here, and I believe that most of this has to do with the certs (And I am just grasping at straws here) I am starting to think that it would just be easier to deploy everything from scratch, but if anybody has any ideas, I would appreciate it. Thank you Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za From: Anton Louw via Users <users(a)ovirt.org> Sent: 18 June 2020 12:39 To: users(a)ovirt.org Subject: [ovirt-users] Cannot authenticate user Invalid scopes: ovirt-app-api Hi All, A new issue 😊 We have configured oVirt to use KeyCloak for authentication. This all works, I can log into the WebUI etc, but as soon as I need to talk to the API, it gives me the “invalid scopes” error. I have double checked KeyCloak, and the scopes are added. I went through the logs, but there is nothing telling me exactly what the actual cause is. I get the below when trying to get a token from the engine: “{"error_code":"access_denied","error":"Cannot authenticate user Invalid scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access."}” Does anybody have any idea where this is going wrong? Thanks Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<http://www.vox.co.za> [F]<https://www.facebook.com/voxtelecomZA> [T]<https://www.twitter.com/voxtelecom> [I]<https://www.instagram.com/voxtelecomza> [L]<https://www.linkedin.com/company/voxtelecom> [Y]<https://www.youtube.com/user/VoxTelecom> [#VoxBrand]<https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> Disclaimer The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here<https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>.

1 0

Cannot authenticate user Invalid scopes: ovirt-app-api
by Anton Louw 18 Jun '20

18 Jun '20

Hi All, A new issue 😊 We have configured oVirt to use KeyCloak for authentication. This all works, I can log into the WebUI etc, but as soon as I need to talk to the API, it gives me the “invalid scopes” error. I have double checked KeyCloak, and the scopes are added. I went through the logs, but there is nothing telling me exactly what the actual cause is. I get the below when trying to get a token from the engine: “{"error_code":"access_denied","error":"Cannot authenticate user Invalid scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access."}” Does anybody have any idea where this is going wrong? Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

1 0

Shutting be down kvm host does what to VMs
by Louis Bohm 18 Jun '20

18 Jun '20

I have a single ovirt host running 2 VMs. If I do a shutdown -h now on the kvm host will ovirt do a similar shutdown command on the VMs? And wait for them to shutdown before finishing it's shutdown? Please do not tell me I should have 2 physical hosts. I know but it's not in the clients budget. Thanks, Louis

2 1

cant edit ISO domain in any way
by Philip Brown 18 Jun '20

18 Jun '20

oVirt 4.3: Okay, I found documentation that I cant have more than one "ISO" type storage domain. I can kinda understand that. But, I cant even edit or delete the existing one? Even when logged in to the oVirt GUI as admin@internal? Is this some kind of bug or something?

2 3

Information requested on oVirt + RDO/OpenStack
by Glenn Marcy 18 Jun '20

18 Jun '20

I am hoping to try out adding RDO to oVirt after things with CentOS 8.2 settle down. I've done deployments of RDO on KVM before without any issues (TripleO Quickstart), but this would be my first time trying it on oVirt. Since oVirt recently updated to the openstack-java 3.2.9 packages, is there a specific version of OpenStack (Train or Ussuri) that runs on CentOS 8.x that I need? Are there any issues with the fact that oVirt already uses and/or provides some OpenStack services? Does the fact that OpenStack deployments are now more "containerized" present any issues I should be aware of? Are there initiatives for further convergence between oVirt, RDO/OpenStack and OKD/OCP that are changing this space where it would make sense to follow and/or participate in those efforts? I'm starting out with oVirt to get an understanding of the capabilities that it brings to the table, but interested in the convergence of the other technologies that would benefit from having oVirt as, or a part of, the foundation. Best Regards, Glenn

2 1

Ansible ovirt_disk module: how to attach disk without activation
by Gianluca Cecchi 17 Jun '20

17 Jun '20

Hello, root problem in a 4.3.8 environment is that sometimes when I hot add a floating disk to a VM in web admin gui, it attaches and also activates it by default (the flag is checked by default, but you can uncheck it) and this two-phases action fails as a single step. What I get is: VDSM ovhost command HotPlugDiskVDS failed: Requested operation is not valid: Domain already contains a disk with that address And then the VM event regarding hot add disk failure. I'm going to investigate more: it should be a past bug already solved in theory by my libvirt sw version (I've to crosscheck its id)... but I still get the error sometimes. What programmatically works is to attach the disk without activating it (this step always completes with success) and then activate the disk as a separate operation (this one typically fails the first time when I have the "problematic" situation, but then the second time succeeds). So I would like to use it as a workaround in the mean time. The problem reflects using the ansible module ovirt_disk, that by default activates the disk. So I have tried to specify "activate: no" (introduced in 2.8, readings the docs) when I attach it, but it seems not to work as expected. I'm testing using awx and its info says: AWX 9.0.1.0 Ansible 2.8.5 I tried this on a VM that (as usual when you want to reproduce... ;-) doesn't show the problem: ovirt_disk: auth: "{{ ovirt_auth }}" state: attached activate: no name: "{{ tobe_sw_disk_name }}" vm_name: "{{ ansible_hostname }}" size: "{{ current_sw_disk_size }}" interface: virtio_scsi delegate_to: localhost register: disk_attach_info But going to see registered variable it contains "active: true": "disk_activate_info": { "changed": false, "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827", "diskattachment": { "href": "/ovirt-engine/api/vms/b5c67c93-bd5d-42b6-a873-05f69cece2f1/diskattachments/6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827", "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827", "active": true, "bootable": false, "disk": { .... In fact I followed with the step to activate the disk: ovirt_disk: auth: "{{ ovirt_auth }}" state: present activate: yes name: "{{ tobe_sw_disk_name }}" vm_name: "{{ ansible_hostname }}" size: "{{ current_sw_disk_size }}" interface: virtio_scsi delegate_to: localhost register: disk_activate_info But in playbook run I got: ok: [target_vm -> localhost] And inside registered variable "changed: false": "disk_activate_info": { "changed": false, "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827", "diskattachment": { "href": "/ovirt-engine/api/vms/b5c67c93-bd5d-42b6-a873-05f69cece2f1/diskattachments/6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827", "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827", "active": true, ... Any tip to realize what needed: task to only attach disk without activating it and then task to activate the disk? Thanks in advance, Gianluca

2 3

Re: New VM from Template and Storage size
by Eyal Shenitzky 17 Jun '20

17 Jun '20

Hi Erez, This sounds like a nice RFE. Can you please submit it to Bugzilla - https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine ? In the title add in the beginning - [RFE] ... Thanks. On Wed, 17 Jun 2020 at 08:24, Erez Zarum <erezz(a)nanosek.com> wrote: > It is reasonable flow that you inherit the configuration from the > template, but you can change most of the settings during the creation of > the VM, I just don't understand why not to be able to change the disk size > and name. > Why disk size? You can say the same thing with any other settings, so just > make a template for any different setting you need for different VMs based > on that same OS. > This flow of changing the disk size is supported in any other platforms > take a few, OpenStack, VMWare, Xen and any other Cloud providers. > I don't see a reason why to do this in two API calls, one for VM creation > and then another one for just expanding the disk size. > I do understand if you create a VM based on a thin template which is just > a link that there's no other way. > Another "issue" is that it creates the new of the new disk for the VM > based on the template name instead of "vmname_Disk1" etc... > I have a customer with many different disk sizes, varying from 50GB up to > 200GB, If I go and create a template for an OS based on that, I will > probably have 10 templates, it's not scalable if you need to just modify > something in the template as well. > > So the only option right now is to use OpenStack Glance for saving images > or create a new feature in Foreman/Satelite for that. > > On 16/06/2020, 20:53, "Nir Soffer" <nsoffer(a)redhat.com> wrote: > > On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum <erezz(a)nanosek.com> wrote: > > > > Hey, > > > > I have created a template that the disk is a thick (raw) with a size > of 15GB. > > > > I am trying to create a VM from that template but having the disk > with a much larger size, both template and the VM are set to use thick and > I create the new VM with the clone option, so there’s no link between the > new VM and the template. > > > > So far the only solution I managed to find is to adjust the size > after creating the VM. > > This looks like reasonable flow. You create the vm from a template, so > you inherit the > disk size from the template. Then you modify the disk to the required > size. > > > For example, this situation causes a problematic step when using > Foreman/Satelite as trying to provision a VM based on a template but with > different size for the OS disk. > > Why is this problematic? > > > I assume that one of the ways to solve it is to convert the template > somehow into an “image”? like using OpenStack Glance as a place to store > “templates” as images? Any other way besides using Glance? > > If you always need to resize the template, why not create another > templated with the right > size based on this template? > > Nir > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/46IFRJCTZNZZH… > -- Regards, Eyal Shenitzky

1 0

Re: New VM from Template and Storage size
by Nir Soffer 17 Jun '20

17 Jun '20

On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum <erezz(a)nanosek.com> wrote: > > Hey, > > I have created a template that the disk is a thick (raw) with a size of 15GB. > > I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template. > > So far the only solution I managed to find is to adjust the size after creating the VM. This looks like reasonable flow. You create the vm from a template, so you inherit the disk size from the template. Then you modify the disk to the required size. > For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk. Why is this problematic? > I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance? If you always need to resize the template, why not create another templated with the right size based on this template? Nir

2 1

Re: oVirt noVNC
by Anton Louw 17 Jun '20

17 Jun '20

Hi Paul, Apologies for the late response. So we only have a cert bundle on the one that is currently not working. The env that is working still has all the default certs. Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> Sent: 12 June 2020 13:13 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za>; users(a)ovirt.org Subject: Re: oVirt noVNC Sorry Anton, I'm trying to get a lot of things sorted before the weekend. This seems the wrong way round, if you follow the documentation you shouldn't have the symbolic link on the working system unless you replaced the file it was pointing to. Do you have certificate bundles for both systems? Regards, Paul S. ________________________________ From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Sent: 12 June 2020 11:44 To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Thanks Paul, So the symbolic link has then been removed, as per the below. Not quite sure where to go from here. Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>> Sent: 12 June 2020 12:30 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; users(a)ovirt.org<mailto:users@ovirt.org> Subject: Re: oVirt noVNC Yes Anton, I think it's in the documentation it's Steps 2 & 3 • • The Engine has been configured to use /etc/pki/ovirt-engine/apache-ca.pem, which is symbolically linked to /etc/pki/ovirt-engine/ca.pem. Remove the symbolic link. # rm /etc/pki/ovirt-engine/apache-ca.pem • Save your CA certificate as /etc/pki/ovirt-engine/apache-ca.pem. # cp /tmp/3rd-party-ca-cert.pem /etc/pki/ovirt-engine/apache-ca.pem Regards, Paul S. ________________________________ From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Sent: 12 June 2020 11:06 To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Hi Paul, Double checked the permissions as well. All seems to be fine. The only thing that does look different between the environments are the below: ENV1 (Not working) [cid:image008.png@01D64474.A4312E70] ENV2 (Working) [cid:image009.png@01D64474.A4312E70] It seems that on the working environment, there is a shortcut file (apached-ca.pem) which points to the ca.pem file, but on the environment that is not working, the apache-ca.pem file is not a shortcut. Could this perhaps be an issue? Thanks Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>> Sent: 12 June 2020 10:44 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; users(a)ovirt.org<mailto:users@ovirt.org> Subject: Re: oVirt noVNC No worries, If all is pointing to the correct files I would check permissions. Regards, Paul S. ________________________________ From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Sent: 12 June 2020 09:34 To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Hi Paul, Thanks for the reply. Apologies, I should have added that I have installed our own certificates. The main problem I am facing is that the noVNC console just refuses to open, I get the attached error with any VM I try and access. I should have perhaps started with this issue in my first mail, apologies 😊 Thanks Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>> Sent: 12 June 2020 10:29 To: users(a)ovirt.org<mailto:users@ovirt.org>; Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Subject: Re: oVirt noVNC Hello Anton, if your organisation has it's own CA you can install your own certificates or get certificates from a trusted CA. https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL.html<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> Paul S. ________________________________ From: Anton Louw via Users <users(a)ovirt.org<mailto:users@ovirt.org>> Sent: 12 June 2020 08:56 To: users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Hi Everybody, With regards to noVNC, is it a requirement to install the CA into your local browser? I would like users to access their VM console, but with no additional work from their side, ie. Downloading the CA and importing it. Thank you Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> [#VoxBrand]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vox.c…> Disclaimer The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.voxte…>. To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/> To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/> To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/> To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/>

1 0

help: renamed master volume
by Philip Brown 16 Jun '20

16 Jun '20

Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 on the way, I browsed into the Storage area, in one of the nodes. Noticed under the "Volume groups", area that the volumes were named after some loong ID string. Saw there was a "rename" button. figured it would be just like renaming a VM. thigns would just get auto adjusted. but after I renamed to something in english, the cluster is freaking out, "cant find master domain: u'spUUID=xxxxxxx, msdUUID=xxxxxxx' " and under Storage: Storage DOmains, the Data(Master) is down. How can I recover from this ASAP? :-(

2 4

New VM from Template and Storage size
by Erez Zarum 16 Jun '20

16 Jun '20

Hey, I have created a template that the disk is a thick (raw) with a size of 15GB. I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template. So far the only solution I managed to find is to adjust the size after creating the VM. For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk. I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance? Thanks!

1 0

oVirt 4.4 Self-hosted Engine and Intel Skylake CPUs
by Erez Zarum 16 Jun '20

16 Jun '20

Hey, I was trying to install oVirt with SE on a node that has Intel Skylake CPU (Intel Xeon Gold 6238R CPU to be precise) which by Intel supports TSX. When the SE was provisioned as a local VM all was working well, it was using a different CPU type for local provisioning. After the local SE VM was migrated to the shared Storage (iSCSI) and was configured, it failed to start. When checking the XML (and vm.conf) that was created and provided to libvirt I noticed it uses the "Secure Intel Skylake" type CPU with +tsx-ctrl as a required flag. My assumption as this is a fresh install of oVirt with SE is that the newly created Cluster was set to this CPU compatibility. This specific CPU by Intel does not expose any tsx flags, while it does indeed support TSX libvirt has no way of knowing it, more strange, some other CPUs from that same range/models do expose the tsx flag. I have tried to set the kernel cmdline to tsx=yes|auto|off and none of those helped. The quick solution was to start the engine manually by editing the XML file (hosted-engine --vm-shutdown and then start it with libvirt) and change the Cluster CPU type and the HostedEngine CPU type as well to "Intel Skylake" and then start it (hosted-engine --vm-start) Another solution which i haven't tried is to get the correct string from the oVirt-Engine API of the non-secure Intel Skylake CPU and hardcode it into the cpu_model fact in the SE ansible role (task). At the end i opted not to try any workaround and decided to go on with oVirt 4.3 which went smooth, it chose "Intel Skylake Server IBRS SSBD MDS Family" as the Cluster CPU compatibility and installation went without any errors/issues. 1) What will happen if i decide to upgrade to 4.4? I will first have to reinstall a node with CentOS 8 and then migrate the HostedEngine to there as well, will it keep the current cluster CPU type or will it try to upgrade and these fail the upgrade? 2) Are you aware of this situation? I understand this is a new solution because you had to update everytime the CPU databases but on the other hand, Intel is not helping here by not being strict about exposing the tsx flags, perhaps the best will be to let the user chose which CPU type use on the first Cluster created by the SE ansible role? (As far as i remember, this was available in the previous versions of oVirt) Thanks!

2 2

oVirt-4.4 on CetOS 8.2
by Dominik Holler 16 Jun '20

16 Jun '20

Hello, CentOS 8.2 was released before oVirt was prepared for CentOS 8.2 . Currently oVirt-4.4 fails to install on CentOS 8.2 . This will be fixed soon. Dominik

2 2

Continuing HE install from lost connection
by Glenn Marcy 16 Jun '20

16 Jun '20

I ran the Prepare VM stage of the GUI HostedEngine install and when I came back it had disconnected. Looking at the logs and the current status everything appears to be just fine, but there doesn't seem to be any way in the GUI to continue where it left off. I was wondering if there was some way to provide the hosted_storage information requested in the next panel and complete the installation, perhaps with the command line, instead of redoing all of the work that has already been completed successfully? Regards, Glenn Marcy

2 1

Advise Needed - Hosted Engine Minor Update
by jrbdeguzman05＠gmail.com 16 Jun '20

16 Jun '20

Hi Guys! How do you usually backup your hosted engine prior minor updates? I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently. I’ve used engine-backup before updating and for restore. However, the problem I’m encountering now is that, it looks like the hosted-engine settings are only being restored. The version is still 4.3.9 when I’m trying to revert it to 4.3.8. Am I missing some steps aside from engine-backup —restore? I saw on old posts that snapshots of hosted engine is not a recommended step before upgrade/update. Appreciate your help in advance!

3 3

LDAP setup fails on 4.4 reading PEM file
by Stack Korora 15 Jun '20

15 Jun '20

Greetings, I'm having some issues getting LDAP working on CentOS 8 with oVirt 4.4. I would appreciate some help please. When I run ovirt-engine-extension-aaa-ldap-setup I choose "11 - RFC-2307 Schema (Generic)" because that's what my LDAP guy said I should do. :-) Next I select the default Yes for "Use DNS". I select 4 for "Failover between multiple hosts". I put in my two hosts "svr1.my.domain srv2.my.domain". To select the protocol I type "ldaps". To select the method to obtain the PEM I type "File". Then the "File path". A full path to the file. Not quoted. Yes, I checked that I typed it correct. I can copy-paste into "ls" and it's fine with the correct read permissions and everything. (I can't copy paste into the script but that's another issue.) It immediately fails with: [ ERROR ] Failed to execute stage 'Environment customization': a byte-like object is required, not 'str' There is a log file, here is the snippet at the point it goes wrong. 2020-06-11 11:35:49,915-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND File path: 2020-06-11 11:36:24,373-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:RECEIVE /etc/pki/ca-trust/source/anchors/Infrastructure.pem 2020-06-11 11:36:24,375-0500 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine-extension-aaa-ldap/setup/bin/../plugins/ovirt-engine-extension-aaa-ldap/ldap/common.py", line 781, in _customization_late cacert, cacertfile, insecure = self._getCACert() File "/usr/share/ovirt-engine-extension-aaa-ldap/setup/bin/../plugins/ovirt-engine-extension-aaa-ldap/ldap/common.py", line 357, in _getCACert _cacertfile.write('\n'.join(cacert) + '\n') File "/usr/lib64/python3.6/tempfile.py", line 485, in func_wrapper return func(*args, **kwargs) TypeError: a bytes-like object is required, not 'str' 2020-06-11 11:36:24,376-0500 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment customization': a bytes-like object is required, not 'str' 2020-06-11 11:36:24,376-0500 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2020-06-11 11:36:24,376-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2020-06-11 11:36:24,376-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'TypeError'>, TypeError("a bytes-like object is required, not 'str'",), <traceback object at 0x7f7e053a4448>)]' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/hosts=str:'svr1.my.domain srv2.my.domain' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/protocol=str:'ldaps' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/serverset=str:'failover' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/useDNS=bool:'True' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_CACERT_FILE=str:'/etc/pki/ca-trust/source/anchors/Infrastructure.pem' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_CACERT_METHOD=str:'file' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_PROTOCOL=str:'ldaps' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_SERVERSET=str:'4' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_USE_DNS=str:'yes' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/2/OVAAALDAP_LDAP_SERVERSET=str:'svr1.my.domain srv2.my.domain' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:779 ENVIRONMENT DUMP - END Can someone help please? Thanks!

2 4

It looks like big changes are happening, Centos moving from 8.1.1911 to 8.2.2004 perhaps
by Glenn Marcy 15 Jun '20

15 Jun '20

I hope this situation settles down before rc5 trying to run 4.4.1-rc4 hosted engine setup, got [ ERROR ] fatal: [localhost -> ovirt-engine.example.com] FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: Problem: package ovirt-engine-4.4.1.3-1.el8.noarch requires ovirt-provider-ovn >= 1.2.1, but none of the providers can be installed - package ovirt-provider-ovn-1.2.30-1.el8.noarch requires openvswitch >= 2.7, but none of the providers can be installed - cannot install the best candidate for the job - nothing provides librte_bitratestats.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_bus_pci.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_bus_vdev.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_bus_vmbus.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_cmdline.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_common_cpt.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9(DPDK_17.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9(DPDK_18.11)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_17.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_18.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_18.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_18.11)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_2.2)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_gro.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_gso.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_hash.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ip_frag.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_kvargs.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_latencystats.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mbuf.so.4()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mbuf.so.4(DPDK_2.1)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_member.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool.so.5()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool.so.5(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool.so.5(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool_bucket.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool_ring.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool_stack.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_meter.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_meter.so.2(DPDK_18.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_meter.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_metrics.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_net.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pci.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pdump.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_bnxt.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_e1000.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_enic.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_failsafe.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_i40e.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_ixgbe.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_mlx4.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_mlx5.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_netvsc.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_nfp.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_qede.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_ring.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_ring.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_tap.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_vdev_netvsc.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_vhost.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_virtio.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ring.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ring.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_17.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_17.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_2.1)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64", "rc": 1, "results": []}

2 1

Re: Problem with oVirt 4.4
by Yedidyah Bar David 15 Jun '20

15 Jun '20

On Mon, Jun 15, 2020 at 2:13 PM minnie.du(a)vinchin.com <minnie.du(a)vinchin.com> wrote: > > Hi, > > I tried to send the log to you by email, but it fails. So I have sent them to Google Drive. Please go to the link below to get them: > > https://drive.google.com/file/d/1c9dqkv7qyvH6sS9VcecJawQIg91-1HLR/view?usp=… > https://drive.google.com/file/d/1zYfr_6SLFZj_IpM2KQCf-hJv2ZR0zi1c/view?usp=… I did get them, but not engine logs. Can you please attach them as well? Thanks. vdsm.log.61 has: 2020-05-26 14:36:49,668+0000 ERROR (jsonrpc/6) [virt.vm] (vmId='e78ce69c-94f3-416b-a4ed-257161bde4d4') Live merge failed (job: 1c308aa8-a829-4563-9c01-326199c3d28b) (vm:5381) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5379, in merge bandwidth, flags) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f ret = attr(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 728, in blockCommit if ret == -1: raise libvirtError ('virDomainBlockCommit() failed', dom=self) libvirt.libvirtError: internal error: qemu block name 'json:{"backing": {"driver": "qcow2", "file": {"driver": "file", "filename": "/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/08f91e3f-f37b-4434-a183-56478b732c1b"}}, "driver": "qcow2", "file": {"driver": "file", "filename": "/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/5ba0d7e5-afa8-4d75-bc5a-1b077955a990"}}' doesn't match expected '/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/5ba0d7e5-afa8-4d75-bc5a-1b077955a990' Adding Eyal. Eyal, can you please have a look? Thanks. > > Best regards, > > Minnie Du--Presales & Business Development > > Mob : +86-15244932162 > Tel : +86-28-85530156 > Skype :minnie.du@vinchin.com > Email: minnie.du(a)vinchin.com > Website: www.vinchin.com > > F5, Building 8, National Information Security Industry Park, No.333 YunHua Road, Hi-Tech Zone, Chengdu, China > > > From: Yedidyah Bar David > Date: 2020-06-15 15:42 > To: minnie.du > CC: users > Subject: Re: [ovirt-users] Problem with oVirt 4.4 > On Mon, Jun 15, 2020 at 10:39 AM <minnie.du(a)vinchin.com> wrote: > > > > We have met a problem when testing oVirt 4.4. > > > > Our VM is on NFS storage. When testing the snapshot function of oVirt 4.4, we created snapshot 1 and then snapshot 2, but after clicking the delete button of snapshot 1, snapshot 1 failed to be deleted and the state of corresponding disk became illegal. Removing the snapshot in this state requires a lot of risky work in the background, leading to the inability to free up snapshot space. Long-term backups will cause the target VM to create a large number of unrecoverable snapshots, thus taking up a large amount of production storage. So we need your help. > > Can you please share relevant parts of engine and vdsm logs? Perhaps > open a bug and attach all of them, just in case. > > Thanks! > -- > Didi > > -- Didi

4 4

Re: [ANN] oVirt 4.4.1 Fourth Release Candidate is now available for testing
by Glenn Marcy 15 Jun '20

15 Jun '20

This candidate changes the version of the OpenStack Java API from 3.2.8 to 3.2.9, which isn't available in the repositories. Installation produces the error: [ ERROR ] fatal: [localhost -> ovirt-engine.example.com] FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: Problem: cannot install the best candidate for the job - nothing provides openstack-java-cinder-client >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-cinder-model >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-client >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-glance-client >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-glance-model >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-keystone-client >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-keystone-model >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-quantum-client >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-quantum-model >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch - nothing provides openstack-java-resteasy-connector >= 3.2.9 needed by ovirt-engine-4.4.1.3-1.el8.noarch", "rc": 1, "results": []} Regards, Glenn Marcy

2 1