- Users - oVirt List Archives

oVirt node 4.4.1 deploy FQDN not reachable
by Roberto Nunin 25 Aug '20

25 Aug '20

Hi all I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso. When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks) If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries. As already stated, these names are certainly resolved by DNS used. Any hints about ? -- Roberto Nunin

3 5

Actual oVirt install questions
by David White 25 Aug '20

25 Aug '20

:) Ok, after all of the questions I've pestered you guys with, I'm actually getting started. Thank you all for your help. A few of questions right off the bat. For this install, I'm installing the latest (4.4.2) onto CentOS 8. 1) What's the difference between the `ovirt-hosted-engine-setup` command and the `engine-setup` command? I ran both of them, and it seems like they do the exact same thing. 2) For either of the commands above, I'm able to get as far as the step where it asks about the storage: Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs] It's clear to me that using this install method, the storage should be setup first / independently of the installer. So ok, I'll try the Cockpit install, since the documentation says that's the preferred method anyway. (I'm just a sucker for the command line, doing it myself, and understanding everything that I'm doing. I like to avoid GUIs if I can help it. LOL). So I logged into the Cockpit Dashboard at {ip-address}:9090, clicked on 'Virtualization' then clicked on Hosted Engine. Here, I clicked on Hyperconvered, and since I'm just installing to a single host right now, I clicked on Run Gluster Wizard for Single Node. So here's my 3rd question. 3) I can't get past the first step of this wizard. It is asking for the FQDN of the host (Host1). - The documentation indicates that this is NOT the base OS, but I've tried that - I've also tried the IP address that I intend to use for the manager (i.e. what I envision is akin to the vCenter IP address for a vSphere environment -- correct?) In both cases, the wizard won't let me proceed, and keeps saying "Host is not added to known_hosts" What am I missing, here? I'm familiar with the known_hosts file... but that's the VM / manager that I'm trying to create, I thought? Why does the wizard continue to give me that error message? Sent with ProtonMail Secure Email.

4 13

Guest agent ubuntu 20.04
by carl langlois 24 Aug '20

24 Aug '20

Hi, This may not be the right place to ask but any of you is using Ubuntu 20.04 guest. I have noticed that the guest agent is not present in the repo.. Regards Carl

4 4

Is oVirt suited for supporting long-lived VMs than OpenStack?
by yam yam 24 Aug '20

24 Aug '20

Hi guys, I'm wondering why people say oVirt is better suited for traditional workloads like long-lived VMs than OpenStack. does oVirt have some additional features for it? Of course, VMs in OpenStack might be intentionally killed according to resource pressure if auto-scaling is used. but otherwise, I guess OpenStack has enough to run long-lived VMs. thanks.

3 6

Incremental VM backups
by Kevin Doyle 24 Aug '20

24 Aug '20

Hi I am looking at ways to backup VM's, ideally that support incremental backups. I have found a couple of python scripts that snapshot a VM and back it up but not incremental. The question is what do you use to backup the VM's ? (both linux and windows) Thanks Kevin

5 6

[ANN] oVirt 4.4.2 Fourth Release Candidate is now available for testing
by Lev Veyde 23 Aug '20

23 Aug '20

oVirt 4.4.2 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Fourth Release Candidate for testing, as of August 20th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.2/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

VMware import : older SSL version problems
by Philip Brown 23 Aug '20

23 Aug '20

using ovirt 4.4.1 to attempt to import from VMware, I have a problem with older SSL ciphers: libvirt.libvirtError: internal error: curl_easy_perform() returned an error: SSL connect error (35) : error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol where can I tell it "shut up and take the data"? I found on the web a generic openssl reference that supposedly I should be able to edit /etc/pki/tls/openssl.cnf and add MinProtocol=TLSv1.0 CipherString = DEFAULT@SECLEVEL=1 but that didnt help. its still complaining about the SSL protocol. -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

2 1

ovirt-imageio : can't upload / download
by Michael Jones 23 Aug '20

23 Aug '20

Hi, I have image upload/download working on some older ovirt servers where it still has the split daemon/proxy... on one newer one this feature is not working; software in use: CentOS 8 ovirt-engine-4.4.1.10-1.el8.noarch ovirt-imageio-client-2.0.9-1.el8.x86_64 ovirt-imageio-daemon-2.0.9-1.el8.x86_64 ovirt-imageio-common-2.0.9-1.el8.x86_64 the ui test button allowed me to work out 50-vdsm.conf was setting the wrong remote port... (was 54322, changed to 54323) updated remote with; [remote] host = 0.0.0.0 port = 54323 the test now passes, but on upload or download it still fails. Next i changed the control to be unix socket instead of tcp port 54324 (vdsm was giving an error: Image daemon is unsupported); I looked up the error line in the vdsm code, and found it was looking for unix socket: DAEMON_SOCK=/run/ovirt-imageio/sock switching to sock seemed to resolve all errors in the vdsm log; --- content of the imageio log; no errors as far as i can see: 2020-08-18 12:49:56,109 INFO (MainThread) [server] Starting (pid=2696562, version=2.0.9) 2020-08-18 12:49:56,109 DEBUG (MainThread) [services] Creating remote.service on port 54323 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Prefer IPv4: False 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Available network interfaces: [(<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('0.0.0.0', 54323))] 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Creating server socket with family=AddressFamily.AF_INET and type=SocketKind.SOCK_STREAM 2020-08-18 12:49:56,111 DEBUG (MainThread) [services] Securing server (cafile=/etc/pki/vdsm/certs/cacert.pem, certfile=/etc/pki/vdsm/certs/vdsmcert.pem, keyfile=/etc/pki/vdsm/keys/vdsmkey.pem) 2020-08-18 12:49:56,113 INFO (MainThread) [services] remote.service listening on ('0.0.0.0', 54323) 2020-08-18 12:49:56,113 DEBUG (MainThread) [services] Creating local.service on socket '\x00/org/ovirt/imageio' 2020-08-18 12:49:56,113 INFO (MainThread) [services] local.service listening on '\x00/org/ovirt/imageio' 2020-08-18 12:49:56,113 DEBUG (MainThread) [services] Creating control.service on socket '/run/ovirt-imageio/sock' 2020-08-18 12:49:56,113 DEBUG (MainThread) [uhttp] Removing socket '/run/ovirt-imageio/sock' 2020-08-18 12:49:56,113 INFO (MainThread) [services] control.service listening on '/run/ovirt-imageio/sock' 2020-08-18 12:49:56,115 DEBUG (MainThread) [server] Changing ownership of /run/ovirt-imageio to 988:984 2020-08-18 12:49:56,115 DEBUG (MainThread) [server] Changing ownership of /var/log/ovirt-imageio/daemon.log to 988:984 2020-08-18 12:49:56,115 DEBUG (MainThread) [server] Dropping root privileges, running as 988:984 2020-08-18 12:49:56,116 DEBUG (MainThread) [services] Starting remote.service 2020-08-18 12:49:56,116 DEBUG (remote.service) [services] remote.service started 2020-08-18 12:49:56,116 DEBUG (MainThread) [services] Starting local.service 2020-08-18 12:49:56,117 DEBUG (local.service) [services] local.service started 2020-08-18 12:49:56,117 DEBUG (MainThread) [services] Starting control.service 2020-08-18 12:49:56,117 DEBUG (control.service) [services] control.service started 2020-08-18 12:49:56,117 INFO (MainThread) [server] Ready for requests 2020-08-18 12:51:34,602 INFO (Thread-1) [http] OPEN client=local 2020-08-18 12:51:34,603 INFO (Thread-1) [tickets] [local] ADD ticket={'dirty': False, 'ops': ['read'], 'filename': 'debian-10.3.0-amd64-netinst.iso.raw', 'size': 351272960, 'sparse': True, 'transfer_id': 'ec7b329e-3ef1-448d-ac73-1e5e1b4c0ef9', 'uuid': '17db8f9f-3280-4e7c-8fbf-e5326e1f98be', 'timeout': 300, 'url': 'file:///rhev/data-center/mnt/_var_local_ovirt_local__data/7ee98037-126b-4c79-b921-a9ff4272fa91/images/315af697-a064-4c2c-bdf6-8144a8218526/8e709a79-4da0-4d91-803e-d6ec12ec84c3'} 2020-08-18 12:51:34,603 DEBUG (Thread-1) [http] Empty request line, client disconnected 2020-08-18 12:51:34,603 INFO (Thread-1) [http] CLOSE client=local [connection 1 ops, 0.000842 s] [dispatch 1 ops, 0.000305 s] --- vdsm log for transfer id: ec7b329e-3ef1-448d-ac73-1e5e1b4c0ef9 no errors as far as i can see... 2020-08-18 12:51:34,602+0000 INFO (jsonrpc/5) [vdsm.api] START add_image_ticket(ticket={'dirty': False, 'ops': ['read'], 'filename': 'debian-10.3.0-amd64-netinst.iso.raw', 'size': 351272960, 'sparse': True, 'transfer_id': 'ec7b329e-3ef1-448d-ac73-1e5e1b4c0ef9', 'uuid': '17db8f9f-3280-4e7c-8fbf-e5326e1f98be', 'timeout': 300, 'url': 'file:///rhev/data-center/mnt/_var_local_ovirt_local__data/7ee98037-126b-4c79-b921-a9ff4272fa91/images/315af697-a064-4c2c-bdf6-8144a8218526/8e709a79-4da0-4d91-803e-d6ec12ec84c3'}) from=::ffff:37.187.146.167,58882, flow_id=19204d8c-ffe6-4c45-81fe-96e07097d519, task_id=441bf5ea-1e93-4b5b-aeae-f0e52b43cf62 (api:48) 2020-08-18 12:51:34,603+0000 INFO (jsonrpc/5) [vdsm.api] FINISH add_image_ticket return=None from=::ffff:37.187.146.167,58882, flow_id=19204d8c-ffe6-4c45-81fe-96e07097d519, task_id=441bf5ea-1e93-4b5b-aeae-f0e52b43cf62 (api:54) 2020-08-18 12:51:34,603+0000 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.add_image_ticket succeeded in 0.00 seconds (__init__:312) --- engine log: urn [status=Status [code=0, message=Done]], log id: 7ac2f68b 2020-08-18 12:51:34,604Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Started transfer session with ticket id 17db8f9f-328 0-4e7c-8fbf-e5326e1f98be, timeout 300 seconds 2020-08-18 12:51:34,604Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Adding image ticket to ovirt-imageio-proxy, id 17db8 f9f-3280-4e7c-8fbf-e5326e1f98be 2020-08-18 12:51:34,604Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Failed to add image ticket to ovirt-imageio-proxy: C onnection refused (Connection refused): java.lang.RuntimeException: Connection refused (Connection refused) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.getConnection(ImageioClient.java:114) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.putTicket(ImageioClient.java:65) is there a way for me to validate where engine thinks the proxy is? the test button passed after changing remote port to 54323... any help much appreciated. Kind Regards, Michael Jones

