- Users - oVirt List Archives

Failed to upload ISO oVirt 4.4.0 - imageio unable to verify certificate
by Erez Zarum 13 Jul '20

13 Jul '20

I have changed the Engine SSL certificate with our own certificates (using FreeIPA), i have followed the procedure described in the documents carefully and it is indeed working well. I haven now tried to upload an ISO and it fails, using "test connection" says the connection to the imageio service is ok, but when the upload starts it fails. I can see those errors in the ovirt-imageio daemon log file. 2020-07-10 06:00:48,386 ERROR (Thread-11) [http] Server error Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", line 699, in __call__ self.dispatch(req, resp) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", line 744, in dispatch return method(req, resp, *match.groups()) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/cors.py", line 84, in wrapper return func(self, req, resp, *args) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/images.py", line 66, in put backends.get(req, ticket, self.config), File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init__.py", line 53, in get cafile=config.tls.ca_file) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 48, in open secure=options.get("secure", True)) File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 63, in __init__ options = self._options() File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", line 364, in _options self._con.request("OPTIONS", self.url.path) File "/usr/lib64/python3.6/http/client.py", line 1254, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1300, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1249, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib64/python3.6/http/client.py", line 1036, in _send_output self.send(msg) File "/usr/lib64/python3.6/http/client.py", line 974, in send self.connect() File "/usr/lib64/python3.6/http/client.py", line 1422, in connect server_hostname=server_hostname) File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket _context=self, _session=session) File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ self.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake self._sslobj.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897) Looking at old posts here, i have also tried: keytool -importcert -trustcacerts -keystore /etc/pki/ovirt-engine/.truststore -storepass mypass -file /etc/pki/ovirt-engine/apache-ca.pem And restarted both the ovirt-imageio service and the ovirt-engine service, it didn't help.

3 5

Re: Using ovirt imageio
by Nir Soffer 13 Jul '20

13 Jul '20

On Tue, Jul 7, 2020 at 5:05 PM Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Dear ovirt community, > Hi Łukasz, Adding devel(a)ovit.org since this topic is more appropriate for the devel list. > I am trying to use ovirt imageio api to receive changed blocks (dirty > bitmap) on ovirt 4.4. Could anyone tell me how to get them step by step? On > the documentation I saw endpoint "GET /images/ticket-uuid/map". I don't > know what ticket-uuid is and how to generate it. I also need to know how to > use this api because I can't reach it via /ovirt-engine/api/ > > I am asking about this endpoint: > > https://www.ovirt.org/documentation/incremental-backup-guide/incremental-ba… > This guide is outdated and should not be used now. The most up to date information is here: https://www.ovirt.org/develop/release-management/features/storage/increment… However the extents API is also outdated in the feature page. We are working on updating it. So here is example: First you must start backup with from_checkpoint_id argument: backup = backups_service.add( types.Backup( disks=disks, from_checkpoint_id="checkpoint-id", ) ) > "checkpoint-id" is the checkpoint created in the last backup. This starts a backup in in incremental mode. Dirty extents are available only in this mode. Then you start a transfer for download, using the backup id: transfer = imagetransfer.create_transfer( connection, disk, types.ImageTransferDirection.DOWNLOAD, backup=types.Backup(id=backup_uuid)) The transfer.transfer_url is the URL to download from, for example: https://host:54322/images/53787351-3f72-44a1-8a26-1323524fac4a Connect to host:54322 and send this request: GET /images/53787351-3f72-44a1-8a26-1323524fac4a/extents?context=dirty And parse the return json list, containing objects like: [ {"start": 0, "length": 65536, "dirty": true}, {"start": 65536, "length": 1048576, "dirty": false}, ... ] For example code of using the imageio API, see imageio http backend: https://github.com/oVirt/ovirt-imageio/blob/d5aa0e1fe659f1bf1247516f83c71e0… https://github.com/oVirt/ovirt-imageio/blob/d5aa0e1fe659f1bf1247516f83c71e0… We are adding a ImageioClient API that makes it easier to consume without writing any HTTP code: https://gerrit.ovirt.org/c/110068 With this you can use: with ImageioClient(transfer.transfer_url, cafile=args.cafile) as client: for extent in client.extent("dirty"): if extent.dirty: print("##dirty start={} length={}".format(extent.start, extent.length)) client.write_to(sys.stdout.buffer, extent.start, extent.length) print() This will stream the dirty extents to stdout. Not very useful as is, but illustrates how you can consume the data. Here is an example writing extents to a sparse stream format: https://gerrit.ovirt.org/c/110069 For complete backup example code see: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/backup_v… Note the new imagetransfer helper module: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/helpers/… Nir 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.* > > _______________________________________________ > 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/AIJMMJOR354VK… >

3 4

[ANN] Updated oVirt release 4.4.1.1
by Lev Veyde 13 Jul '20

13 Jul '20

The oVirt Team has just released a new version of ovirt-ansible-engine-setup (1.1.6) package that fixes oVirt Hyperconverged deployment related issue.[1] Updated ovirt-node-ng-installer and ovirt-appliance have been built. Also a new torrent for this new ovirt-node-ng-installer ISO is now available. https://bugzilla.redhat.com/show_bug.cgi?id=1855164 -- 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

Lots of problems with deploying the hosted-engine (ovirt 4.4 | CentOS 8.2.2004)
by jonas 13 Jul '20

13 Jul '20

