April 2020 - Users - oVirt List Archives

deprecating export domain?
by Charles Kozler 30 Aug '20

30 Aug '20

Hello, I recently read on this list from a redhat member that export domain is either being deprecated or looking at being deprecated To that end, can you share details? Can you share any notes/postings/bz's that document this? I would imagine something like this would be discussed in larger audience This seems like a somewhat significant change to make and I am curious where this is scheduled? Currently, a lot of my backups rely explicitly on an export domain for online snapshots, so I'd like to plan accordingly Thanks!

11 21

Support for Shared SAS storage
by Vinícius Ferrão 13 Aug '20

13 Aug '20

Hello, I’ve two compute nodes with SAS Direct Attached sharing the same disks. Looking at the supported types I can’t see this on the documentation: https://www.ovirt.org/documentation/admin-guide/chap-Storage.html There’s is local storage on this documentation, but my case is two machines, both using SAS, connected to the same machines. It’s the VRTX hardware from Dell. Is there any support for this? It should be just like Fibre Channel and iSCSI, but with SAS instead. Thanks,

7 11

oVirt thrashes Docker network during installation
by thomas＠hoberg.net 30 Jul '20

30 Jul '20

I want to run containers and VMs side by side and not necessarily nested. The main reason for that is GPUs, Voltas mostly, used for CUDA machine learning not for VDI, which is what most of the VM orchestrators like oVirt or vSphere seem to focus on. And CUDA drivers are notorious for refusing to work under KVM unless you pay $esla. oVirt is more of a side show in my environment, used to run some smaller functional VMs alongside bigger containers, but also in order to consolidate and re-distribute the local compute node storage as a Gluster storage pool: Kibbutz storage and compute, if you want, very much how I understand the HCI philosophy behind oVirt. The full integration of containers and VMs is still very much on the roadmap I believe, but I was surprised to see that even co-existence seems to be a problem currently. So I set-up a 3-node HCI on CentOS7 (GPU-less and older) hosts and then added additional (beefier GPGPU) CentOS7 hosts, that have been running CUDA workloads on the latest Docker-CE v19 something. The installation works fine, I can migrate VMs to these extra hosts etc., but to my dismay Docker containers on these hosts lose access to the local network, that is the entire subnet the host is in. For some strange reason I can still ping Internet hosts, perhaps even everything behind the host's gateway, but local connections are blocked. It would seem that the ovritmgmt network that the oVirt installation puts in breaks the docker0 bridge that Docker put there first. I'd consider that a bug, but I'd like to gather some feedback first, if anyone else has run into this problem. I've repeated this several times in completely distinct environments with the same results: Simply add a host with a working Docker-CE as an oVirt host to an existing DC/cluster and then try if you can still ping anyone on that net, including the Docker host from a busybox container afterwards (should try that ping just before you actually add it). No, I didn't try this with podman yet, because that's separate challenge with CUDA: Would love to know if that is part of QA for oVirt already.

5 9

Shutdown procedure for single host HCI Gluster
by Gianluca Cecchi 25 Jul '20

25 Jul '20

Hello, I'm testing the single node HCI with ovirt-node-ng 4.3.9 iso. Very nice and many improvements over the last time I tried it. Good! I have a doubt related to shutdown procedure of the server. Here below my steps: - Shutdown all VMs (except engine) - Put into maintenance data and vmstore domains - Enable Global HA Maintenance - Shutdown engine - Shutdown hypervisor It seems that the last step doesn't end and I had to brutally power off the hypervisor. Here the screenshot regarding infinite failure in unmounting /gluster_bricks/engine https://drive.google.com/file/d/1ee0HG21XmYVA0t7LYo5hcFx1iLxZdZ-E/view?usp=… What would be the right step to do before the final shutdown of hypervisor? Thanks, Gianluca

3 10

Upgrade ovirt from 3.4 to 4.3
by lu.alfonsi＠almaviva.it 19 Jun '20

19 Jun '20

Good morning, i have a difficult enviroment with 20 Hypervisors based on ovirt 3.4.3-1 and i would like to reach the 4.3 version. Which are the best steps to achieve these objective? Thanks in advance Luigi

3 10

Re: Single instance scaleup.
by Strahil 05 Jun '20

05 Jun '20