3 14

Max running ansible-playbook
by Tommaso - Shellrent 21 Aug '20

21 Aug '20

Hi to all. on our angine we always see max 2 ansible-playbook running on the same time. How can we ingrease this value? Regards. -- -- Shellrent - Il primo hosting italiano Security First *Tommaso De Marchi* /COO - Chief Operating Officer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155> | Fax 04441492177

2 3

HCI Cluster Configuration
by Clint Boggio 20 Aug '20

20 Aug '20

Ovirt 4.3.9 HCI Gluster 3 Dell 730XD Managed Engine When I finished the "hosted engine deploy" I failed to add the gluster storage according to the documentation and i'd like to get that back on track. 1. I ticked the check box in the cluster configuration to "enable gluster service", all of my current gluster storage domains went "red triangle" on me and the hosts also went "red triangle" so I quickly changed it back and all went back to normal. Do I need to check that box to make the "Use Managed Gluster Volume" check box and drop down menu show my HCI gluster volumes that exist on the three nodes ? Do I need to put the storage domain(s) in maintenance mode to change them from unmanaged to managed ? Will the system honor the VM(s) that live in my "engine" and "vmstore" gluster volumes which are currently in use in the system if/when I change them from unmanaged to managed,or will the system wipe them and hose my managed engine and VMs ? Thank you for your help !

1 0

Re: Help remove snapshot
by Shani Leviim 20 Aug '20

20 Aug '20

Hi Magnus, Sounds like you triggered this one https://bugzilla.redhat.com/show_bug.cgi?id=1555116. The error message you've got was meant to avoid removing a snapshot from a broken chain. On the Active VM snapshot -> Disks, is there any disk with Illegal status? Deleting the whole snapshot can be done from the DB: *delete from snapshots where snapshot_id = '.....';* Although it's recommended to understand the root cause for that one. Can you please share your engine.log? *Regards,* *Shani Leviim* On Mon, Aug 17, 2020 at 1:37 PM Magnus Isaksson <magnus(a)vmar.se> wrote: > Hi! > > I would need some help removing a snapshot that looks like this. > How do i remove it manually or fix snapshot definition? > ----------------- > Error while executing action: > > TUN_SALDC01: > > - The requested snapshot has an invalid parent, either fix the > snapshot definition or remove it manually to complete the process. > > ----------------- > And when i look at the disk on tha tnapshot it show as this: > > > And general info: > > _______________________________________________ > 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/5QEBPZPUHDGS5… >

3 3

Re-creating ISO Storage Domain after Manager Rebuild
by bob.franzke＠mdaemon.com 19 Aug '20

19 Aug '20

Hi All, Late last year I had a disk issue with my Ovirt Manager Server that required I rebuild it and restored from backups. While this worked mostly, one thing that did not get put back correctly was the physical storage location of an ISO domain on the manager server. I believe this was previously set up as an NFS share being hosted on the Manager Server itself. The physical disk path and filesystem were not re-created on the manager server's local disk. So after the restore, the ISO domain shows up in the Ovirt Admin portal but shows the as down, and inactive. If I go into the domain, the 'Manage Domain' and 'Remove' buttons are not available. The only option I have for this is 'Destroy'. I right now have no ability to do things like boot a VM from a CD and am assuming its because the ISO domain that the images for this would be stored on is not available. How can I recreate this ISO domains to be able to upload ISO images that VM machines can boot from.The original path on the manager server was /gluster: sdc 8:32 0 278.9G 0 disk ├─sdc1 8:33 0 1G 0 part /boot └─sdc2 8:34 0 277.9G 0 part ├─centos_mydesktop-root 253:0 0 50G 0 lvm / ├─centos_mydesktop-swap 253:1 0 23.6G 0 lvm [SWAP] ├─centos_mydesktop-home 253:2 0 25G 0 lvm /home └─centos_mydesktop-gluster 253:3 0 179.3G 0 lvm /gluster The current layout is now: â””â”€sda3 8:3 0 277.7G 0 part â”œâ”€centos-root 253:0 0 50G 0 lvm / â”œâ”€centos-swap 253:1 0 4G 0 lvm [SWAP] â””â”€centos-home 253:2 0 223.7G 0 lvm /home Can I just create a new filesystem here, destroy the old ISO domain, and add a new one using the new path? I am a total Ovirt Noob so would appreciate any help here. Thanks. Bob