Hi! I have banged my head against deploying the ovirt 4.4 self-hosted engine on Centos 8.2 for last couple of days. First I was astonished that resources.ovirt.org has no IPv6 connectivity, which made my initial plan for a mostly IPv6-only deployment impossible. CentOS was installed from scratch using the ks.cgf Kickstart file below, which also adds the ovirt 4.4 repo and installs cockpit-ovirt-dashboard & ovirt-engine-appliance. When deploying the hosted-engine from cockpit while logged in as a non-root (although privileged) user, the "(3) Prepare VM" step instantly fails with a nondescript error message and without generating any logs. By using the browser dev tools it was determined that this was because the ansible vars file could not be created as the non-root user did not have write permissions in '/var/lib/ovirt-hosted-engine-setup/cockpit/' . Shouldn't cockpit be capable of using sudo when appropriate, or at least give a more descriptive error message? After login into cockpit as root, or when using the command line ovirt-hosted-engine-setup tool, the deployment fails with "Failed to download metadata for repo 'AppStream'". This seems to be because a) the dnsmasq running on the host does not forward dns queries, even though the host itself can resolve dns queries just fine, and b) there also does not seem to be any functioning routing setup to reach anything outside the host. Regarding a) it is strange that dnsmasq is running with a config file '/var/lib/libvirt/dnsmasq/default.conf' containing the 'no-resolv' option. Could the operation of systemd-resolved be interfering with dnsmasq (see ss -tulpen output)? I tried to manually stop systemd-resolved, but got the same behaviour as before. I hope someone could give me a hint how I could get past this problem, as so far my ovirt experience has been a little bit sub-par. :D Also when running ovirt-hosted-engine-cleanup, the extracted engine VMs in /var/tmp/localvm* are not removed, leading to a "disk-memory-leak" with subsequent runs. Best regards Jonas --- ss -tulpen output post deploy-run --- [root@nxtvirt ~]# ss -tulpen | grep ':53 ' udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=1379,fd=18)) uid:193 ino:32910 sk:6 <-> udp UNCONN 0 0 [fd00:1234:5678:900::1]:53 [::]:* users:(("dnsmasq",pid=13525,fd=15)) uid:979 ino:113580 sk:d v6only:1 <-> udp UNCONN 0 0 [fe80::5054:ff:fe94:f314]%virbr0:53 [::]:* users:(("dnsmasq",pid=13525,fd=12)) uid:979 ino:113575 sk:e v6only:1 <-> tcp LISTEN 0 32 [fd00:1234:5678:900::1]:53 [::]:* users:(("dnsmasq",pid=13525,fd=16)) uid:979 ino:113581 sk:20 v6only:1 <-> tcp LISTEN 0 32 [fe80::5054:ff:fe94:f314]%virbr0:53 [::]:* users:(("dnsmasq",pid=13525,fd=13)) uid:979 ino:113576 sk:21 v6only:1 <-> --- running dnsmasq processes on host ('nxtvirt') post deploy-run --- dnsmasq 13525 0.0 0.0 71888 2344 ? S 12:31 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 13526 0.0 0.0 71860 436 ? S 12:31 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper --- var/lib/libvirt/dnsmasq/default.conf --- ##WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE ##OVERWRITTEN AND LOST. Changes to this configuration should be made using: ## virsh net-edit default ## or other application using the libvirt API. ## ## dnsmasq conf file created by libvirt strict-order pid-file=/run/libvirt/network/default.pid except-interface=lo bind-dynamic interface=virbr0 dhcp-option=3 no-resolv ra-param=*,0,0 dhcp-range=fd00:1234:5678:900::10,fd00:1234:5678:900::ff,64 dhcp-lease-max=240 dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts enable-ra --- cockpit wizard overview before the 'Prepare VM' step --- VM Engine FQDN:engine.*REDACTED* MAC Address:00:16:3e:20:13:b3 Network Configuration:Static VM IP Address:*REDACTED*:1099:babe::3/64 Gateway Address:*REDACTED*:1099::1 DNS Servers:*REDACTED*:1052::11 Root User SSH Access:yes Number of Virtual CPUs:4 Memory Size (MiB):4096 Root User SSH Public Key:(None) Add Lines to /etc/hosts:yes Bridge Name:ovirtmgmt Apply OpenSCAP profile:no Engine SMTP Server Name:localhost SMTP Server Port Number:25 Sender E-Mail Address:root@localhost Recipient E-Mail Addresses:root@localhost --- ks.cgf --- #version=RHEL8 ignoredisk --only-use=vda autopart --type=lvm # Partition clearing information clearpart --drives=vda --all --initlabel # Use graphical install #graphical text # Use CDROM installation media cdrom # Keyboard layouts keyboard --vckeymap=de --xlayouts='de','us' # System language lang en_US.UTF-8 # Network information network --bootproto=static --device=enp1s0 --ip=192.168.199.250 --netmask=255.255.255.0 --gateway=192.168.199.10 --ipv6=*REDACTED*:1090:babe::250/64 --ipv6gateway=*REDACTED*:1090::1 --hostname=nxtvirt.*REDACTED* --nameserver=*REDACTED*:1052::11 --activate network --hostname=nxtvirt.*REDACTED* # Root password rootpw --iscrypted $6$*REDACTED* firewall --enabled --service=cockpit --service=ssh # Run the Setup Agent on first boot firstboot --enable # Do not configure the X Window System skipx # System services services --enabled="chronyd" # System timezone timezone Etc/UTC --isUtc --ntpservers=ntp.*REDACTED*,ntp2.*REDACTED* user --name=nonrootuser --groups=wheel --password=$6$*REDACTED* --iscrypted # KVM Users/Groups group --name=kvm --gid=36 user --name=vdsm --uid=36 --gid=36 %packages @^server-product-environment #@graphical-admin-tools @headless-management kexec-tools cockpit %end %addon com_redhat_kdump --enable --reserve-mb='auto' %end %anaconda pwpolicy root --minlen=6 --minquality=1 --notstrict --nochanges --notempty pwpolicy user --minlen=6 --minquality=1 --notstrict --nochanges --emptyok pwpolicy luks --minlen=6 --minquality=1 --notstrict --nochanges --notempty %end %post --erroronfail --log=/root/ks-post.log #!/bin/sh dnf update -y # NFS storage mkdir -p /opt/ovirt/nfs-storage chown -R 36:36 /opt/ovirt/nfs-storage chmod 0755 /opt/ovirt/nfs-storage echo "/opt/ovirt/nfs-storage localhost" > /etc/exports echo "/opt/ovirt/nfs-storage engine.*REDACTED*" >> /etc/exports dnf install -y nfs-utils systemctl enable nfs-server.service # Install ovirt packages dnf install -y https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm dnf install -y cockpit-ovirt-dashboard ovirt-engine-appliance # Enable cockpit systemctl enable cockpit.socket %end #reboot --eject --kexec reboot --eject --- Host (nxtvirt) ip -a post deploy-run --- 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:ad:79:1b brd ff:ff:ff:ff:ff:ff inet 192.168.199.250/24 brd 192.168.199.255 scope global noprefixroute enp1s0 valid_lft forever preferred_lft forever inet6 *REDACTED*:1099:babe::250/64 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fead:791b/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:94:f3:14 brd ff:ff:ff:ff:ff:ff inet6 fd00:1234:5678:900::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe94:f314/64 scope link valid_lft forever preferred_lft forever 6: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:94:f3:14 brd ff:ff:ff:ff:ff:ff 7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master virbr0 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:68:d3:8a brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe68:d38a/64 scope link valid_lft forever preferred_lft forever --- iptables-save post deploy-run --- # Generated by iptables-save v1.8.4 on Sun Jun 28 13:20:53 2020 *filter :INPUT ACCEPT [4007:8578553] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [3920:7633249] :LIBVIRT_INP - [0:0] :LIBVIRT_OUT - [0:0] :LIBVIRT_FWO - [0:0] :LIBVIRT_FWI - [0:0] :LIBVIRT_FWX - [0:0] -A INPUT -j LIBVIRT_INP -A FORWARD -j LIBVIRT_FWX -A FORWARD -j LIBVIRT_FWI -A FORWARD -j LIBVIRT_FWO -A OUTPUT -j LIBVIRT_OUT -A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 53 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 67 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 53 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 68 -j ACCEPT -A LIBVIRT_FWO -i virbr0 -j REJECT --reject-with icmp-port-unreachable -A LIBVIRT_FWI -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A LIBVIRT_FWX -i virbr0 -o virbr0 -j ACCEPT COMMIT # Completed on Sun Jun 28 13:20:53 2020 # Generated by iptables-save v1.8.4 on Sun Jun 28 13:20:53 2020 *security :INPUT ACCEPT [3959:8576054] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [3920:7633249] COMMIT # Completed on Sun Jun 28 13:20:53 2020 # Generated by iptables-save v1.8.4 on Sun Jun 28 13:20:53 2020 *raw :PREROUTING ACCEPT [4299:8608260] :OUTPUT ACCEPT [3920:7633249] COMMIT # Completed on Sun Jun 28 13:20:53 2020 # Generated by iptables-save v1.8.4 on Sun Jun 28 13:20:53 2020 *mangle :PREROUTING ACCEPT [4299:8608260] :INPUT ACCEPT [4007:8578553] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [3920:7633249] :POSTROUTING ACCEPT [3923:7633408] :LIBVIRT_PRT - [0:0] -A POSTROUTING -j LIBVIRT_PRT COMMIT # Completed on Sun Jun 28 13:20:53 2020 # Generated by iptables-save v1.8.4 on Sun Jun 28 13:20:53 2020 *nat :PREROUTING ACCEPT [337:32047] :INPUT ACCEPT [0:0] :POSTROUTING ACCEPT [159:9351] :OUTPUT ACCEPT [159:9351] :LIBVIRT_PRT - [0:0] -A POSTROUTING -j LIBVIRT_PRT COMMIT # Completed on Sun Jun 28 13:20:53 2020