Hi Leo, As you do not have a distributed volume , you can easily switch to replica 2 arbiter 1 or replica 3 volumes. You can use the following for adding the bricks: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Admi… Best Regards, Strahil NikolivOn May 26, 2019 10:54, Leo David <leoalex(a)gmail.com> wrote: > > Hi Stahil, > Thank you so much for yout input ! > > gluster volume info > > > Volume Name: engine > Type: Distribute > Volume ID: d7449fc2-cc35-4f80-a776-68e4a3dbd7e1 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 > Transport-type: tcp > Bricks: > Brick1: 192.168.80.191:/gluster_bricks/engine/engine > Options Reconfigured: > nfs.disable: on > transport.address-family: inet > storage.owner-uid: 36 > storage.owner-gid: 36 > features.shard: on > performance.low-prio-threads: 32 > performance.strict-o-direct: off > network.remote-dio: off > network.ping-timeout: 30 > user.cifs: off > performance.quick-read: off > performance.read-ahead: off > performance.io-cache: off > cluster.eager-lock: enable > Volume Name: ssd-samsung > Type: Distribute > Volume ID: 76576cc6-220b-4651-952d-99846178a19e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 > Transport-type: tcp > Bricks: > Brick1: 192.168.80.191:/gluster_bricks/sdc/data > Options Reconfigured: > cluster.eager-lock: enable > performance.io-cache: off > performance.read-ahead: off > performance.quick-read: off > user.cifs: off > network.ping-timeout: 30 > network.remote-dio: off > performance.strict-o-direct: on > performance.low-prio-threads: 32 > features.shard: on > storage.owner-gid: 36 > storage.owner-uid: 36 > transport.address-family: inet > nfs.disable: on > > The other two hosts will be 192.168.80.192/193 - this is gluster dedicated network over 10GB sfp+ switch. > - host 2 wil have identical harware configuration with host 1 ( each disk is actually a raid0 array ) > - host 3 has: > - 1 ssd for OS > - 1 ssd - for adding to engine volume in a full replica 3 > - 2 ssd's in a raid 1 array to be added as arbiter for the data volume ( ssd-samsung ) > So the plan is to have "engine" scaled in a full replica 3, and "ssd-samsung" scalled in a replica 3 arbitrated. > > > > > On Sun, May 26, 2019 at 10:34 AM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Hi Leo, >> >> Gluster is quite smart, but in order to provide any hints , can you provide output of 'gluster volume info <glustervol>'. >> If you have 2 more systems , keep in mind that it is best to mirror the storage on the second replica (2 disks on 1 machine -> 2 disks on the new machine), while for the arbiter this is not neccessary. >> >> What is your network and NICs ? Based on my experience , I can recommend at least 10 gbit/s interfase(s). >> >> Best Regards, >> Strahil Nikolov >> >> On May 26, 2019 07:52, Leo David <leoalex(a)gmail.com> wrote: >>> >>> Hello Everyone, >>> Can someone help me to clarify this ? >>> I have a single-node 4.2.8 installation ( only two gluster storage domains - distributed single drive volumes ). Now I just got two identintical servers and I would like to go for a 3 nodes bundle. >>> Is it possible ( after joining the new nodes to the cluster ) to expand the existing volumes across the new nodes and change them to replica 3 arbitrated ? >>> If so, could you share with me what would it be the procedure ? >>> Thank you very much ! >>> >>> Leo > > > > -- > Best regards, Leo David

4 5

Failed to add storage domain
by thunderlight1＠gmail.com 31 May '20

31 May '20