5 5

Problem with "ceph-common" pkg for oVirt Node 4.4.1
by m.andreev＠2500baden.eu 19 Aug '20

19 Aug '20

Hi! I have a problem with install ceph-common package(needed for cinderlib Managed Block Storage) in oVirt Node 4.4.1 - oVirt doc say: "$ yum install -y ceph-common" but no Repo with ceph-common ver 12.2.7 for CentOS8 - official CentOS has only "ceph-common-10.2.5-4.el7.x86_64.rpm" and CEPH has only ceph-common ver. 14.2 for EL8 How can I install ceph-common ver. 12.2.7? BR Mike

3 2

Upgrade Memory of oVirt Nodes
by souvaliotimaria＠mail.com 19 Aug '20

19 Aug '20

Hello everyone, I have an oVirt 4.3.2.5 hyperconverged 3 node production environment and we want to add some RAM to it. Can I upgrade the RAM without my users noticing any disruptions and keep the VMs running? The way I thought I should do it was to migrate any running VMs to the other nodes, then set one node in maintenance mode, shut it down, place the new memory, bring it back up, remove it from maintenance mode and see how the installation reacts and repeat for the other two nodes. Is this correct or should I follow another way? Will there be a problem during the time when the nodes will not be identical in their resources? Thank you for your time, Souvalioti Maria

4 5

OVirt hosted engine setup dnf config
by Raphael Höser 19 Aug '20

19 Aug '20

Hi all, I'm currently installing OVirt 4.4 on CentOS 8 in an hosted engine setup and it fails during ovirt-hosted-engine-setup. Because of our corporate proxy, some changes to the dnf.conf is needed (namely proxy_auth_method=basic) and the config is working fine when running dnf commands the normal way. Proxy configuration is provided via http_proxy, https_proxy and ftp_proxy env vars. The setup fails during a DNF call with status code 407 (proxy auth required). Is there another way to provide that config or any other way to resolve this? My googling didn't help me yet. On the same machine I had a running OVirt 4.3 on CentOS 7 running as a test and now wanted to upgrade (after a complete wipe). Thanks for your help, Raphael content of /etc/dnf/dnf.conf: [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True best=True skip_if_unavailable=False proxy_auth_method=basic timeout=120 minrate=90 Log of ovirt-hosted-engine-setup: [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine. The locally running engine will be used to configure a new storage domain and create a VM there. At the end the disk of the local VM will be moved to the shared storage. Are you sure you want to continue? (Yes, No)[Yes]: Configuration files: Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200818091958-tozsht.log Version: otopi-1.9.2 (otopi-1.9.2-1.el8) [ INFO ] DNF Downloading 1 files, 0.00KB [ INFO ] DNF Downloaded CentOS-8 - AppStream [ INFO ] DNF Errors during downloading metadata for repository 'AppStream': - Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.68) - Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.67) [ ERROR ] DNF Failed to download metadata for repo 'AppStream': Cannot prepare internal mirrorlist: Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.67) [ ERROR ] Failed to execute stage 'Environment setup': Failed to download metadata for repo 'AppStream': Cannot prepare internal mirrorlist: Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.67) [ INFO ] Stage: Clean up [Some more cleanup]

3 8

Re: Help remove snapshot
by Shani Leviim 19 Aug '20

19 Aug '20

Hi Magnus, You can find the VM's snapshot by sending a REST API request http://localhost:8080/ovirt-engine/api/vms/<vm-id>/snapshots/ You can also find the VM's snapshots (and view their parameters) by using SQL: select * from snapshots where vm_id = '<vm-id>'; You can also delete the relevant snapshot by specifying the snapshot's description: *delete from snapshots where description = '.....';* *Regards,* *Shani Leviim* On Tue, Aug 18, 2020 at 7:50 PM Magnus Isaksson <magnus(a)vmar.se> wrote: > Hi Shani > > Thanks for the help. > > What i can see it does not display any illegal statuses. > > I am a bit unsure how to delete it from the DB, how do i find the > snapshot_id? > > Cheers > Magnus > > ------------------------------ > *From:* Shani Leviim <sleviim(a)redhat.com> > *Sent:* 17 August 2020 13:45 > *To:* Magnus Isaksson <magnus(a)vmar.se> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Help remove snapshot > > Hi Magnus, > Sounds like you triggered this one > https://bugzilla.redhat.com/show_bug.cgi?id=1555116. > The error message you've got was meant to avoid removing a snapshot from a > broken chain. > > On the Active VM snapshot -> Disks, is there any disk with Illegal status? > > Deleting the whole snapshot can be done from the DB: > *delete from snapshots where snapshot_id = '.....';* > > Although it's recommended to understand the root cause for that one. > > Can you please share your engine.log? > > > *Regards, * > > *Shani Leviim * > > > On Mon, Aug 17, 2020 at 1:37 PM Magnus Isaksson <magnus(a)vmar.se> wrote: > > Hi! > > I would need some help removing a snapshot that looks like this. > How do i remove it manually or fix snapshot definition? > ----------------- > Error while executing action: > > TUN_SALDC01: > > - The requested snapshot has an invalid parent, either fix the > snapshot definition or remove it manually to complete the process. > > ----------------- > And when i look at the disk on tha tnapshot it show as this: > > > And general info: > > _______________________________________________ > 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/5QEBPZPUHDGS5… > >

1 0

HA Storage options
by David White 19 Aug '20

19 Aug '20