5 6

Error: missing groups or modules: javapackages-tools in EL 8.2
by Patrick Lomakin 13 Jul '20

13 Jul '20

I'm take an error after executing "dnf module enable -y javapackages-tools pki-deps postgresql:12 389-ds". Error message: "Error: Problems in request: missing groups or modules: javapackages-tools" Installed system - Red Hat Enterprise Linux 8.2

2 1

ovirt terraform - multiple nics creation problem
by marek 13 Jul '20

13 Jul '20

i have problem with creation VM with multiple nics part of terraform config resource "ovirt_vm" "vm" { .... initialization { authorized_ssh_key = "${var.vm_authorized_ssh_key}" host_name = "${var.vm_hostname}" timezone = "${var.vm_timezone}" user_name = "${var.vm_user_name}" custom_script = "${var.vm_custom_script}" dns_search = "${var.vm_dns_search}" dns_servers = "${var.vm_dns_servers}" nic_configuration { label = "eth0" boot_proto = "${var.vm_nic_boot_proto}" address = "${var.vm_nic_ip_address}" gateway = "${var.vm_nic_gateway}" netmask = "${var.vm_nic_netmask}" on_boot = "${var.vm_nic_on_boot}" } nic_configuration { label = "eth1" boot_proto = "${var.vm_nic2_boot_proto}" address = "${var.vm_nic2_ip_address}" gateway = "${var.vm_nic2_gateway}" netmask = "${var.vm_nic2_netmask}" on_boot = "${var.vm_nic2_on_boot}" } } } resource "ovirt_vnic" "eth0" { name = "eth0" vm_id = "${ovirt_vm.vm.id}" vnic_profile_id = "${data.ovirt_vnic_profiles.nic1.vnic_profiles.0.id}" } resource "ovirt_vnic" "eth1" { name = "eth1" vm_id = "${ovirt_vm.vm.id}" vnic_profile_id = "${data.ovirt_vnic_profiles.nic2.vnic_profiles.0.id}" } how terraform knows which nic_configuration {} from ovirt_vm belongs to which resource "ovirt_vnic"? my problem is that VM has paired nic_configuration(eth0) with resource "ovirt_vnic" "eth1" and vice versa any hints? https://github.com/oVirt/terraform-provider-ovirt/blob/master/ovirt/resourc… my experience with Go is not enough to understand how is "pairing" done Marek

1 0

Re: Ovirt 4.4.1 Install failure at OVF_Store check
by Andy 13 Jul '20

13 Jul '20

Attached are the install logs thanks Andy

1 0

Revert to 4.3
by jb 13 Jul '20

13 Jul '20