Hi! I have installed oVirt using the iso ovirt-node-ng-installer-4.3.2-2019031908.el7. I the did run the Host-engine deployment through Cockpit. I got an error when it tries to create the domain storage. It sucessfully mounted the NFS-share on the host. Bellow is the error I got: 2019-04-14 10:40:38,967+0200 INFO ansible skipped {'status': 'SKIPPED', 'ansible_task': u'Check storage domain free space', 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_type': 'task'} 2019-04-14 10:40:38,967+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fb6918ad9d0> kwargs 2019-04-14 10:40:39,516+0200 INFO ansible task start {'status': 'OK', 'ansible_task': u'ovirt.hosted_engine_setup : Activate storage domain', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_type': 'task'} 2019-04-14 10:40:39,516+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Activate storage domain kwargs is_conditional:False 2019-04-14 10:40:41,923+0200 DEBUG var changed: host "localhost" var "otopi_storage_domain_details" type "<type 'dict'>" value: "{ "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py\", line 664, in main\n storage_domains_module.post_create_check(sd_id)\n File \"/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py\", line 526, in post_create_check\n id=storage_domain.id,\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py\", line 3053, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 232, in _internal_add\n return future.wait() if wait else future\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 55, in wait\n return self._code(response)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 229, in callback\n self._check_fault(response)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 132, in _check_fault\n self._raise_error(response , body)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 118, in _raise_error\n raise error\nError: Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400.\n", "failed": true, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400." }" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "play_hosts" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u'Activate storage domain', 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, u\'exception\': u\'Traceback (most recent call last):\\n File "/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py", line 664, in main\\n storage_domains_module.post_create_check(sd_id)\\n File "/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py", line 526', 'task_duration': 2, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'} 2019-04-14 10:40:41,924+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fb691843190> kwargs ignore_errors:None 2019-04-14 10:40:41,928+0200 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "00:37 Minutes", "ansible_result": "type: <type 'dict'>\nstr: {u'localhost': {'unreachable': 0, 'skipped': 6, 'ok': 23, 'changed': 1, 'failures': 1}}", "ansible_type": "finish", "status": "FAILED" } 2019-04-14 10:40:41,928+0200 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:01 ] Force facts gathering [ 00:01 ] Check local VM dir stat [ 00:01 ] Obtain SSO token using username/password credentials [ 00:01 ] Fetch host facts [ < 1 sec ] Fetch cluster ID [ 00:01 ] Fetch cluster facts [ 00:01 ] Fetch Datacenter facts [ < 1 sec ] Fetch Datacenter ID [ < 1 sec ] Fetch Datacenter name [ 00:02 ] Add NFS storage domain [ 00:01 ] Get storage domain details [ 00:01 ] Find the appliance OVF [ 00:01 ] Parse OVF [ < 1 sec ] Get required size [ FAILED ] Activate storage domain 2019-04-14 10:40:41,928+0200 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7fb69404eb90> kwargs Any suggestions on how fix this?

2 2

How to connect to a guest with vGPU ?
by Josep Manel Andrés Moscardó 29 May '20

29 May '20

Hi, I got vGPU through mdev working but I am wondering how I would connect to the client and make use of the GPU. So far I try to access the console through SPICE and at some point in the boot process it switches to GPU and I cannot see anything else. Thanks. -- Josep Manel Andrés Moscardó Systems Engineer, IT Operations EMBL Heidelberg T +49 6221 387-8394

3 4

Issues encountered performing HE install on 4.3
by Alan G 24 May '20

24 May '20

Hi, I hit a few issues while performing a recent HE install of 4.3. While I managed to find solutions/workarounds to all the problems I thought I might share them here * As defined in the Ansible defaults the temp dir for building the local HE VM is /var/tmp. I was 80M short of the required space and there did not appear to be a (supported) way to specify a different location. I ended up having to do a bind mount of /var/tmp to get me through the install. Would be nice to be able to specify a custom location. * Permissive umask required. Our CIS CentOS 7 build requires that default umask is 027. This breaks the installer as it creates the VM image under /var/tmp as root and cannot then access it as qemu user. As the temp files are cleaned up on failure it took me a while to track this one down. My solution was to temporarily set the umask to 022 for the session while running the installer. It would be nice if the installer either handled this by doing a chmod/chown as required, or at least doing a umask pre-check and failing with a meaningful error. * SSH root login required on host. Again for CIS we have "PermitRoologin no" configured in sshd. This means the add host task fails on the Engine, but instead of a hard failure we get a timeout on the installer. Which left me chasing some imagined routing/bridging/DNS issue. Eventually I realised I could get to the engine logs and found the issue but took several hours. Would be nice if the installer could either support a sudo option or at least perform a root login pre-check and fail with a meaningful error. Thanks, Alan

2 1

Upgrade scenario to 4.4 for HCI Gluster
by Gianluca Cecchi 11 May '20

11 May '20