Hi, I started an email thread a couple months ago, and felt like I got some great feedback and suggestions on how to best setup an oVirt cluster. Thanks for your responses thus far.My goal is to take a total of 3-4 servers that I can use for both the storage and the virtualization, and I want both to be highly available. You guys told me about oVirt Hyperconverged with Gluster, and that seemed like a great option. However, I'm concerned that this may not actually be the best approach. I've spoken with multiple people at Red Hat who I have a relationship with (outside of the context of the project I'm working on here), and all of them have indicated to me that Gluster is being deprecated, and that most of the engineering focus these days is on Ceph. I was also told by a Solutions Architect who has extensive experience with RHV that the hyperconverged clusters he used to build would always give him problems. Does oVirt support DRBD or Ceph storage? From what I can find, I think that the answer to both of those is, sadly, no. So now I'm thinking about switching gears, and going with iSCSI instead. But I'm still trying to think about the best way to replicate the storage, and possibly use multipathing so that it will be HA for the VMs that rely on it. Has anyone else experienced problems with the Gluster hyperconverged solution? Am I overthinking this whole thing, and am I being too paranoid? Is it possible to setup some sort of software-RAID with multiple iSCSI targets? As an aside, I now have a machine that I was planning to begin doing some testing and practicing with. Previous to my conversations with the folks at Red Hat, I was planning on doing some initial testing and config with this server before purchasing another 2-3 servers to build the hyperconverged cluster. Sent with ProtonMail Secure Email.

4 3

Cannot access Engine VM
by Steven Bach 18 Aug '20

18 Aug '20

Hello All, I installed Ovirt node 4.4.1.5 from the ovirt ISO, IP 192.168.1.53/24 I setup the self hosted engine by logging into the web interface, configured it for 192.168.1.55/24 IP on the default generated bridge interface and setup a FQDN that is resolvable via DNS. Setup NFS storage, and all seems good. The Engine VM is running, but I cannot access it at all outside the node. SSH'd in the node I can ping the engine, anything else on that same subnet cannot SSH or even ping it (Again, DNS is resolving correctly to the IP Address). I am able to SSH into the engine from the node. While SSH'd into the Engine from the node, I can only ping the Node and nothing beyond that, not able to install ovirt repo, nothing. Any ideas are greatly appreciated, thank you, -- Steven Bach sbach(a)bachnetworks.com

2 1

Re: Help with problem in oVirt 4.4.
by Nir Soffer 18 Aug '20

18 Aug '20

On Tue, Aug 18, 2020 at 6:07 AM Rodrigo Mauriz <rmauriz(a)gmail.com> wrote: Hi Rodrigo, I'm moving the discussion to ovirt users list, which is the right place to discuss this: https://lists.ovirt.org/archives/list/users%40ovirt.org/ > When I try to upload an ISO file by: > > Storage -> Storage Domains -> Disks > I get an error: > "Connection to ovirt-imageio-proxy service failed. Make sure service is installed, configured, and ovirt-engine certificate is registered as valid CA in browser." > > Review and note that the services that perform this task were not installed in the ovirt-engine: > • ovirt-imageio-proxy This package does not exist and not needed in ovirt 4.4 > • ovirt-imageio-daemon > • ovirt-imageio-common These packages are needed, and installed when you instal ovirt-engine. The ovirt-imageio service is configured automatically when you run engine-setup. > Example: > #systemctl status ovirt-imageio-proxy (not installed) > > I tried to install it but it throws it an error: > > #yum install ovirt-imageio-proxy engine-setup > > Updating Subscription Management repositories. > Unable to read consumer identity > This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. > Last metadata expiration check: 0:41:46 Aug on Fri 07 Aug 2020 10:20:42 AM -04. > No match for argument: ovirt-imageio-proxy > No match for argument: engine-setup > Error: Unable to find a match: ovirt-imageio-proxy engine-setup This is correct, ovirt-imageio-proxy is not needed and does not exist. > The same, for the engine-iso-uploader I think the iso uploader was deprecated a long time ago, and it is not needed to upload images. > I asked a person who works at Red Hat and they told me that this apps (services) are not released yet. Uploading images from the UI was available in ovirt 4.4.0, but is fully functional since ovirt 4.4.1. We know about hone issue - if you replaced apache certificates with 3rd party certificates, uploading via ovirt-imageio service on engine host (as a proxy) will not work: https://bugzilla.redhat.com/1866745 https://bugzilla.redhat.com/1862107 If you are using engine built certificates, upload and download should work. We may have more info about the failure in engine log. Please share the log showing the time when you tried to upload an image. Nir

1 0

Glusterfs version
by suporte＠logicworks.pt 17 Aug '20

17 Aug '20

Hello, What is the compatibility gluster version to work with oVirt 4.4.1 ? Thanks -- Jose Ferradeira http://www.logicworks.pt

2 1

Help remove snapshot
by Magnus Isaksson 17 Aug '20

17 Aug '20

Hi! I would need some help removing a snapshot that looks like this. How do i remove it manually or fix snapshot definition? ----------------- Error while executing action: TUN_SALDC01: * The requested snapshot has an invalid parent, either fix the snapshot definition or remove it manually to complete the process. ----------------- And when i look at the disk on tha tnapshot it show as this: [cid:98462a7f-dbb6-447e-925a-5b170883d7c7] And general info: [cid:9264e2e0-459f-4b54-aba7-08b3bf1f4068]

1 0

How to diable dhcp in ovirt network
by Adam Xu 17 Aug '20

17 Aug '20

Hi everyone Recently, when I install okd on ovirt. The installation process was failed because the vm automatically acquired an IP address from DHCP before the installer assigned it. Our DHCP is enabled by a layer 3 switch, I tried to diable dhcp using network filter. but there is no entry related to blocking the DHCP feature. Is there any way for ovirt to disable DHCP? -- Adam Xu

2 1

Help needed - Not able to find Windows Guest agent in 4.4.1.10-1.el8 Hosted Engine
by dhanaraj.ramesh＠yahoo.com 17 Aug '20

17 Aug '20

Hi Team, unable to locate Windows guest agant iso in 4.4.1.10-1.el8 Hosted Engine version. please share us where can i get the iso? there is no /usr/share/oVirt-guest-tools-iso/oVirt-tools-setup.iso available in 4.4.1 HE

3 2

Migration not working
by Juan Pablo Lorier 17 Aug '20

17 Aug '20

Hi, I'm having issues with migration to some hosts. I have a 4 node cluster and I tried updating to see if it fixes but it's still failing. The reason is nos clear in the engine log. 2020-08-14 09:45:32,322-03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-429) [364e7777] EVENT_ID: VM_MIGRATION_START_SYSTEM_INITIAT ED(67), Migration initiated by system (VM: medialist2-videoteca, Source: virt2.tnu.com.uy, Destination: virt3.tnu.com.uy, Reason: ). 2020-08-14 09:45:32,336-03 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-429) [535a8bdb] Lock Acquired to object 'EngineLock:{exclusiveLocks='[aac7468 5-c969-4761-923f-043400176edf=VM]', sharedLocks=''}' 2020-08-14 09:45:32,355-03 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-429) [535a8bdb] Running command: MigrateVmToServerCommand internal: true. Ent ities affected : ID: aac74685-c969-4761-923f-043400176edf Type: VMAction group MIGRATE_VM with role type USER 2020-08-14 09:45:32,383-03 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-429) [535a8bdb] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId= '634f3f64-8945-470c-b31c-b8d4c73109e6', vmId='aac74685-c969-4761-923f-043400176edf', srcHost='virt2.tnu.com.uy', dstVdsId='f9e441a0-a4e6-4548-8c6f-83a958120f02', dstHost='virt4. tnu.com.uy:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth= '125', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action= {name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, pa rams=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='172.16.100.45'}), log id: 1db80717 2020-08-14 09:45:32,385-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-429) [535a8bdb] START, MigrateBrokerVDSCommand(HostName = virt 2.tnu.com.uy, MigrateVDSCommandParameters:{hostId='634f3f64-8945-470c-b31c-b8d4c73109e6', vmId='aac74685-c969-4761-923f-043400176edf', srcHost='virt2.tnu.com.uy', dstVdsId='f9e4 41a0-a4e6-4548-8c6f-83a958120f02', dstHost='virt4.tnu.com.uy:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompre ssed='false', consoleAddress='null', maxBandwidth='125', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDow ntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, para ms=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='172.1 6.100.45'}), log id: 4085b503 2020-08-14 09:45:32,433-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-429) [535a8bdb] FINISH, MigrateBrokerVDSCommand, return: , log id: 4085b503 2020-08-14 09:45:32,437-03 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-429) [535a8bdb] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 1db8 0717 2020-08-14 09:45:32,446-03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-429) [535a8bdb] EVENT_ID: VM_MIGRATION_START_SYSTEM_INITIAT ED(67), Migration initiated by system (VM: reverse_proxy, Source: virt2.tnu.com.uy, Destination: virt4.tnu.com.uy, Reason: ). 2020-08-14 09:45:32,462-03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-429) [535a8bdb] EVENT_ID: USER_VDS_MAINTENANCE_WITHOUT_REASON(620), Host virt2.tnu.com.uy was switched to Maintenance mode by jplorier(a)tnu.com.uy. 2020-08-14 09:45:32,681-03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-14) [7667d149-886e-406b-9cd6-9b7472fa9944] Command 'MaintenanceNumberOfVdss' id: 'db97a747-115b-4f01-aa3d-6277080e6a44' child commands '[]' executions were completed, status 'SUCCEEDED' 2020-08-14 09:45:33,024-03 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [] Received first domain report for host virt2.tnu.com.uy 2020-08-14 09:45:33,686-03 INFO [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [7667d149-886e-406b-9cd6-9b7472fa9944] Ending command 'org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand' successfully. 2020-08-14 09:45:35,137-03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [] VM 'fd854ebe-144f-455f-bf0c-48167d7aae9f'(medialist2-videoteca) moved from 'MigratingFrom' --> 'Up' 2020-08-14 09:45:35,137-03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [] Adding VM 'fd854ebe-144f-455f-bf0c-48167d7aae9f'(medialist2-videoteca) to re-run list 2020-08-14 09:45:35,144-03 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [] Rerun VM 'fd854ebe-144f-455f-bf0c-48167d7aae9f'. Called from VDS 'virt2.tnu.com.uy' *In the host running the vm, I see no error related to the migration, only about Engine VM which seems to be working fine otherwise:* 2020-08-14 09:06:23,337-0400 ERROR (jsonrpc/3) [root] failed to retrieve Hosted Engine HA score '[Errno 2] No such file or directory'Is the Hosted Engine setup finished? (api:19 *VDSM version in node:* vdsm.x86_64 4.30.46-1.el7 @ovirt-4.3 All nodes are up to date. Thanks

3 3

oVirt nested on oVirt works, when you enable MAC spoofing on host VMs
by thomas＠hoberg.net 13 Aug '20

13 Aug '20

Howto: Create a new network profile that doesn't have the MAC spoofing filter included. In my case I used one without any filters, you may want to be more careful. Background: I had tried the nested approach with the default settings and found that the hosted-engine setup worked just find to the point where it was running as a nested VM on the install node, but that it failed to tie in the other gluster nodes or to communicate to the outside: There was something wrong with the network, but no obivous failures. I tried using other, simpler "client hypervisors" (it's all KVM anyway) VirtualBox and 'native' KVM and the symptoms were the same: The VMs ran just fine, but the network didn't connect. And then I remembered that obviously a Hypervisor need to override the MAC for each client VM if you want full network access and I had come across "no-mac-spoofing" often enough it somehow stayed on my mind... and finally it clicked. Anyhow, validing full functionality now and the main interest in this is the ability to do a full simulation/testing of oVirt 4.3->4.4 upgrades on 3-node HCI setups, which I'd rather not do on the live physical system. Of course, it's also quite cool!

1 0

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

[ANN] oVirt 4.4.2 Third Release Candidate is now available for testing
by Lev Veyde 13 Aug '20

13 Aug '20

oVirt 4.4.2 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Third Release Candidate for testing, as of August 13th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.2/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Request for feedback about "Overview of Networking in oVirt"
by Dominik Holler 12 Aug '20

12 Aug '20

Hello, there is a new documentation "Overview of Networking in oVirt" available in https://www.ovirt.org/documentation/networking-overview/ Please let me know if you have any questions, comments, suggestions, or any kind of critics about this text. If you want to improve, you could also create directly a Pull Request on https://github.com/ovirt/ovirt-site . Thanks Dominik

3 3

Is the udev settling issue more wide spread? Getting failed 'qemu-img -convert' also while copying disks between data and vmstore domains
by thomas＠hoberg.net 12 Aug '20

12 Aug '20

While trying to diagnose an issue with a set of VMs that get stopped for I/O problems at startup, I try to deal with the fact that their boot disks cause this issue, no matter where I connect them. They might have been the first disks I ever tried to sparsify and I was afraid that might have messed them up. The images are for a nested oVirt deployment and they worked just fine, before I shut down those VMs... So I first tried to hook them as secondary disks to another VM to have a look, but that just cause the other VM to stop at boot. Also tried downloading, exporting, and plain copying the disks to no avail, OVA exports on the entire VM fail again (fix is in!). So to make sure copying disks between volumes *generally* work, I tried copying a disk from a working (but stopped) VM from 'vmstore' to 'data' on my 3nHCI farm, but that failed, too! Plenty of space all around, but all disks are using thin/sparse/VDO on SSD underneath. Before I open a bug, I'd like to have some feedback if this is a standard QA test, this is happening to you etc. Still on oVirt 4.3.11 with pack_ova.py patched to wait for the udev settle, This is from the engine.log on the hosted-engine: 2020-08-12 00:04:15,870+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM gem2 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.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\\nqemu-img: error while reading sector 135168: 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 151552: Transport endpoint is not connected\\n')",) and this is from the vdsm.log on the gem2 node: Error: Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\nqemu-img: error while reading sector 135168: 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 151552: Transport endpoint is not connected\n') 2020-08-12 00:03:15,428+0200 ERROR (tasks/7) [storage.Image] Unexpected error (image:849) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/image.py", line 837, in copyCollapsed raise se.CopyImageError(str(e)) CopyImageError: 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.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\\nqemu-img: error while reading sector 135168: 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 151552: T ransport endpoint is not connected\\n')",) 2020-08-12 00:03:15,429+0200 ERROR (tasks/7) [storage.TaskManager.Task] (Task='6399d533-e96a-412d-b0c3-0548e24d658d') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1633, in copyImage postZero, force, discard) File "/usr/lib/python2.7/site-packages/vdsm/storage/image.py", line 837, in copyCollapsed raise se.CopyImageError(str(e)) CopyImageError: 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.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\\nqemu-img: error while reading sector 135168: 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 151552: T ransport endpoint is not connected\\n')",)