Hello everybody, at to moment I run ovirt engine in a VM on a different server (no hosted engine) and I have two hosts. One is only a backup and is not running. I would like to install a new ovirt engine 4.4 VM and use the backup host. And if this is running fine in some month I would migrate the second host to 4.4. The Problem is only that I have to upgrade the data center compatibly mode to 4.4 and with that I'm a bit afraid. Is it possible, to downgrade the compatibility mode, when something unsuspected is happen? The original 4.3 engine VM I would like to have untouched, that I can go back if is necessary. Regards Jonathan

1 0

Not able to asign IB network to IB Bond
by Andrey Rusakov 12 Jul '20

12 Jul '20

Hi all, We are using oBirt since 4.2. Config is 1Gb or 10G for VM ext network and 40Gb IB for Starage and VM Migration. We are testing 4.4 and 4.4.0 at the moment. 2 problems - Major problem is that i can't assign IB netwrok to IB bond i got - "Error while executing action HostSetupNetworks: Unexpected exception" VDSM.log 2020-07-11 15:33:39,147+0300 INFO (jsonrpc/1) [api.network] START setupNetworks(networks={'IB': {'netmask': '255.255.255.0', 'bonding': 'bond1', 'ipv6autoconf': False, 'bridged': 'false', 'ipaddr': '172.17.21.101', 'dhcpv6': False, 'mtu': 65520, 'switch': 'legacy'}}, bondings={}, options={'connectivityTimeout': 120, 'commitOnSuccess': True, 'connectivityCheck': 'true'}) from=::ffff:172.16.21.201,33614, flow_id=fe589281-3171-41b4-b7aa-e28a4bbebe55 (api:48) 2020-07-11 15:33:40,088+0300 INFO (jsonrpc/1) [api.network] FINISH setupNetworks error=MAC address cannot be specified in bond interface along with specified bond options from=::ffff:172.16.21.201,33614, flow_id=fe589281-3171-41b4-b7aa-e28a4bbebe55 (api:52) 2020-07-11 15:33:40,088+0300 ERROR (jsonrpc/1) [jsonrpc.JsonRpcServer] Internal server error (__init__:350) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File "/usr/lib/python3.6/site-packages/vdsm/rpc/Bridge.py", line 198, in _dynamicMethod result = fn(*methodArgs) File "<decorator-gen-480>", line 2, in setupNetworks File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 1548, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in _callmethod raise convert_to_error(kind, result) libnmstate.error.NmstateValueError: MAC address cannot be specified in bond interface along with specified bond options 2nd problem - IB bond not working after reboot - theres is no bond1 insterface at all (my solution is to restart network) This is not very important as VDSM will change config after Adding bond to oVirt. P.S. I Got 100% same config with same cards and samу bond config on 4.3 - everething is wotking fine.

1 0

Metrics in Kibana not working
by Guillaume Pavese 12 Jul '20

12 Jul '20

Trying to use the provided visualizations/Dashboards for ovirt metrics in Kibana. Using ovirt 4.3.7, with ovirt-engine-metrics 1.3.7-1 and latest rsylog-8.24.0-52 and collectd-5.10.0-2 I am receiving data in indexes and some fields are present. A few graph work, but most don't and I am getting a lot of errors like theses : Error in visualisation[esaggs] > "field" is a required parameter - On my hosts I can see the following collectd errors: systemd[1]: Starting Collectd statistics daemon... collectd[21629]: plugin_load: plugin "disk" successfully loaded. ... collectd[21629]: plugin_load: plugin "network" successfully loaded. collectd[21629]: Systemd detected, trying to signal readiness. systemd[1]: Started Collectd statistics daemon. collectd[21629]: virt plugin: reader virt-0 initialized collectd[21629]: Initialization complete, entering read-loop. collectd[21629]: write_syslog plugin: send failed with status -1 (Connection reset by peer) collectd[21629]: write_syslog plugin: error with ws_send_message - And the following rsyslog ones : systemd[1]: Starting System Logging Service... rsyslogd[210059]: [origin software="rsyslogd" swVersion="8.24.0-52.el7_8.2" x-pid="210059" x-info="http://www.rsyslog.com"] start systemd[1]: Started System Logging Service. rsyslogd[210059]: command 'SystemLogSocketName' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.24.0-52.el7_8.2 try http://www.rsyslog.com/e/2222 ] I think that this is this bug : https://bugzilla.redhat.com/show_bug.cgi?id=1732918 However it's CLOSED INSUFFICIENT_DATA with last message being "Closing with insufficient data. Please reopen if you can provide needed info." Is my understanding correct that only RedHat employees can reopen closed bugs? I have encountered quite a lot of situations where I'm facing an issue covered by such a closed bug with a "please reopen if you can provide info" msg, but frustratingly not being able to do so... Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

2 1

Is there a way to access VM data that is stored using iscsi block storage outside of the ovirt platform ?
by Kevin Doyle 10 Jul '20

10 Jul '20

We have had problems trying to get our broken hosted engine to work. The datastore for all the VM's was stored in an iscsi storage that was deactivated before the platform went down, I am now looking for a way to access this data and start the VM's outside of a running hosted-engine Can I build an new ovirt standalone engine on a new bare metal remote server and connect to the hosts and start up the domain ? I would be interested in your thoughts. The problem with rebuilding the hosted-engine is that it cannot reuse the lun dedicated for the hosted-engine. I have tried to rebuild using NFS but it complains about not seeing the master domain thanks Kevin

3 3

Weird problem starting VMs in oVirt-4.4
by Joop 10 Jul '20

10 Jul '20

Hi All, Just had a rather new experience in that starting a VM worked but the kernel entered grub2 rescue console due to the fact that something was wrong with its virtio-scsi disk. The message is Booting from Hard Disk .... error: ../../grub-core/kern/dl.c:266:invalid arch-independent ELF maginc. entering rescue mode... Doing a CTRL-ALT-Del through the spice console let the VM boot correctly. Shutting it down and repeating the procedure I get a disk problem everytime. Weird thing is if I activate the BootMenu and then straight away start the VM all is OK. I don't see any ERROR messages in either vdsm.log, engine.log If I would have to guess it looks like the disk image isn't connected yet when the VM boots but thats weird isn't it? Regards, Joop