Hello, I saw from some mails in the list that the approach for upgrading from 4.3 to 4.4 will be similar to the 3.6 => 4.0 one. Reading the RHV 4.0 Self Hosted Engine Guide it seems it was necessary to have a second host, going through this: 5.4. Upgrading a RHEV-H-Based Self-Hosted Engine Environment https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/ht… and also https://www.ovirt.org/develop/release-management/features/sla/hosted-engine… upgrade process involved: - set global ha maintenance - install a new host (and set it as on hosted engine one) - migrate engine VM to this host and set the host as the SPM - create a backup with engine-backup, verify its contents and copy to the host in some directory - run the upgrade utility on the host to update the engine VM hosted-engine --upgrade-appliance this will create a backup floating disk of the engine vm disk for rollback purposes and override the existing engine disk with a new one where to deploy the new engine version applying also the restore from the engine-backup --> what are requirements for 4.4 engine VM and so free storage to have on engine storage domain? The engine-setup will be automatically executed on the new version engine VM - exit from global maintenance - update remaining hosts Is the above procedure the correct one that I can test on a 4.3.9 lab? The 3.6 -> 4.0 flow implied that a 4.0 host could run a 3.6 engine VM Because the backup disk operation is done by the current running engine itself. So it should be true also for 4.3 -> 4.4 and a 4.4. host should be able to run a 4.3 engine, correct? In case of single 4.3.9 ovirt-node-ng host HCI with Gluster, can I apply the upgrade in a similar way? Something like: - create engine-backup and copy over to the host - put host into global maintenace - shutdown all VMS, engine included - enable 4.4. repo - install new image-base 4.4 is this correct and I can use 4.3 and 4.4 image base versions or do I have to sort-of-scratch necessarily? because 4.3 host is based on el7 while 4.4 on el8... but perhaps on mage based system I have flexibility..? what version of gluster will it be applied? Incompatibilities with the current 4.3.9 one (version 6.8-1.el7) - reboot host - exit global maintenance and wait for engine vm to come up correctly - enter global maintenance again - run the upgrade utility on the host Or do I need at least temporarily a new server to use as the 4.4. host, or what will be the expected path? Thanks, Gianluca

2 3

Ubuntu 18.04 and 16.04 cloud images hang at boot up
by suaro＠live.com 07 May '20

07 May '20

I'm using oVirt 4.3 (latest ) and able to successfully provision Centos VMs without any problems. When I attempt to provision Ubuntu VMs, they hang at startup. The console shows : ... ... [ 4.010016] Btrfs loaded [ 101.268594] random: nonblocking pool is initialized It stays like this indefinitely. Again, I have no problems with Centos images, but need Ubuntu Any tips greatly appreciated.

3 2

Backup software recommendations
by Colin Coe 06 May '20

06 May '20

Hi all I'm looking for recommendations for backup software. It needs to handle physical and virtual Linux and Windows, RHV and Hyper-V. It doesn't have to be open source and it doesn't have to be free. The main features we need are: - disk to disk backups - inter-site replication with rate limiting - be able to handle Linux thin volumes (think RHGS) - support BMR ans granular file / directory restore - correctly handle Windows VSS - support RHEL point releases as soon as they are released I'm as much after "stay away from" as recommendations. We currently use Arcserve UDP and it is ... well ... sub optimal Thanks in advance CC

3 4

Gluster deployment fails with missing UUID
by Shareef Jalloq 05 May '20

05 May '20

Hi, I'm running the gluster deployment flow and am trying to use a second drive as the gluster volume. It's /dev/sdb on each node and I'm using the JBOD mode. I'm seeing the following gluster ansible task fail and a google search doesn't bring up much. TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** failed: [ovirt-gluster-01.jalloq.co.uk] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"ansible_loop_var": "item", "changed": false, "err": " Couldn't find device with uuid Y8FVs8-LP6w-R6CR-Yosh-c40j-17XP-ttP3Np.\n Couldn't find device with uuid tA4lpO-hM9f-S8ci-BdPh-lTve-0Rh1-3Bcsfy.\n Couldn't find device with uuid RG3w6j-yrxn-2iMw-ngd0-HgMS-i5dP-CGjaRk.\n Couldn't find device with uuid lQV02e-TUZE-PXCd-GWEd-eGqe-c2xC-pauHG7.\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}

4 11

oVirt 4.4.0 Beta release refresh is now available for testing
by Sandro Bonazzola 03 May '20

03 May '20