3 4

uprade from 4.3 to 4.4
by suporte＠logicworks.pt 12 Aug '20

12 Aug '20

Hello, is possible to upgrade from ovirt 4.3 to 4.4 ? Thanks -- Jose Ferradeira http://www.logicworks.pt

2 2

oVirt 4.4.0 Release is now generally available
by Sandro Bonazzola 12 Aug '20

12 Aug '20

oVirt 4.4.0 Release is now generally available The oVirt Project is excited to announce the general availability of the oVirt 4.4.0 Release, as of May 20th, 2020 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Some of the features included in the oVirt 4.4.0 release require content that will be available in CentOS Linux 8.2 but cannot be tested on RHEL 8.2 yet due to some incompatibility in the openvswitch package that is shipped in CentOS Virt SIG, which requires rebuilding openvswitch on top of CentOS 8.2. The cluster switch type OVS is not implemented for CentOS 8 hosts. Please note that oVirt 4.4 only supports clusters and datacenters with compatibility version 4.2 and above. If clusters or datacenters are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See users mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Installation instructions For the engine: either use the oVirt appliance or install CentOS Linux 8 minimal by following these steps: - Install the CentOS Linux 8 image 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.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…, selecting the minimal installation. - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. Update instructionsUpdate from oVirt 4.4 Release Candidate On the engine side and on CentOS hosts, you’ll need to switch from ovirt44-pre to ovirt44 repositories. In order to do so, you need to: 1. dnf remove ovirt-release44-pre 2. rm -f /etc/yum.repos.d/ovirt-4.4-pre-dependencies.repo 3. rm -f /etc/yum.repos.d/ovirt-4.4-pre.repo 4. dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm 5. dnf update On the engine side you’ll need to run engine-setup only if you were not already on the latest release candidate. On oVirt Node, you’ll need to upgrade with: 1. Move node to maintenance 2. dnf install https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/noarch/ovirt-node-ng-imag… 3. Reboot 4. Activate the host Update from oVirt 4.3 oVirt 4.4 is available only for CentOS 8. In-place upgrades from previous installations, based on CentOS 7, are not possible. For the engine, use backup, and restore that into a new engine. Nodes will need to be reinstalled. A 4.4 engine can still manage existing 4.3 hosts, but you can’t add new ones. For a standalone engine, please refer to upgrade procedure at https://ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 If needed, run ovirt-engine-rename (see engine rename tool documentation at https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html ) When upgrading hosts: You need to upgrade one host at a time. 1. Turn host to maintenance. Virtual machines on that host should migrate automatically to a different host. 2. Remove it from the engine 3. Re-install it with el8 or oVirt Node as per installation instructions 4. Re-add the host to the engine Please note that you may see some issues live migrating VMs from el7 to el8. If you hit such a case, please turn off the vm on el7 host and get it started on the new el8 host in order to be able to move the next el7 host to maintenance. What’s new in oVirt 4.4.0 Release? - 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 API/SDK v3 support deprecated in past versions. - 4K block disk support only for file-based storage. iSCSI/FC storage do not support 4K disks yet. - You can export a VM to a data domain. - You can edit floating disks. - Ansible Runner (ansible-runner) is integrated within the engine, enabling more detailed monitoring of playbooks executed from the engine. - Adding and reinstalling hosts is now completely based on Ansible, replacing ovirt-host-deploy, which is not used anymore. - 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/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/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