10 22

Recreate OVF_STORE
by Николай Чаплинский 10 Jul '20

10 Jul '20

After some troubles with gluster store i was found missing ovf_store file. I recreated file with dd, but now i get errors in agent.log. What the right way for recreate OVF_STORE file? oVirt 4.3. agent.log: MainThread::ERROR::2020-07-10 11:34:19,866::agent::145::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Trying to restart agent MainThread::INFO::2020-07-10 11:34:19,866::agent::89::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down MainThread::INFO::2020-07-10 11:34:30,243::agent::67::ovirt_hosted_engine_ha.agent.agent.Agent::(run) ovirt-hosted-engine-ha agent 2.3.6 started MainThread::INFO::2020-07-10 11:34:30,305::hosted_engine::234::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname) Found certificate common name: sponode1.vdispo.ru MainThread::INFO::2020-07-10 11:34:30,421::hosted_engine::543::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Initializing ha-bro ker connection MainThread::INFO::2020-07-10 11:34:30,423::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor network, options { 'tcp_t_address': '', 'network_test': 'dns', 'tcp_t_port': '', 'addr': '10.1.99.1'} MainThread::INFO::2020-07-10 11:34:30,427::brokerlink::92::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id network MainThread::INFO::2020-07-10 11:34:30,427::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor mgmt-bridge, optio ns {'use_ssl': 'true', 'bridge_name': 'ovirtmgmt', 'address': '0'} MainThread::INFO::2020-07-10 11:34:30,432::brokerlink::92::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id mgmt-bridge MainThread::INFO::2020-07-10 11:34:30,432::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor mem-free, options {'use_ssl': 'true', 'address': '0'} MainThread::INFO::2020-07-10 11:34:30,434::brokerlink::92::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id mem-free MainThread::INFO::2020-07-10 11:34:30,434::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor cpu-load-no-engine , options {'use_ssl': 'true', 'vm_uuid': '141397e0-050a-4e6a-9fe7-9042184ca2a8', 'address': '0'} MainThread::INFO::2020-07-10 11:34:30,437::brokerlink::92::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id cpu-load-no-engine MainThread::INFO::2020-07-10 11:34:30,437::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor engine-health, opt ions {'use_ssl': 'true', 'vm_uuid': '141397e0-050a-4e6a-9fe7-9042184ca2a8', 'address': '0'} MainThread::INFO::2020-07-10 11:34:30,439::brokerlink::92::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id engine-health MainThread::INFO::2020-07-10 11:34:30,440::brokerlink::80::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor storage-domain, op tions {'sd_uuid': '927801cc-f7fc-40bb-9bb9-92b2b19a5087'} MainThread::INFO::2020-07-10 11:34:30,441::brokerlink::92::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Success, id storage-domain MainThread::INFO::2020-07-10 11:34:30,441::hosted_engine::565::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Broker initialized, all submonitors started MainThread::INFO::2020-07-10 11:34:30,700::upgrade::979::ovirt_hosted_engine_ha.lib.upgrade.StorageServer::(upgrade_35_36) Host configuration is already up-to-d ate MainThread::INFO::2020-07-10 11:34:30,799::ovf_store::120::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) Found OVF_STORE: imgUUID:7a6cb900-03f2-4f3f -915c-633482b2f28c, volUUID:1beb6ac5-b55c-44dc-8d71-7ea9e85c2909 MainThread::INFO::2020-07-10 11:34:31,353::ovf_store::120::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) Found OVF_STORE: imgUUID:7ae16997-0b97-4c1f -a06b-1a57dcec7445, volUUID:ad3561e2-ae47-41e9-9e5b-c903f2391e67 MainThread::INFO::2020-07-10 11:34:31,844::ovf_store::151::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF) OVF_STORE volume path: /var/run/v dsm/storage/927801cc-f7fc-40bb-9bb9-92b2b19a5087/7ae16997-0b97-4c1f-a06b-1a57dcec7445/ad3561e2-ae47-41e9-9e5b-c903f2391e67 MainThread::ERROR::2020-07-10 11:34:31,861::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid globa l metadata key: CAP=1073741824 MainThread::ERROR::2020-07-10 11:34:31,861::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid globa l metadata key: CTIME=1590138019 MainThread::ERROR::2020-07-10 11:34:31,861::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid globa l metadata key: DESCRIPTION={"DiskAlias":"he_metadata","DiskDescription":"Hosted-Engine metadata disk"} MainThread::ERROR::2020-07-10 11:34:31,861::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid globa l metadata key: DISKTYPE=HEMD MainThread::ERROR::2020-07-10 11:34:31,861::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid globa l metadata key: DOMAIN=927801cc-f7fc-40bb-9bb9-92b2b19a5087 MainThread::ERROR::2020-07-10 11:34:31,861::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid globa l metadata key: FORMAT=RAW MainThread::ERROR::2020-07-10 11:34:31,861::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid globa l metadata key: GEN=0 MainThread::ERROR::2020-07-10 11:34:31,862::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid global metadata key: IMAGE=cdd8e110-ccae-4ff2-9215-18e04227e839 MainThread::ERROR::2020-07-10 11:34:31,862::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid global metadata key: LEGALITY=LEGAL MainThread::ERROR::2020-07-10 11:34:31,862::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid global metadata key: PUUID=00000000-0000-0000-0000-000000000000 MainThread::ERROR::2020-07-10 11:34:31,862::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid global metadata key: TYPE=PREALLOCATED MainThread::ERROR::2020-07-10 11:34:31,862::metadata::67::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(parse_global_metadata_to_dict) Invalid global metadata key: VOLTYPE=LEAF MainThread::ERROR::2020-07-10 11:34:31,862::hosted_engine::452::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Unhandled monitoring loop exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 449, in start_monitoring self._monitoring_loop() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 468, in _monitoring_loop for old_state, state, delay in self.fsm: File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/fsm/machine.py", line 127, in next new_data = self.refresh(self._state.data) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/state_machine.py", line 81, in refresh stats.update(self.hosted_engine.collect_stats()) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 760, in collect_stats data["cluster"] = self.process_global_metadata(all_stats.pop(0)) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 830, in process_global_metadata md = metadata.parse_global_metadata_to_dict(self._log, data) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/metadata.py", line 63, in parse_global_metadata_to_dict k, v = token.split('=') ValueError: need more than 1 value to unpack MainThread::ERROR::2020-07-10 11:34:31,864::agent::144::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent return action(he) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper return he.start_monitoring() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 456, in start_monitoring self.publish(stopped) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 355, in publish blocks = self._generate_local_blocks(state) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 652, in _generate_local_blocks lm = state.data.stats.local AttributeError: 'NoneType' object has no attribute 'local' MainThread::ERROR::2020-07-10 11:34:31,864::agent::145::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Trying to restart agent MainThread::INFO::2020-07-10 11:34:31,864::agent::89::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down virt OS Version: RHEL - 7 - 7.1908.0.el7.centos OS Description: CentOS Linux 7 (Core) Kernel Version: 3.10.0 - 1127.8.2.el7.x86_64 KVM Version: 2.12.0 - 44.1.el7_8.1 LIBVIRT Version: libvirt-4.5.0-33.el7_8.1 VDSM Version: vdsm-4.30.46-1.el7 SPICE Version: 0.14.0 - 9.el7 GlusterFS Version: glusterfs-7.5-1.el7 CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.11.0-4.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Disabled