oVirt 4.4.0 Beta release refresh is now available for testing The oVirt Project is excited to announce the availability of the beta release of oVirt 4.4.0 refresh (beta 4) for testing, as of April 17th, 2020 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.3. Important notes before you try it Please note this is a Beta release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. In particular, please note that upgrades from 4.3 and future upgrades from this beta to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Beta require content that will be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 beta yet due to some incompatibility in openvswitch package shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2. Known Issues - ovirt-imageio development is still in progress. In this beta you can’t upload images to data domains using the engine web application. You can still copy iso images into the deprecated ISO domain for installing VMs or upload and download to/from data domains is fully functional via the REST API and SDK. For uploading and downloading via the SDK, please see: - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_d… - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/download… Both scripts are standalone command line tool, try --help for more info. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0 Beta? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support only for file based storage. iSCSI/FC storage do not support 4k disks yet. - Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 4

Engine UI exception while viewing unattached hosts in Network tab
by Shareef Jalloq 03 May '20

03 May '20

Hi, I'm following the Gluster setup blog post ( https://blogs.ovirt.org/2018/02/up-and-running-with-ovirt-4-2-and-gluster-s…) and am at the 'Storage network' section. I've created a new 'gluster' network, selected the network and navigated to the 'Hosts' tab. The guide tells you to click the 'Unattached' button and then 'Setup Host Networks' for each host. However, clicking the 'Unattached' button fires off a bunch of exceptions rather than displaying my 3 hosts. The message is: "Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'N' of null Please have your administrator check the UI logs" Anyone seen this before? Where is the UI log located? Shareef.

3 3

Unable to remove system roles from Everyone group
by miguel.garcia＠toshibagcs.com 02 May '20

02 May '20

I opened Everyone group and added system role UserRole and realized now that everybody can see all VMS which is not good. I tried to remove the role from the group but got the error "Error while executing action: It's not allowed to remove system permissions assigned to built-in Everyone group" Looking into Ovirt forums I see that this change should be made through the engine database but I was not able to reach that part. Can someone help me out how to remove the system role from Everyone group? or at least reset the group?

2 1

Running Host on sudo user
by carl langlois 30 Apr '20

30 Apr '20

Hi, I was wandering if it is possible to run ovirt node using a sudo user instead of the root user? Let says i want or need to disable root ssh login.. Thanks and regards. Carl

3 3

Can we agree on adding reference to version in help request email?
by Sandro Bonazzola 30 Apr '20

30 Apr '20

Hi, I was looking in the past 2 weeks email landing on this mailing list and a common thing I notice is that it's hard to understand which version of the involved software they're referring too. Can we agree on adding at the top of the message a couple of line like output of yum -q list installed centos-release ovirt-release\* ovirt-engine redhat-release vdsm glusterfs centos-release.x86_64 7-7.1908.0.el7.centos glusterfs.x86_64 6.8-1.el7 ovirt-engine.noarch 4.3.9.4-1.el7 ovirt-release43.noarch 4.3.9-1.el7 It will help understanding if the help request is something that may be already known, a regression, and so on. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

3 2

Add custom Network Filter to oVirt
by Hendrik Peyerl 30 Apr '20

30 Apr '20

Hello all, can anyone give me a hint on where to find documentation on how to add custom created network filters through oVirt? Thanks, Hendrik

3 5

Re: Move Hosted Engine VM to a different storage domain
by Yedidyah Bar David 30 Apr '20

30 Apr '20