11 35

Reverting to Snapshot
by Christian Reiss 12 Aug '20

12 Aug '20

Hey folks, this, I hope, is a trivial question. But I really can't find the button for it. If you take a snapshot of any vm - how do you revert to that snapshot, discarding all changes after? I see options to clone, delete, take snapshot, preview... but revert? Really in the true sense of "discard all changes, go back to this snapshot state". What am I not seeing here? :) -- with kind regards, mit freundlichen Gruessen, Christian Reiss

2 2

oVirt Node 4.1.1 Hosted Engine Deployment Fibre Channel No LUNS found
by hkexdong＠yahoo.com.hk 12 Aug '20

12 Aug '20

I've an external RAID subsystem connect to the host by SAS cable (SFF-8644). I follow the instructions of the RAID card manufacture. Include the driver during host installation. And I can see the created RAID volumes (LUNs) available in "Installation Destination". Although I choose to install the engine in host local disk. The installation success and I proceed to hosted engine deployment by Cockpit. And now I stuck at part 4 Storage. I believe "Storage Type" select "Fibre Channel" is correct even I'm not using fibre cable. As NFS and iSCSI are utilize network. I confirm there are 2 RAID volume (LUN0 & LUN1) created in the external RAID subsystem. Why oVirt cannot discover them. What could be wrong :(

3 6

Hosted Engine Deployment stuck at 3. Prepare VM
by hkexdong＠yahoo.com.hk 12 Aug '20

12 Aug '20

oVirt Node version is 4.4.1. This version can successful deploy before. But after I compile the RAID driver. It now stuck at Prepare VM. The last message is "[ INFO ] TASK [ovirt.hosted_engine_setup : Install ovirt-engine-appliance rpm]" According to the instructions from RAID controller manufacture. I'd install the "kernel-headers-xxx.rpm" and "kernel-devel-xxx.rpm" which extracted from official CentOS 8.2.2004 ISO. Also include a bunch of packages for compile driver (e.g. gcc, make, zlib-devel, etc.) I think those packages ruined the deployment. But I still want to know it actually stuck at which part and the reason. Is there any way to check the deployment log?

5 4

ovirt4.4 and ldap auth with starttls
by Jiří Sléžka 11 Aug '20

11 Aug '20

Hello, better start new thread... it looks like tls1.0 is not supported anymore in ovirt-engine-extension-aaa-ldap I just migrated engine from 4.3 to 4.4 and cannot use my ldap profile because server_error: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(The server selected protocol version TLS10 is not accepted by client preferences [TLS12]), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb but when I try to force tls 1.0 by setting ... pool.default.ssl.startTLS = true pool.default.ssl.startTLSProtocol = TLSv1 ... I got server_error: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(No appropriate protocol (protocol is disabled or cipher suites are inappropriate)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb I can't switch to something better on server side, is it possible to allow weak ciphers/protocols on client side? Thanks in advance, Jiri

2 2

ovirt4.4.1 engine Deployment failure
by xilazz＠126.com 11 Aug '20

11 Aug '20

Hello, everyone I am using these versions for my test : - ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm - ovirt-node-ng-installer-4.4.1-2020072310.el8.iso But I'm always prompted when I'm hosting a cubide-engine deploy :The error was: error while evaluating conditional ((otopi_host_net.ansible_facts.otopi_host_net | length == 0)).The specific hints are:fatal: [localhost]: FAILED! => {"msg": "The conditional check '(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The error was: error while evaluating conditional ((otopi_host_net.ansible_facts.otopi_host_net | length == 0)): 'list object' has no attribute 'ansible_facts'\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml': line 29, column 13, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_host_net\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task. Only one syntax may be used.\n"} [ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook The test machine node has four network CARDS, but I haven't configured the team. I don't know why, it has been suffering for several days.I don't know if you've ever been in a situation like this, other than installing a lower version.

2 1

migrating standalone engine to selfhosted and upgrade from 4.3 to 4.4 in one step
by Jiří Sléžka 11 Aug '20

11 Aug '20

Hello, I have 4 host cluster managed with standalone engine in version 4.3 and I would like to migrate this standalone engine to 4.4 as hosted engine. I have two new hosts which I would like to use as base for new HE cluster. (new hosts are Intel based, old ones are AMD Opteron based - new cluster will have 4.4 compatibility, old one have to stay at 4.2 compatibility level). I red this https://www.ovirt.org/documentation/migrating_from_a_standalone_manager_to_… but the question is: Can I migrate and upgrade in one step? Have anybody did that already? If it is not possible what is a suggested approach? Thanks for help Jiri

2 4

hosted-engine upgrade from 4.3 to 4.4 fails with "Cannot edit VM."
by d＠sekretev.ru 10 Aug '20

10 Aug '20

Hi! hosted-engine --deploy --restore-from-file=ovirt_engine_full.arch fails with [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot edit VM. A VM running the engine ("hosted engine") cannot be set to highly available as it has its own HA mechanism.]". HTTP response code is 409. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Cannot edit VM. A VM running the engine (\"hosted engine\") cannot be set to highly available as it has its own HA mechanism.]\". HTTP response code is 409."} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook Can anybody help with this error? May be someone has access to this page https://access.redhat.com/solutions/5303571?

3 3

It is possible to export a vm bigger as 5 TB?
by miguel.garcia＠toshibagcs.com 10 Aug '20

10 Aug '20

We have a vm with many virtual drives and need to backup as ova file. Since this demands a lot of space I had mounted an nfs directory in the host but get next message after try to export ova: Error whle executing action: Cannot export VM. Invalid target folder: /mnt/shared2 on Host. You may refer to the engine.log file for further details. Looking at the engine.log file got this mesage: 2020-07-03 11:42:37,268-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Lock Acquired to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:42:37,275-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Executing Ansible command: /usr/bin/ansible-playbook --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config -v --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa --inventory=/tmp/ansible-inventory2275650137225503626 --extra-vars=target_directory="/nt/shared2" --extra-vars=validate_only="True" /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml [Logfile: /var/log/ovirt-engine/ova/ovirt-export-ova-validate-ansible-20200703114237-172.16.99.13-e357a397-3dc3-4566-900f-6e0e0cb39030.log] 2020-07-03 11:42:39,554-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Ansible playbook command has exited with value: 2 2020-07-03 11:42:39,555-04 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Validation of action 'ExportVmToOva' failed for user Miguel.Garcia. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName hyp11.infra,$directory /nt/shared2 2020-07-03 11:42:39,556-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Lock freed to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:44:53,021-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Lock Acquired to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:44:53,027-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Executing Ansible command: /usr/bin/ansible-playbook --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config -v --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa --inventory=/tmp/ansible-inventory3629946116235444875 --extra-vars=target_directory="/mnt/shared2" --extra-vars=validate_only="True" /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml [Logfile: /var/log/ovirt-engine/ova/ovirt-export-ova-validate-ansible-20200703114453-172.16.99.13-ba070d4b-5f76-4fd7-adc0-53e0f96e6635.log] 2020-07-03 11:44:55,538-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Ansible playbook command has exited with value: 2 2020-07-03 11:44:55,538-04 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Validation of action 'ExportVmToOva' failed for user Miguel.Garcia. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName hyp11.infra,$directory /mnt/shared2 2020-07-03 11:44:55,539-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Lock freed to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:45:17,391-04 INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [6d510f0c] Lock Acquired to object 'EngineLock:{exclusiveLocks='[f762fb4b-57c1-40d0-bf3f-be4c83f16f44=PROVIDER]', sharedLocks=''}' I had tried to addthe nfs partition as a Storage Domain data type but that didn't help either. The mount persmission is as follow: drwxr-xr-x. 3 vdsm kvm 50 Jul 3 11:47 /mnt/shared2 Any idea how can export this vm?

4 5

OVA export creates empty and unusable images
by thomas＠hoberg.net 10 Aug '20

10 Aug '20

I've tested this now in three distinct farms with CentOS7.8 and the latest oVirt 4.3 release: OVA export files only contain an XML header and then lots of zeros where the disk images should be. Where an 'ls -l <vmname>.ova' shows a file about the size of the disk, 'du -h <vmname>.ova' shows mere kilobytes, 'strings <vmname>.ova' dumps the XML and then nothing but repeating zeros until the end of the file. Exporting existing VMs from a CentOS/RHEL 7 farm and importing them after a rebuild on CentOS/RHEL 8 would seem like a safe migration strategy, except when OVA export isn't working. Please treat with priority!

4 17

oVirt Hyperconverged question
by Benedetto Vassallo 10 Aug '20

10 Aug '20

Hi all, I am planning to build a 3 nodes hyperconverged system with oVirt, but I have a question. After having the system up and running with 3 nodes (compute and storage), if I need some extra compute power can I add some other "compute" (with no storage) nodes as glusterfs clients to enhance the total compute power of the cluster and using the actual storage? Thank you and Best Regards. -- Benedetto Vassallo Responsabile U.O. Sviluppo e manutenzione dei sistemi Sistema Informativo di Ateneo Università degli studi di Palermo Phone: +3909123860056 Fax: +3909123860880

3 3

Deep dive - oVirt metrics with DWH and Grafana
by Sandro Bonazzola 10 Aug '20

10 Aug '20

The oVirt project is pleased to invite you to ShirlyRadco's deep dive session on oVirt metrics with DWH and Grafana in tomorrow, August 10th 2020, premiere on YouTube at https://www.youtube.com/watch?v=8_JMIlJJ8yc&feature=youtu.be Regards, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Thin Provisioned to Preallocated
by Jorge Visentini 10 Aug '20

10 Aug '20

Hi oVirt land. Can I convert the disks of Thin Provision to Preallocated? Best Regards. -- Att, Jorge Visentini +55 55 98432-9868

5 5

Do distinct export domains share a name space? Can't export a VM, because it already exists in an unattached export domain...
by thomas＠hoberg.net 10 Aug '20

10 Aug '20

After OVA export/import was a) recommended against b) not working with the current 4.3 on CentOS 7, I am trying to make sure I keep working copies of critical VMs before I test if the OVA export now works properly, with the Redhat fix from 4.4. applied to 4.3. Long story short, I have an export domain "export", primarily attached to a 3 node HCI gluster-cluster and another domain "exportMono", primarily attached to a single node HCI gluster-cluster. Yes I use an export domain for backup, because, ...well there is no easy and working alternative out of the box, or did I overlook something? But of course, I also use an export domain for shipping between farms, so evidently I swap export domains like good old PDP-11 disk cartridges.... or at least I'd like to. I started by exporting VM "tdc" from the 1nHCI to exportMono, reattached that to 3nHCI for am import. Import worked everything fine, transfer succeed. So I detach exportMono, which belongs to the 1nHCI cluster. Next I do the OVA export on 1nHCI, but I need to get the working and reconfigured VM "tdc" out of the way on 3nHCI, so I dump it into the "export" export domain belonging to 3nHCI, because I understand I can't run two copies of the same VM on a single cluster. Turns out I can' export it, because even if the export domain is now a different one and definitely doesn't contain "tdc" at all, oVirt complains that the volume ID that belongs to "tdc" already exists in the export domain.... So what's the theory here behind export domains? And what's the state of their support in oVirt 4.4? I understand that distinct farms can't share an export domain, because they have no way of coordinating properly. Of course I tried to use one single NFS mount for both farms but the second farm properly detected the presense of another and required a distinct path. But from the evidence before me, oVirt doesn't support or like the existance of more than one export domain, either: Something that deserves a note or explanation. I understand they are deprecated in 4.3 already, but since they are also the only way to manage valuable VM images moving around, that currently works with the GUI on oVirt 4.3 it would be nice to have these questions answered.