1 0

Call for presentation for oVirt 2020 conference still open
by Sandro Bonazzola 09 Jul '20

09 Jul '20

Just a reminder call for presentation for the oVirt 2020 online conference is still open! Looking forward also for user stories and integrations with oVirt! Read more at https://blogs.ovirt.org/ovirt-2020-online-conference/ I would be happy to hear about how oVirt helped your organization or which amazing integrated datacenter you realized with oVirt and other projects in the ecosystem. -- 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

Problem with backuping ovirt 4.4 with SDK
by Łukasz Kołaciński 09 Jul '20

09 Jul '20

Hello, I am trying to do full backup on ovirt 4.4 using sdk. I used steps from this youtube video: https://www.youtube.com/watch?v=E2VWUVcycj4 and I got error after running backup_vm.py. I see that sdk has imported disks and created backup entity and then I got sdk.NotFoundError exception. I also tried to do full backup with API and after finalizing backup disappeared (I think) and I couldn't try incremental. [ 0.0 ] Starting full backup for VM '51708c8e-6671-480b-b2d8-199a1af9cbdc' Password: [ 4.2 ] Waiting until backup 0458bf7f-868c-4859-9fa7-767b3ec62b52 is ready Traceback (most recent call last): File "./backup_vm.py", line 343, in start_backup backup = backup_service.get() File "/usr/lib64/python3.7/site-packages/ovirtsdk4/services.py", line 32333, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python3.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python3.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python3.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/usr/lib64/python3.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault body = self._internal_read_body(response) File "/usr/lib64/python3.7/site-packages/ovirtsdk4/service.py", line 312, in _internal_read_body self._raise_error(response) File "/usr/lib64/python3.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error ovirtsdk4.NotFoundError: HTTP response code is 404. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./backup_vm.py", line 476, in <module> main() File "./backup_vm.py", line 173, in main args.command(args) File "./backup_vm.py", line 230, in cmd_start backup = start_backup(connection, args) File "./backup_vm.py", line 345, in start_backup raise RuntimeError("Backup {} failed".format(backup.id)) RuntimeError: Backup 0458bf7f-868c-4859-9fa7-767b3ec62b52 failed P.S Thank you for previous answers :) 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

oVirt 4.3 -> 4.4 Upgrade Path Questions
by Andrei Verovski 08 Jul '20

08 Jul '20