On Wed, Apr 29, 2020 at 8:42 AM Anton Louw <Anton.Louw(a)voxtelecom.co.za> wrote: > > > Hi, > > > > Thank you for the reply. I am building another environment today, so I > will run through the backup and restore again. I do recall one issue I had > with the restore was that it gave an error that one of the storage domains > were already in use. This was a new storage domain I added, with no VMs on. > > > > I just want to make sure, I probably cannot deploy the HE on a storage > domain that is in maintenance, correct? I will try and create a new storage > domain again, but remove it from the data center, and perhaps see if the HE > will deploy to it. > hosted-engine deploy does not require an "empty storage domain" (in maintenance or not), but one that "does not exist yet" - meaning, a path to storage that will be used as a storage domain, but in which a storage domain was not created yet. The deploy process itself will create the domain there. I hope this clarifies. > > > The main goal was to have no downtime, but if it is going to be too > complex, I think my next option will be to create a new HE, and attach the > current storage domains. Obviously it is going to take a bit of planning, > as I will need to configure all the networks etc. from scratch again. > Good luck and keep us updated! Best regards, > > > Thanks > > > > *Anton Louw* > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > [image: F] <https://www.facebook.com/voxtelecomZA> > [image: T] <https://www.twitter.com/voxtelecom> > [image: I] <https://www.instagram.com/voxtelecomza/> > [image: L] <https://www.linkedin.com/company/voxtelecom> > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > *From:* Strahil Nikolov <hunter86_bg(a)yahoo.com> > *Sent:* 26 April 2020 08:55 > *To:* Yedidyah Bar David <didi(a)redhat.com>; Anton Louw < > Anton.Louw(a)voxtelecom.co.za> > *Cc:* users(a)ovirt.org > *Subject:* Re: [ovirt-users] Re: Move Hosted Engine VM to a different > storage domain > > > > On April 26, 2020 9:39:07 AM GMT+03:00, Yedidyah Bar David < > didi(a)redhat.com> wrote: > >On Fri, Apr 24, 2020 at 1:04 PM Anton Louw > ><Anton.Louw(a)voxtelecom.co.za> > >wrote: > > > >> > >> > >> Hi All, > >> > >> > >> > >> I know this question has been asked before, by myself included. I was > >> hoping that someone has run through the exercise of moving the hosted > >> engine VM to a different storage domain. I have tried many routes, > >but the > >> backup and restore does not work for me. > >> > > > >The "standard answer" is backup and restore. Why does it not work? > > > > > >> > >> > >> Is there anybody that can perhaps give me some guidelines or a > >process I > >> can follow? > >> > > > >I didn't try that myself. > > > >The best guidelines I can give you are: Try first on at a test system. > >Do > >the backup on the real machine, create some isolated VM (isolated so > >that > >it does not interfere with your hosts/storage) somewhere to be used as > >a > >test host (or a physical machine if you have one), some storage > >somewhere, > >and restore on it. Make it work. Document what you needed to do. Ask > >here > >with specific questions if/when you have them. Then do on the > >production > >setup. > > > >Also clarify your needs. Do you need no-downtime for the VMs? If so, > >that's > >more complex. If you don't, it might be enough/simpler to deploy a new > >setup and just import the existing storage. Do you have HA VMs? etc. > > > > > >> > >> > >> The reason I need to move the HE VM is because we are decommissioning > >the > >> current storage array where the HE VM is located. > >> > > > >Good luck! > > > >Best regards, > > > > > >> > >> > >> Thank you very much > >> > >> *Anton Louw* > >> *Cloud Engineer: Storage and Virtualization* at *Vox* > >> ------------------------------ > >> *T:* 087 805 0000 | *D:* 087 805 1572 > >> *M:* N/A > >> *E:* anton.louw(a)voxtelecom.co.za > >> *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > >> www.vox.co.za > >> > >> [image: F] <https://www.facebook.com/voxtelecomZA> > >> [image: T] <https://www.twitter.com/voxtelecom> > >> [image: I] <https://www.instagram.com/voxtelecomza/> > >> [image: L] <https://www.linkedin.com/company/voxtelecom> > >> [image: Y] <https://www.youtube.com/user/VoxTelecom> > >> > >> [image: #VoxBrand] > >> <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > >> *Disclaimer* > >> > >> The contents of this email are confidential to the sender and the > >intended > >> recipient. Unless the contents are clearly and entirely of a personal > >> nature, they are subject to copyright in favour of the holding > >company of > >> the Vox group of companies. Any recipient who receives this email in > >error > >> should immediately report the error to the sender and permanently > >delete > >> this email from all storage devices. > >> > >> This email has been scanned for viruses and malware, and may have > >been > >> automatically archived by *Mimecast Ltd*, an innovator in Software as > >a > >> Service (SaaS) for business. Providing a *safer* and *more useful* > >place > >> for your human generated data. Specializing in; Security, archiving > >and > >> compliance. To find out more Click Here > >> <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > >> > >> > >> _______________________________________________ > >> Users mailing list -- users(a)ovirt.org > >> To unsubscribe send an email to users-leave(a)ovirt.org > >> Privacy Statement: https://www.ovirt.org/privacy-policy.html > >> oVirt Code of Conduct: > >> https://www.ovirt.org/community/about/community-guidelines/ > >> List Archives: > >> > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/V3PRBRZD7SLUQ… > >> > > If youchange the gluster volume you can use the 'hosted-engine' tool + > migration of the data ? > > The example is for Gluster, but also > hosted-engine --set-shared-config storage <server1>:/engine > > hosted-engine --set-shared-config mnt_options > backup-volfile-servers=<server2>:<server3> > > Best Regards, > Strahil Nikolov > > -- Didi