3 3

4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem
by Stephen Panicho 09 Aug '20

09 Aug '20

Hi all! I'm using Cockpit to perform an HCI install, and it fails at the hosted engine deploy. Libvirtd can't restart because of a missing /etc/pki/CA/cacert.pem file. The log (tasks seemingly from /usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/initial_clean.yml): [ INFO ] TASK [ovirt.hosted_engine_setup : Stop libvirt service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop vdsm config statements] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial abrt config files] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restart abrtd service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Stop and disable services] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial libvirt default network configuration] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Start libvirt] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service libvirtd: Job for libvirtd.service failed because the control process exited with error code.\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\n"} journalctl -u libvirtd: May 22 04:33:25 node1 libvirtd[26392]: libvirt version: 5.6.0, package: 10.el8 (CBS <cbs(a)centos.org>, 2020-02-27-01:09:46, ) May 22 04:33:25 node1 libvirtd[26392]: hostname: node1 May 22 04:33:25 node1 libvirtd[26392]: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory May 22 04:33:25 node1 systemd[1]: libvirtd.service: Main process exited, code=exited, status=6/NOTCONFIGURED May 22 04:33:25 node1 systemd[1]: libvirtd.service: Failed with result 'exit-code'. May 22 04:33:25 node1 systemd[1]: Failed to start Virtualization daemon. From a fresh CentOS 8.1 minimal install, I've installed the following: - The 4.4 repo - cockpit - ovirt-cockpit-dashboard - vdsm-gluster (providing glusterfs-server and allowing the Gluster Wizard to complete) - gluster-ansible-roles (only on the bootstrap host) I'm not exactly sure what that initial bit of the playbook does. Comparing the bootstrap node with another that has yet to be touched, both /etc/libvirt/libvirtd.conf and /etc/sysconfig/libvirtd are the same on both hosts. Yet the bootstrap host can no longer start libvirtd while the other host can. Neither host has the /etc/pki/CA/cacert.pem file. Please let me know if I can provide any more information. Thanks!

9 15

Why OVA imports failed (the other reason...)
by thomas＠hoberg.net 07 Aug '20

07 Aug '20