Hi ! I have 2-node oVirt 4.3 installation, with engine running as KVM guest on SuSE file server (not hosted engine). Nodes are manually installed on CentOS 7.x (further referred as old node #1 and #2). I’m going to add 1 additional node, and migrate system to CentOS 8.2 / oVirt 4.4. Is this correct roadmap, or something can be done in a better way? Here is my plan. 1) Upgrade oVirt Hosted Engine running under KVM / SuSE file server to CentOS 8.2 / oVirt 4.4. Or its better to install from scratch new CentOS 8.2/oVirt 4.4 and migrate database? 2) Install CentOS 8.2 and oVirt node 4.4 on new server (let’s name it node #3). 3) Migrate virtual machines from old node #1 to the new (#3). 4) Upgrade CentOS on old node #1 to v8.2, and oVirt from web interface. Will that work, or upgrade CentOS 7 -> 8 will render this process unmanageable due to removal of many components? 5) Migrate back virtual machines from node #3 to newly upgraded node #1. 6) Repeat step 4 and 5 for old node #2. I have set of custom shell and python scripts running on engine and nodes, so manual installation was a way to go. Thanks in advance for any suggestion(s) with best regards Andrei

4 4

[ANN] oVirt 4.4.1 is now generally available
by Lev Veyde 08 Jul '20

08 Jul '20

oVirt 4.4.1 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.1 , as of July 8th, 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 Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers 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, the 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 the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.1 Release? This update is the first in a series of stabilization updates to the 4.4 series. This release introduces a new monitoring solution that provides a user interface to oVirt DWH collected data using Grafana. This allows admins to track inventory, monitor performance and capacity trends, and easily identify and troubleshoot resources issues. Grafana is installed and configured during engine-setup and includes pre-built dashboards that are based on the data collected by the ovirt_engine_history PostgreSQL Data Warehouse database (BZ#1777877 <https://bugzilla.redhat.com/show_bug.cgi?id=1777877>). In oVirt 4.4.1 the maximum memory size for 64-bit x86_64 and ppc64/ppc64le VMs is now 6TB. For x86_64 this limit is applied also to VMs in 4.2 and 4.3 Cluster Levels. You can now use CentOS Stream as an alternative to CentOS Linux on non-production systems. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) - oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) oVirt Node and Appliance have been updated, including: - oVirt 4.4.1: http://www.ovirt.org/release/4.4.1/ - CentOS Linux 8.2.2004: https://lists.centos.org/pipermail/centos-announce/2020-June/035756.html - CentOS Virt SIG updates including Advanced Virtualization 8.2 (qemu-kvm 4.2 <https://www.qemu.org/2019/12/13/qemu-4-2-0/>, libvirt 6.0.0 <https://libvirt.org/news.html#v6-0-0-2020-01-15>) - Wildfly 19.1.0: https://wildfly.org/news/2020/05/04/WildFly-1910-Released/ - Ansible 2.9.10: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.6: https://docs.gluster.org/en/latest/release-notes/7.6/ 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.1 release highlights: http://www.ovirt.org/release/4.4.1/ - 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.1/ [2] http://resources.ovirt.org/pub/ovirt-4.4/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

rhv 4.3.9 - snapshots fail
by Markus Schaufler 08 Jul '20

08 Jul '20

Hi, I think we ran into this bug https://bugzilla.redhat.com/show_bug.cgi?id=1802277 and https://access.redhat.com/solutions/5174961 as we have exactly that problems and log-entries. As there are now several VMs that cannot create (or delete) snapshots accordingly we cannot do backups on that VMs. Are there any suggestions or workarounds in order that we can still backup them up? Thanks very much, Markus

2 1

Hosted engine can't start after changing cluster settings
by Patrick Lomakin 08 Jul '20

08 Jul '20

I changed the BIOS Type settings in the cluster settings section to UEFI BIOS, and hosted-engine does not start after rebooting. Although, before I made the changes, I looked in the engine at the /boot partition, which has the /efi directory. Is there any way to change the engine settings manually, and how can I connect to it (or to its partitions) to perform actions? I can't imagine how you can reinstall the engine without unplugging storage to import all virtual machines later. Losing data in virtual machines is a disaster for me.

2 1

Ovirt 4.3.10 Glusterfs SSD slow performance over 10GE
by jury cat 07 Jul '20

07 Jul '20

Hello all, I am using Ovirt 4.3.10 on Centos 7.8 with glusterfs 6.9 . My Gluster setup is of 3 hosts in replica 3 (2 hosts + 1 arbiter). All the 3 hosts are Dell R720 with Perc Raid Controller H710 mini(that has maximim throughtout 6Gbs) and with 2×1TB samsumg SSD in RAID 0. The volume is partitioned using LVM thin provision and formated XFS. The hosts have separate 10GE network cards for storage traffic. The Gluster Network is connected to this 10GE network cards and is mounted using Fuse Glusterfs(NFS is disabled).Also Migration Network is activated on the same storage network. The problem is that the 10GE network is not used at full potential by the Gluster. If i do live Migration of Vms i can see speeds of 7GB/s ~ 9GB/s. The same network tests using iperf3 reported 9.9GB/s , these exluding the network setup as a bottleneck(i will not paste all the iperf3 tests here for now). I did not enable all the Volume options from "Optimize for Virt Store", because of the bug that cant set volume cluster.granural-heal to enable(this was fixed in vdsm-4 40, but that is working only on Centos 8 with ovirt 4.4 ) . i whould be happy to know what are all these "Optimize for Virt Store" options, so i can set them manually. The speed on the disk inside the host using dd is b etween 1GB/s to 700Mbs. [root@host1 ~]# dd if=/dev/zero of=test bs=100M count=40 cou nt=80 status=progress 8074035200 bytes (8.1 GB) copied, 11.059372 s, 730 MB/s 80+0 records in 80+0 records out 8388608000 bytes (8.4 GB) copied, 11.9928 s, 699 MB/s The dd write test on the gluster volme inside the host is poor only ~ 120MB/s . During the dd test, if i look at Networks->Gluster network ->Hosts at Tx and Rx the network speed barerly reaches over 1Gbs (~1073 Mbs) out of maximum of 10000 Mbs. dd if=/dev/zero of=/rhev/data-center/mnt/glu sterSD/gluster1.domain.local\:_data/test bs=100M count=80 status=progress 8283750400 bytes (8.3 GB) copied, 71.297942 s, 116 MB/s 80+0 records in 80+0 records out 8388608000 bytes (8.4 GB) copied, 71.9545 s, 117 MB/s I have attached my Gluster volume settings and mount options. Thanks, Emy

4 10

Running Self Hosted-Engine on the same iSCSI target as other Storage Domains
by Erez Zarum 07 Jul '20

07 Jul '20

We are using Dell SC (Storage) with iSCSI with oVirt, it is impossible to create a new Target Portal with a specific LUN so it's impossible to isolate the SE LUN from other LUNs that are in use by other Storage Domains. According to the documentations this is not a best practice, while searching i ran into that specific issue but it seems to be solved. Is it still by best practice when using oVirt 4.4 to use a whole different target for the SE? If it is not possible giving the current envrionment restrictions is the only option for us is to attach a few disks to each servers and create a small gluster cluster (volume) just for the SE?

2 1

Re: broker.log not rotating
by Strahil Nikolov 07 Jul '20

07 Jul '20

Yes, ovirt-ha-broker and ovirt-ha-agent take care of HostedEngine to be up and running and in case something goes bad - to be migrated away. Best Regards, Strahil Nikolov На 3 юли 2020 г. 7:53:14 GMT+03:00, Anton Louw via Users <users(a)ovirt.org> написа: >Hi Everybody, > >Thanks for all the responses. So I managed to truncate the log. I just >want to make sure, the ‘ovirt-ha-agent’ service is only for the hosted >engine correct? > >I can still migrate machines between the hosts, so it should then not >impact the VMs? > >Thanks > > >Anton Louw >Cloud Engineer: Storage and Virtualization >______________________________________ >D: 087 805 1572 | M: N/A >A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg >anton.louw(a)voxtelecom.co.za > >www.vox.co.za > > > >From: Darrell Budic <budic(a)onholyground.com> >Sent: 02 July 2020 19:56 >To: Anton Louw <Anton.Louw(a)voxtelecom.co.za> >Cc: users(a)ovirt.org >Subject: Re: [ovirt-users] broker.log not rotating > >They’re just log files, so generally safe to delete. You may want to >take a look at the huge one though, see what’s up. I had a similar >problem that turned out to be a broken HA agent install, cleaned and >reinstalled and it went back to the same volume of logs as the others. > >Now I need to check if they added logrotate.d config files for it to >clean those up, hum. > > -Darrell > > >On Jul 2, 2020, at 12:00 AM, Anton Louw via Users ><users(a)ovirt.org<mailto:users@ovirt.org>> wrote: > > > >Hi All, > >I had a space alert on one of my nodes this morning, and when I looked >around, I saw that var/log/ovirt-hosted-engine-ha/broker.log was >sitting at around 30GB. Does anybody know if it is safe to delete the >log file? Or is there another process that I should follow? > >I had a look at my other nodes, and the broker.log file does not exceed >4GB. > >Thank you > >Anton Louw >Cloud Engineer: Storage and Virtualization at Vox >________________________________ >T: 087 805 0000 | D: 087 805 1572 >M: N/A >E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> >A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg >www.vox.co.za<http://www.vox.co.za/> > >[F]<https://www.facebook.com/voxtelecomZA> > >[T]<https://www.twitter.com/voxtelecom> > >[I]<https://www.instagram.com/voxtelecomza/> > >[L]<https://www.linkedin.com/company/voxtelecom> > >[Y]<https://www.youtube.com/user/VoxTelecom> > > >[#VoxBrand]<https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > >Disclaimer >The contents of this email are confidential to the sender and the >intended recipient. Unless the contents are clearly and entirely of a >personal nature, they are subject to copyright in favour of the holding >company of the Vox group of companies. Any recipient who receives this >email in error should immediately report the error to the sender and >permanently delete this email from all storage devices. > >This email has been scanned for viruses and malware, and may have been >automatically archived by Mimecast Ltd, an innovator in Software as a >Service (SaaS) for business. Providing a safer and more useful place >for your human generated data. Specializing in; Security, archiving and >compliance. To find out more Click >Here<https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > > >_______________________________________________ >Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> >To unsubscribe send an email to >users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> >Privacy Statement: >https://www.ovirt.org/privacy-policy.html<https://www.ovirt.org/privacy-policy.html> >oVirt Code of Conduct: >https://www.ovirt.org/community/about/community-guidelines/<https://www.ovirt.org/community/about/community-guidelines/> >List Archives: >https://lists.ovirt.org/archives/list/users@ovirt.org/message/4L6OOVVW6KOSB…<https://lists.ovirt.org/archives/list/users@ovirt.org/message/4L6OOVVW6KOSB…>

1 0

oVirt 4.4.0, slave interfaces are down after a reboot
by Erez Zarum 07 Jul '20

07 Jul '20

Fresh installation of oVirt 4.4.0 (using the ISO), after restarting an host, the host comes up but the slave interfaces of a bond remains in down state. The only way to bring it up is to login via IPMI and restart the "NetworkManager" service. Weird thing, after this, the host says that it's network is out of sync, this happens on a network that is marked as "migration network", what is out of sync is the gateway. I have restart the host again (this happens on all hosts) and i can see that after a restart the NetworkManager state (nmcli c show bond0.421 as example) does not list the routes, after syncing the routes are there.

2 2

iSCSI array "Storage domain does not exist" error after array reboot
by Kevin Doyle 07 Jul '20

07 Jul '20

I am running a hosted engine using iscsi. I had to reboot the array, I took down all the VM's and put the VM data storage into maintenance mode. I also put the hosted engine "hosted-engine --set-maintenance --mode =global" and shut down the engine "hosted-engine --vm-shutdown" I also stopped the broker and agent systemctl stop ovirt-ha-broker' ; 'systemctl stop ovirt-ha-agent' The array was rebooted. I started the broker and agent systemctl start ovirt-ha-broker' ; 'systemctl start ovirt-ha-agent' However I now see errors in the vdsm log INFO (jsonrpc/4) [storage.TaskManager.Task] (Task='76547cc5-e4f0-454c-ac46-c341e7f6d54c') aborting: Task is aborted: "Storage domain does not exist: (u'5626eba7-ebd8-4578-baf0-ca4f4af5889b',)" - code 358 (task:1181) 2020-07-07 14:01:25,098+0100 ERROR (jsonrpc/4) [storage.Dispatcher] FINISH prepareImage error=Storage domain does not exist: (u'5626eba7-ebd8-4578-baf0-ca4f4af5889b',) (dispatcher:83) 2020-07-07 14:01:25,098+0100 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Image.prepare failed (error 358) in 0.07 seconds (__init__:312) INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=93d7e2d6-17ee-4370-b8c4-fb32a3887021 (api:48) 2020-07-07 14:01:25,592+0100 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=93d7e2d6-17ee-4370-b8c4-fb32a3887021 (api:54) 2020-07-07 14:01:25,592+0100 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:709) I have 6 hosts. I have tried rebooting them all, I have tried just running 1 host that was originally hosting the engine, but I cannot bring up the hosted engine. Has anyone any ideas ? how to reconnect the storage domain The hosted engine had its own iscsi disk separate from the VM's thanks Kevin

2 1

How to use sysprep to create Windows templates
by wodel youchi 07 Jul '20

07 Jul '20

Hi, I need to create some Windows Templates for my client, and I am not quite familiar with the Windows sysprep installations. I read the "Sealing a Windows Virtual Machine for Deployment as a Template" on the Virtual Machine Management Guide. What I don't understand is the process of sealing a Windows VM. When should I use the /usr/share/ovirt-engine/conf/sysprep/sysprep.* files? at the creation of the VM that will be a template at the end? or at the creation of new VMs based on the template? When should I use the /etc/ovirt-engine/osinfo.conf.d/xx.files.properties? at the creation of the VM that will be a template at the end? or at the creation of new VMs based on the template? What is the difference between : "Use Cloud-Init/Sysprep" in the VM edit window and the RUN Once window? For me it is not clear, could someone help me to understand. Regards.

2 2