1 0

Failed to complete VM creation,help me!
by liug74＠sina.com 30 Apr '20

30 Apr '20

Storage domain usage is as follows： vgdisplay 3542ca36-747b-407c-aa5e-331510f81fd9 --- Volume group --- VG Name 3542ca36-747b-407c-aa5e-331510f81fd9 System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 15998 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1954 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 113.97 TiB PE Size 128.00 MiB Total PE 933647 Alloc PE / Size 64930 / <7.93 TiB Free PE / Size 868717 / 106.04 TiB VG UUID GiL1LL-ggO5-a6mX-62uc-q597-B3X9-6bzC93 __________________________________________________________ The following error occurred when I created the VM: VDSM H5 command HSMGetAllTasksStatusesVDS failed: Error creating a new volume: (u"Volume creation 62220be2-2781-4771-9373-84af5cc18f01 failed: (28, 'Sanlock resource write failure', 'No space left on device')",) Excuse me, what's the reason, thank you!

3 2

ovrt node ng 4.4 different fs layout and error if changed
by Gianluca Cecchi 29 Apr '20

29 Apr '20

Hello, In CentOS 7 default filesystem in anaconda was xfs, but in ovirt node ng 4.3.9 (based on CentOS 7) the default layout was set to ext4. In CentOS 8 again the default is xfs and I see that ovirt node ng 4.4 beta4 (based on CentOS 8.1) has now xfs for all filesystems, excluded /boot that is set to ext4. In general I have a preference for ext4. I notice that while in 4.3.9 I could somehow customize partition layout, even if not recommended, in 4.4 I always get error if I don't accept automatic partitioning. What I sometimes do: - select disk and custom layout - click done and the storage page appears - I click the button to create automatically and I get the automatic partitioning layout - and here I can change fs type and update settings button and/or change size of some filesystems (eg for /var/log if using Gluster) Even if I only set all filesystems automatically generated by installer to ext4, without changing any size, in the final stage of installation I get this error and installation aborts: " There was an error running the kickstart script at line 5. This is a fatal error and installation will be aborted. The details of this error are: 2020-04-19 10:37:50,451 [INFO] (MainThread) Trying to create a manageable base from '/' 2020-04-19 10:37:50,811 [ERROR] (MainThread) LVM Thin Provisioning partitioning scheme is required. For autoinstall via Kickstart with LVM Thin Provisioning check options: --thinpool and --grow. Please consult documentation for details Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3.6/site-packages/imgbased/__main__.py", line 53, in <module> CliApplication() File "/usr/lib/python3.6/site-packages/imgbased/__init__.py", line 82, in CliApplication app.hooks.emit("post-arg-parse", args) File "/usr/lib/python3.6/site-packages/imgbased/hooks.py", line 120, in emit cb(self.context, *args) File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line 171, in post_argparse layout.initialize(args.source, args.init_nvr) File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line 215, in initialize self.app.imgbase.init_layout_from(source, init_nvr) File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 293, in init_layout_from self.init_tags_on(existing_lv) File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 271, in init_tags_on pool = lv.thinpool() File "/usr/lib/python3.6/site-packages/imgbased/lvm.py", line 305, in thinpool raise MissingLvmThinPool() imgbased.lvm.MissingLvmThinPool " If I change nothing and choose automatic partitioning the installation completes. Tried different times with same results. Is it expected? In this case instead of specifying "recommended" it should be written sort of "mandatory"... Gianluca

2 1

Problem with multiple IP addresses and AWX
by Bernhard Dick 29 Apr '20

29 Apr '20

Hi, I've started to use awx shortly and I'd like to have an inventory based on their RHEV/oVirt-Plugin. Basically that works fine, however on machines that have multiple network interfaces or internal nets (like Docker) the first address in the IP list of the vm (which is used as ansible_host by AWX) is not an address that is reachable from the machine's outside and so those host entries are failing in my jobs. I found an issue at AWX, being like we won't fix first: https://github.com/ansible/awx/issues/1191 It also seems that there where issues related to this on oVirt: First this with a request for setting a primary IP: https://bugzilla.redhat.com/show_bug.cgi?id=1437145 And this one mentioning a way to ignore interfaces on ovirt-guest-agent, however it does no longer work due to the use of qemu-guest-agent: https://bugzilla.redhat.com/show_bug.cgi?id=1437145 Do you have any ideas how to circumvent this or is there some improvement alread in planning? Best regards Bernhard