Empty disks from exports that went wrong didn't help. But that's fixed now, even if I can't fully validate the OVA exports on VMware and VirtualBox. The export/import target for the *.ova files is an SSD hosted xfs file system on a pure compute Xeon D oVirt node, exported and automounted to the 3nHCI cluster, also all SSD but J5005 Atoms. As I import the OVA file, I chose the Xeon-D as the import node and the *local path* on that host for the import. Cockpit checks the OVA file, detects the machine inside, lets me select and chose it for import, potentially overriding some parameters, lets me choose the target storage volume, sets up the job... and then fails, rather siliently and with very little in terms of error reporting ("connection closed") is the best I got. Now that same process worked just fine on a single node HCI cluster (also J5005 Atom), which had me a bit stunned at first, but gave a hint as to the cause: Parts of the input job, most likely an qemu-img job, isn't run via the machine you selected in the first step and unless the path is global (e.g. external NFS), it fails. If someone from the oVirt team could check and validate or disprove this theory, that could be documented and/or added as a check to avoid people falling into the same trap. While I was testing this using a global automount path, my cluster failed me (creating and deleting VMs a bit too quickly?) and I had to struggle for a while to have it recover. While those transient ailures are truly frightening, oVirt's ability to recover from these scenarios is quite simply awsome. I guess it's really mostly miscommunication and not real failures and oVirt has lots of logic to rectify that.

1 1

Has anyone ever had success importing an OVA VM exported from oVirt to VirtualBox or VMware? On Windows?
by thomas＠hoberg.net 07 Aug '20

07 Aug '20

After applying the OVA export patch, that ensured disk content was actually written ino the OVA image, I have been able to transfer *.ova VMs between two oVirt clusters. There are still problems that I will report once I have fully tested what's going on, but in the mean-time for all those, who want to be able to move VMs not only in the direction of oVirt (seems well tested), but also the other way (e.g. local desktop use, or even a vSphere farm) an OVA export could be a life saver--if it worked. I have tried importing oVirt exported VMs (which correctly imported and ran on a second oVirt host) both on VMware workstation 15.5.6 and VirtualBox 6.1.12 running on a Windows 2019 host without success. I've also tried untaring the *.ova into the component *.ovf + image file, but the issue seems to be with the XML description which has both imports fail pretty much instantly, before they even read the disk image file. From what I can tell, the XML created by qemu-img looks just fine, the error messages emitted by both products are very sparse and seem misleading. E.g. VirtualBox complains "Empty element ResourceType under Item element, line 1.", while I see all <Item> well constructed with a ResourceType in every one of them. VMware Workstation is completely useless in terms of log-file-diagnostics: It reports an invalid value for the "populatedSize" for the "Disk", but doesn't log that to the ovftool.log. I am pretty sure the error is in the inconsistent interpretation of this section, where the AllocationUnits, capacity and populatedSize leave some room for misinterpretation: -<DiskSection> <Info>List of Virtual Disks</Info> <Disk ovf:cinder_volume_type="" ovf:disk_storage_type="IMAGE" ovf:description="Auto-generated for Export To OVA" ovf:wipe-after-delete="false" ovf:disk-description="" ovf:disk-alias="oeight_Disk1" ovf:pass-discard="true" ovf:boot="true" ovf:disk-interface="VirtIO_SCSI" ovf:volume-type="Sparse" ovf:volume-format="RAW" ovf:format="http://www.vmware.com/specifications/vmdk.html#sparse" ovf:fileRef="974ad04f-d9bb-4881-aad2-c1d5404200ef" ovf:parentRef="" ovf:populatedSize="536953094144" ovf:capacityAllocationUnits="byte * 2^30" ovf:capacity="500" ovf:diskId="02b8d976-7e42-44e7-8e24-06f974f1c3ea"/> </DiskSection> I am trying to import the *.ova files on a Windows host and the sparsity get typically lost on the scp file transfer, too. Yes, this most likely isn't an oVirt bug, qemu-img is maintained elsewhere and the problem to me looks more on the receiver side. But have you tried it? Can you imagine it being important, too?

2 2

Re: PATCH method not allowed in imageio
by Nir Soffer 07 Aug '20

07 Aug '20

On Fri, Aug 7, 2020, 15:52 Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > Thank you for previous answers. I don't have problems with checkpoints > anymore. > > I am trying to send PATCH request to imageio but it seems like I don't > have write access. In the documentation I saw that it must be a RAW format. > I think I am missing something else. > > OPTIONS Request: > { > "features": [ > "extents" > ], > "max_readers": 8, > "max_writers": 8 > } > Allow: OPTIONS,GET > > PATCH Request: > *You are not allowed to access this resource: Ticket > 485493df-b07a-495c-8aa3-824aad45b4ab forbids write* > > I created transfer using java sdk: > ImageTransfer imageTransfer = > connection.getImageTransfersSvc().addForDisk().imageTransfer( > imageTransfer() > .direction(direction) > Is this a backup? You cannot write to disks during backup. .disk(disk) > .backup(backup) > .inactivityTimeout(120) > .format(DiskFormat.RAW)) > .send().imageTransfer(); > Can you explain what are you trying to do? > It's similar to python examples. > > Best Regards > > Łukasz Kołaciński > > Junior Java Developer > > e-mail: l.kolacinski(a)storware.eu > <m.helbert(a)storware.eu> > > > > > *[image: STORWARE]* <http://www.storware.eu/> > > > > *ul. Leszno 8/44 01-192 Warszawa www.storware.eu > <https://www.storware.eu/>* > > *[image: facebook]* <https://www.facebook.com/storware> > > *[image: twitter]* <https://twitter.com/storware> > > *[image: linkedin]* <https://www.linkedin.com/company/storware> > > *[image: Storware_Stopka_09]* > <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> > > > > *Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa > 000510131* *, NIP 5213672602.** Wiadomość ta jest przeznaczona jedynie > dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne > i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, > przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub > podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub > podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez > pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie > tej wiadomości z wszelkich komputerów. **This message is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you have received this message in error, please contact > the sender and remove the material from all of your computer systems.* > >

1 0

PATCH method not allowed in imageio
by Łukasz Kołaciński 07 Aug '20

07 Aug '20

Hello, Thank you for previous answers. I don't have problems with checkpoints anymore. I am trying to send PATCH request to imageio but it seems like I don't have write access. In the documentation I saw that it must be a RAW format. I think I am missing something else. OPTIONS Request: { "features": [ "extents" ], "max_readers": 8, "max_writers": 8 } Allow: OPTIONS,GET PATCH Request: You are not allowed to access this resource: Ticket 485493df-b07a-495c-8aa3-824aad45b4ab forbids write I created transfer using java sdk: ImageTransfer imageTransfer = connection.getImageTransfersSvc().addForDisk().imageTransfer( imageTransfer() .direction(direction) .disk(disk) .backup(backup) .inactivityTimeout(120) .format(DiskFormat.RAW)) .send().imageTransfer(); It's similar to python examples. Best Regards Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [Storware_Stopka_09]<https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.

1 0

Deploy host engine error: The task includes an option with an undefined variable
by Angel R. Gonzalez 07 Aug '20

07 Aug '20

Hi all! I'm deploying a host engine in a host node with a 8x Intel(R) Xeon(R) CPU E5410 @ 2.33GHz. The deploy proccess show the next message > [INFO]TASK [ovirt.hosted_engine_setup : Convert CPU model name] > [ERROR]fatal: [localhost]: FAILED! => {"msg": "The task includes an > option with an undefined variable. The error was: 'dict object' has no > attribute ''\n\nThe error appears to be in > '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': > line 105, column 15, but may\nbe elsewhere in the file depending on > the exact syntax problem.\n\nThe offending line appears to be:\n\n - > debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' > shorthand syntax and YAML in this task. Only one syntax may be used.\n"} The ansible deploy script in his 105 line show: > - name: Parse server CPU list > set_fact: > server_cpu_dict: "{{ server_cpu_dict | > combine({item.split(':')[1]: item.split(':')[3]}) }}" > with_items: >- > {{ > server_cpu_list.json['values']['system_option_value'][0]['value'].split('; > ')|list|difference(['']) }} > - debug: var=server_cpu_dict I don´t know ansible and i don't how to resolve this issue. Any idea? Thanks in advance, Ángel González.

4 4