1 0

Re: User Groups
by Lucie Leistnerova 29 Apr '20

29 Apr '20

On 4/29/20 9:35 AM, Anton Louw wrote: > > > Hi Paul, > > Thanks. Its just strange, because when I want to assign group > permissions to a VM for instance, I get the below: > > But when I check, Administration, Users then select Groups, I only see > the below: > These are the groups added to RHV manually (check button Add or Administration - Configure - System Permissions - Add) and Everyone (built-in group). So they can be used to assign permissions. > > Am I missing something? > > 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> > > > *From:*Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > *Sent:* 29 April 2020 09:28 > *To:* Anton Louw <Anton.Louw(a)voxtelecom.co.za>; users(a)ovirt.org > *Subject:* Re: User Groups > > Hello Anton, > > In the Administration->Users there is a groups > button. > > Regards, > > Paul S. > > ------------------------------------------------------------------------ > > *From:*Anton Louw <Anton.Louw(a)voxtelecom.co.za > <mailto:Anton.Louw@voxtelecom.co.za>> > *Sent:* 29 April 2020 06:36 > *To:* users(a)ovirt.org <mailto:users@ovirt.org> <users(a)ovirt.org > <mailto:users@ovirt.org>> > *Subject:* [ovirt-users] User Groups > > *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, > > Is there a way to see My Groups through the Web UI? I have tried > looking around, but cannot see anything. Can this only be seen via the > backend in the HE? > > Thanks > > *Anton Louw* > > *Cloud Engineer: Storage and Virtualization*at *Vox* > > ------------------------------------------------------------------------ > > *T:*087 805 0000 | *D:*087 805 1572 > *M:*N/A > *E:*anton.louw@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/ > > > > _______________________________________________ > 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/EOORL4GYWM5XS… -- Lucie Leistnerova Senior Quality Engineer, QE Cloud, RHVM Red Hat EMEA IRC: lleistne @ #rhev-qe

1 0

Can't ping gluster interfaces for HCI setup
by Shareef Jalloq 29 Apr '20

29 Apr '20

Hi, I'm in the process of trying to set up an HCI 3 node cluster in my homelab to better understand the Gluster setup and have failed at the first hurdle. I've set up the node interfaces on the built in NIC and am using a PCI NIC for the Gluster traffic - at the moment this is 1Gb until I can upgrade - and I've assigned a static IP to both interfaces and also have both entries in my DNS. From any of the three nodes, I can ping the gateway, the other nodes, any external IP but I can't ping any of the Gluster NICs. What have I forgotten to do? Here's the relevant output of 'ip addr show'. em1 is the motherboard NIC and p1p1 is port 1 of an Intel NIC. The /etc/sysconfig/network-scripts/ifcfg-<if> scripts are identical aside from IPADDR, NAME, DEVICE and UUID fields. Thanks, Shareef. [root@ovirt-node-00 ~]# ip addr show 2: p1p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:36:9f:1f:f9:78 brd ff:ff:ff:ff:ff:ff inet 10.0.0.34/24 brd 10.0.0.255 scope global noprefixroute p1p1 valid_lft forever preferred_lft forever inet6 fd4d:e9e3:6f5:1:a236:9fff:fe1f:f978/64 scope global mngtmpaddr dynamic valid_lft 7054sec preferred_lft 7054sec inet6 fe80::a236:9fff:fe1f:f978/64 scope link valid_lft forever preferred_lft forever 4: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 98:90:96:a1:16:ad brd ff:ff:ff:ff:ff:ff inet 10.0.0.31/24 brd 10.0.0.255 scope global noprefixroute em1 valid_lft forever preferred_lft forever inet6 fd4d:e9e3:6f5:1:9a90:96ff:fea1:16ad/64 scope global mngtmpaddr dynamic valid_lft 7054sec preferred_lft 7054sec inet6 fe80::9a90:96ff:fea1:16ad/64 scope link valid_lft forever preferred_lft forever

3 11