- Users - oVirt List Archives

Ovirt 4.4/ Centos 8 issue with nfs?
by lee.hanel＠gmail.com 13 Oct '20

13 Oct '20

Greetings, I'm trying to upgrade from 4.3 to 4.4. When trying to mount the original nfs items, I'm getting the following error: vdsm.storage.exception.StorageServerAccessPermissionError: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: 'path = /rhev/data-center/mnt/nfshost:nfs_path' with the following stack trace: 2020-10-08 19:00:17,961+0000 ERROR (jsonrpc/4) [storage.HSM] Could not connect to storageServer (hsm:2421) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 82, in validateDirAccess getProcPool().fileUtils.validateAccess(dirPath) File "/usr/lib/python3.6/site-packages/vdsm/storage/outOfProcess.py", line 194, in validateAccess raise OSError(errno.EACCES, os.strerror(errno.EACCES)) PermissionError: [Errno 13] Permission denied During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2418, in connectStorageServer conObj.connect() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 449, in connect return self._mountCon.connect() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 190, in connect six.reraise(t, v, tb) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 183, in connect self.getMountObj().getRecord().fs_file) File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 93, in validateDirAccess raise se.StorageServerAccessPermissionError(dirPath) via an ls, it looks like there are the correct permissions: ls -alh total 0 drwxr-xr-x. 1 vdsm kvm 100 Oct 8 19:15 . drwxr-xr-x. 4 vdsm kvm 115 Oct 8 19:02 .. drwxr-xr-x. 1 vdsm kvm 52 Oct 1 20:35 ffe7b7bb-a391-42a9-9bae-480807509778 d---------. 1 vdsm kvm 22 Mar 17 2020 '#recycle' But, I wrote a short script to check the individual permissions that are checked, and it thinks I can't write to the directory: We can Read From it: /rhev/data-center/mnt/nfshost:nfspath We can't write to it: /rhev/data-center/mnt/nfshost:nfspath We can execute to it: /rhev/data-center/mnt/nfshost:nfspath This is doing a simple: print(os.stat(path)) if os.access(path, os.F_OK): print("It Exists", "/rhev/data-center/mnt/nfshost:nfspath") else: print("It Doesn't Exists", "/rhev/data-center/mnt/nfshost:nfspath") if os.access(path, os.R_OK): print("We can Read From it: ", "/rhev/data-center/mnt/nfshost:nfspath") else: print("We can't Read from it: ", "/rhev/data-center/mnt/nfshost:nfspath") if os.access(path, os.W_OK): print("We can write to it: ", "/rhev/data-center/mnt/nfshost:nfspath") else: print("We can't write to it: ", "/rhev/data-center/mnt/nfshost:nfspath") if os.access(path, os.X_OK): print("We can execute to it: ", "/rhev/data-center/mnt/nfshost:nfspath") else: print("We can can't to it: ", "/rhev/data-center/mnt/nfshost:nfspath") I took this same checks over to the Centos 7 host, and I it passes the checks fine. Does anyone have any ideas? Thanks, Lee

4 7

VM reboot cause SERVER reboot (oVirt 4.4.2)
by luigi.voso＠convergenze.it 12 Oct '20

12 Oct '20

Hi all, I've a SUPERMICRO server with a M10 GPU (at the moment i've a free-trial license) and i'm using oVirt 4.4.2. My issue is very strange and it seems to be a bug because i can reproduce it: 1. Create a VM (i've tested on Win10Pro/WinServer2012R2) with a vGPU and install the driver (without driver installed, this issue does not appear); 2. Restart the VM. At this point the physical server restarts. Instead, when i shutdown the windows vm, this issue is not appear. I've also tried with a centos 8 vm and it works very well (no reboot). All NVIDIA driver's are update at the 2020-09-30 latest release (11.0). All windows driver are installed (virtio-win-0.1.189). The VM works very well and the vGPU too. This is my very first test with vGPU and i can't understand the reason of this issue. NVIDIA enterprise support told me that it's an ovirt problem, because Windows guest operating system are supported only under Red Hat subscription programs. Has anyone else had the same problem or can you help me? Thank you in advance

1 0

Last week for participating to oVirt Survey Autumn 2020
by Sandro Bonazzola 12 Oct '20

12 Oct '20

Hi, just a kind reminder this is last week for participating to oVirt Survey Autumn 2020! The survey is closing on October 18 2020. You can submit your response at https://docs.google.com/forms/u/1/d/e/1FAIpQLSdzzh_MSsSq-LSQLauJzuaHC0Va1ba… *Please note the answers to this survey will be publicly accessible.* This survey is under oVirt Privacy Policy available at https://www.ovirt.org/privacy-policy.html -- 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. <https://mojo.redhat.com/docs/DOC-1199578>* * <https://www.redhat.com/it/forums/emea/italy-track>*

1 0

oVirt 4.4 - HA Proxy Fencing
by Jeremey Wise 11 Oct '20

11 Oct '20

I have a pair of nodes which service DNS / NTP / FTP / AD /Kerberos / IPLB etc.. ns01, ns02 These two "infrastructure VMs have HA Proxy and pacemaker and I have set to have "HA" within ovirt and node affinity. But.. within HAProxy, the nodes use to be able to call the STONITH function of KVM to reset a node if / as needed. Fence Device: "stonith:fence_virsh" But with oVirt this function no longer works. For VMs and other applications which need STONITH functions, how would this be done with oVirt. I would assume the call would be to oVirt-Engine now, but not seeing documentation on HA-Proxy / Pacemaker to use oVirt. Can someone point me in the right direction? -- penguinpages

2 1

Fencing with oVirt 4.4 apc master switch
by Jeremey Wise 11 Oct '20

11 Oct '20

I use to have hand built CentOS+KVM + Gluster. Moved to HCI oVirt controlled system and so far, been very happy with stability and quality. One feature that was working in old "hand build" version was fencing. I have an old APC master switch AP9606. I use to have and use it for master switch functions of nodes but sense replacement with oVirt it has not worked. Here are setup notes and symptoms IP: 172.16.100.2 Username: apc Password: <blah> Port 8 (it is an eight port unit) Slot: <empty as I have no idea what is expects here I also input values here but no change> Error: Test failed: WARNING:root:Parse error: Ignoring option 'agent' because it does not have value ERROR:root:Unable to connect/login to fencing device 2020-10-11 11:28:50,885 ERROR: Unable to connect/login to fencing device Questions: 1) Has anyone setup this with oVirt such that it uses apc master switch 2) Where is oVirt putting these logs / running this service. I assumed oVirt engine running the services and so tried to find details and logs here. -- penguinpages

1 0

ovirt broker how to modify network_test dns ip address?
by wodel youchi 11 Oct '20

11 Oct '20

Hi, How to modify the ip address of the DNS server used by ovirt-broker for testing? Regards.

2 1

too many glitches while moving storage domain
by Jiří Sléžka 11 Oct '20

11 Oct '20

Hi, today I started one not so common operation and I would like to share my (not so good) experience. I have 4 old Opteron G3 hosts which creates 1 DC with 1 cluster with 4.2 compatibility. Then I got 2 newer Intel based hosts which creates separate DC and cluster. I use one shared FC storage with few LUNs for all the stuff. Intel cluster is selfhosted with oVirt 4.4.2 where I migrated original standalone oVirt 4.3.10 manager. So I have 2 DCs, one with 4.2 and one with 4.4 compatibility. Now the funny part... I had 2 LUNs connected to old 4.2 DC. My intention was detach one of them and attach it to the new DC. first pain was that some of vms had ther disks on both LUNs. It is indicated late in the process and without hint which vms they are. So I had to activate LUN in old DC and tried to find that vms (search string in vms tab "Storage = one and Storage = two" seems not working). Ok, it took two or three rounds... then, also late in the process there was problem that one vm had previewed snapshot so another round with activation of LUN in old DC... Then I was able detach and import LUN to new DC. Nice, but with warning that LUN has 4.2 compatibility which will be converted to 4.4 and there is no way back to connect it to old DC... It is logical but very scary if something went wrong... but it did not in my case :-) LUN is connected in new DC. Now I had to import vms. Most vms were imported ok but two of them were based on template wich resides on other LUN. It was not indicated during detaching! It looks like I cannot move template from storage to storage other way than through Export storage (which I don't have at this moment) or through OVA export for which I have not enough free storage space on hosts. Its a trap! :-) Btw. there is no check for free space while starting export to OVA (template uses preallocated disk). Exporting task still runs but there is no free space at the host... and probably no way to cancel it from manager :-( Ok, I had most of the vms imported. Last really strange thing is that I lost one vm during import. It is not listed in VirtualMachines nor in VM import tab on starage nor in Disk tab... that vm was an Aruba migration tool and was imported from OVN image. In fact there are two disks in Disk import tab, one of them has no Alias/description and was created today around time I started work on this migration. The second one has alias "vmdisk1" and is few months older but I have no idea if it is the lost vm... Sorry for long story, TL;DR version could be: There are glitches in some (not so common) workflows... Cheers, Jiri

2 1

Nodes with a version and others with anothers
by Julio Cesar Bustamante 09 Oct '20

09 Oct '20

Hi everyone is it recommendable to have nodes with ovirt host with a version and others nodes with another version? for example 5 nodes with this description Versión SO -: RHEL - 7 - 6.1810.2.el7.centos Descripción de SO: CentOS Linux 7 (Core) Versión del kernel: 3.10.0 - 957.10.1.el7.x86_64 Versión KVM: 2.12.0 - 18.el7_6.3.1 Versión LIBVIRT: libvirt-4.5.0-10.el7_6.6 Versión VDSM: vdsm-4.20.46-1.el7 Versión de SPICE: 0.14.0 - 6.el7_6.1 Versión GlusterFS: [N. D.] Versión CEPH: librbd1-10.2.5-4.el7 And a node with ths Versión SO -: RHEL - 7 - 5.1804.5.el7.centos Descripción de SO: oVirt Node 4.2.7.1 Versión del kernel: 3.10.0 - 862.14.4.el7.x86_64 Versión KVM: 2.10.0 - 21.el7_5.7.1 Versión LIBVIRT: libvirt-3.9.0-14.el7_5.8 Versión VDSM: vdsm-4.20.43-1.el7 Versión de SPICE: 0.14.0 - 2.el7_5.5 Versión GlusterFS: glusterfs-3.12.15-1.el7 Versión CEPH: librbd1-0.94.5-2.el7

1 0

Disconnected -- Server has closed the connection
by info＠worldhostess.com 09 Oct '20

09 Oct '20

A first part of the fresh install is without any problems and the second part of the fresh install the storage part "Disconnected - Server has closed the connection." Thereafter the OVirt is unstable and disconnect continuously. "Unexpected error - Cockpit had an unexpected internal error." "You can try restarting Cockpit by pressing refresh in your browser. The javascript console contains details about this error (Ctrl-Shift-J in most browsers)." Ctrl-Shift-J in most browsers --- RESULTS DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/jquery.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/cockpit.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/shell/index.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/jquery.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/cockpit.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/patternfly.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE index.js:15 Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://XYZ.co.za:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback. h @ index.js:15 t.inject @ index.js:15 t.a @ index.js:15 (anonymous) @ index.js:6 (anonymous) @ index.js:6 n @ index.js:1 (anonymous) @ index.js:72 n @ index.js:1 (anonymous) @ index.js:15 n @ index.js:1 (anonymous) @ index.js:1 (anonymous) @ index.js:1 DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/shell/index.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/shell/index.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca082ec115b4b7401aa8829/ov irt-dashboard/index.html#/:1 Refused to apply style from 'https://XYZ.co.za:9090/src/base1/patternfly.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. updates.js:11 Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://XYZ.co.za:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback. m @ updates.js:11 t.inject @ updates.js:11 t.a @ updates.js:11 (anonymous) @ updates.js:6 (anonymous) @ updates.js:6 n @ updates.js:1 (anonymous) @ updates.js:43 n @ updates.js:1 (anonymous) @ updates.js:11 n @ updates.js:1 (anonymous) @ updates.js:1 (anonymous) @ updates.js:1 DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/cockpit.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/jquery.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE overview.js:20 Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://XYZ.co.za:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback. p @ overview.js:20 t.inject @ overview.js:20 t.a @ overview.js:20 (anonymous) @ overview.js:6 (anonymous) @ overview.js:6 n @ overview.js:1 (anonymous) @ overview.js:20 n @ overview.js:1 (anonymous) @ overview.js:77 n @ overview.js:1 (anonymous) @ overview.js:82 n @ overview.js:1 (anonymous) @ overview.js:82 n @ overview.js:1 (anonymous) @ overview.js:1 (anonymous) @ overview.js:1 DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/patternfly.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/system/services.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE services.js:19 Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' https://XYZ.co.za:9090". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback. m @ services.js:19 t.inject @ services.js:19 t.a @ services.js:19 (anonymous) @ services.js:6 (anonymous) @ services.js:6 n @ services.js:1 (anonymous) @ services.js:19 n @ services.js:1 (anonymous) @ services.js:19 n @ services.js:1 (anonymous) @ services.js:56 n @ services.js:1 (anonymous) @ services.js:56 n @ services.js:1 (anonymous) @ services.js:1 (anonymous) @ services.js:1 DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/cockpit.min.css.map: Certificate error: net::ERR_CERT_AUTHORITY_INVALID DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/updates/updates.min.js.map: Certificate error: net::ERR_CERT_AUTHORITY_INVALID DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/updates/updates.css.map: Certificate error: net::ERR_CERT_AUTHORITY_INVALID DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/system/overview.min.js.map: Certificate error: net::ERR_CERT_AUTHORITY_INVALID DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/system/overview.css.map: Certificate error: net::ERR_CERT_AUTHORITY_INVALID DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/system/services.min.js.map: Certificate error: net::ERR_CERT_AUTHORITY_INVALID DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/performance/performance.min.js.map: Certificate error: net::ERR_CERT_AUTHORITY_INVALID DevTools failed to load SourceMap: Could not load content for https://XYZ.co.za:9090/cockpit/$1aa0545898ca0350c292c35fee90966b96bf77ad1ca0 82ec115b4b7401aa8829/base1/patternfly.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE 5[Intervention] Slow network is detected. See <URL> for more details. Fallback font will be used while loading: <URL> cockpit.js:606 grep: /sys/class/dmi/id/power/autosuspend_delay_ms: Input/output error p @ cockpit.js:606 m @ cockpit.js:616 v @ cockpit.js:511 a.onmessage.o.dispatch_data @ cockpit.js:441 e @ cockpit.js:297 postMessage (async) (anonymous) @ index.js:72 a.onmessage.o.dispatch_data @ cockpit.js:439 cockpit.js:606 which: no nodectl in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin) p @ cockpit.js:606 m @ cockpit.js:616 v @ cockpit.js:511 a.onmessage.o.dispatch_data @ cockpit.js:441 e @ cockpit.js:297 postMessage (async) (anonymous) @ index.js:72 a.onmessage.o.dispatch_data @ cockpit.js:439 app.js:43 nodectl is not installed. Disabling node functionality index.js:72 transport closed: disconnected (anonymous) @ index.js:72 dispatch @ jquery.js:3816 v.handle @ jquery.js:3679 se @ cockpit.js:76 e @ cockpit.js:223 p @ cockpit.js:607 m @ cockpit.js:616 e @ cockpit.js:456 a.onclose @ cockpit.js:421 patternfly.css:1 GET https://XYZ.co.za:9090/cockpit/static/fonts/RedHatDisplay-Medium.woff2 net::ERR_CERT_AUTHORITY_INVALID Yours Sincerely, Henni

2 2

Re: Gluster volume not responding
by Strahil Nikolov 09 Oct '20

09 Oct '20

Hi Simon, I doubt the system needs tuning from network perspective. I guess you can run some 'screen'-s which a pinging another system and logging everything to a file. Best Regards, Strahil Nikolov В петък, 9 октомври 2020 г., 01:05:22 Гринуич+3, Simon Scott <simon(a)justconnect.ie> написа: Thanks Strahil. I have found between 1 & 4 Gluster peer rpc-clnt-ping timer expired messages in the rhev-data-center-mnt-glusterSD-hostname-strg:_pltfm_data01.log on the storage network IP. Of the 6 Hosts only 1 does not have these timeouts. Fencing has been disabled but can you identify which logs are key to identifying the cause please. It's a bonded (bond1) 10GB ovirt-mgmt logical network and Prod VM VLAN interface AND a bonded (bond2) 10GB Gluster storage network. Dropped packets are seen incrementing in the vdsm.log but neither ethtool -S or kernel logs are showing dropped packets. I am wondering if they are being dropped due to the ring buffers being small. Kind Regards Shimme ________________________________ From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Thursday 8 October 2020 20:40 To: users(a)ovirt.org <users(a)ovirt.org>; Simon Scott <simon(a)justconnect.ie> Subject: Re: [ovirt-users] Gluster volume not responding >Every Monday and Wednesday morning there are gluster connectivity timeouts >but all checks of the network and network configs are ok. Based on this one I make the following conclusions: 1. Issue is reoccuring 2. You most probably have a network issue Have you checked the following: - are there any ping timeouts between fuse clients and gluster nodes - Have you tried to disable fencing and check the logs after the issue reoccurs - Are you sharing Blackup and Prod networks ? Is it possible some backup/other production load in your environment to "black-out" your oVirt ? - Have you check the gluster cluster's logs for anything meaningful ? Best Regards, Strahil Nikolov

1 0

Moving VM disks from one storage domain to another. Automate?
by Green, Jacob Allen /C 09 Oct '20

09 Oct '20

I am looking for an automated way, via Ansible to move a VM disk from one storage domain to another. I found the following, https://docs.ansible.com/ansible/latest/modules/ovirt_disk_module.html and while it mentions copying a VM disk image from one domain to another it does not mention a live storage migration. Which is what I am looking to do. I want to take roughly 100 VMs and move their disk images from one domain to another that is available to the datacenter in some automated/scripted fashion. I am just curious if anyone out there has had to do this and how they tackled it. Or perhaps I am missing some easy obvious way, other than clicking all the disks and clicking move. However from the looks of it, if I did click all the disk and selected move, it appears RHV tries to do them all at once, which is probably not ideal, I would like it to move the disks in a serial One after another fashion, to conserve throughput and IO. I also did not see anything on Ansible galaxy or the ovirt github that would do this. Thank you.

3 2

Gluster volume not responding
by simon＠justconnect.ie 09 Oct '20

09 Oct '20

Hi, Every Monday and Wednesday morning there are gluster connectivity timeouts but all checks of the network and network configs are ok. Description of problem: The following entries were found in the engine.log following VMs becoming unresponsive and hosts fencing. This issue has been causing issues since the beginning of September and no amount of reading logs is helping. This issue occurs every Wednesday morning at exactly the same time. WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-974045) [] domain 'bc482086-598b-46b1-9189-0146fa03447c:pltfm_data03' in problem 'PROBLEMATIC'. vds: 'bdtpltfmovt02' WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-974069) [] domain 'bf807836-b64e-4913-ab41-cfe04ca9abab:pltfm_data01' in problem 'PROBLEMATIC'. vds: 'bdtpltfmovt02' WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-974121) [] domain 'bc482086-598b-46b1-9189-0146fa03447c:pltfm_data03' in problem 'PROBLEMATIC'. vds: 'bdtpltfmovt03' INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] VM '00a082de-c827-4c97-9846-ec32d1ddbfa6'(bdtfmnpproddb03) moved from 'Up' --> 'NotResponding' INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] VM 'f5457f04-054e-4684-9702-40ed4a3e4bdb'(bdtk8shaproxy02) moved from 'Up' --> 'NotResponding' INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] VM 'bea85b27-18e7-4936-9871-cdb987baebdd'(bdtdepjump) moved from 'Up' --> 'NotResponding' INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] VM 'ba1d4fe2-97e7-491a-9485-8319281e7784'(bdtcmgmtnfs01) moved from 'Up' --> 'NotResponding' INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] VM '9e253848-7153-43e8-8126-dba2d7f2d214'(bdtdepnfs01) moved from 'Up' --> 'NotResponding' INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] VM '1e58d106-4b65-4296-8d11-2142abb7808e'(bdtionjump) moved from 'Up' --> 'NotResponding' VDSM Log from one of the Gluster Peers: [2020-10-05 03:03:25.038883] W [MSGID: 114031] [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-pltfm_data02-client-0: remote operation failed. Path: / (00000000-0000-0000-0000-000000000001) [Transport endpoint is not connected] [2020-10-07 05:37:39.582138] C [rpc-clnt-ping.c:162:rpc_clnt_ping_timer_expired] 0-pltfm_data02-client-0: server x.x.x.x:49153 has not responded in the last 30 seconds, disconnecting. [2020-10-07 05:37:39.583217] I [MSGID: 114018] [client.c:2288:client_rpc_notify] 0-pltfm_data02-client-0: disconnected from pltfm_data02-client-0. Client process will keep trying to connect to glusterd until brick's port is available [2020-10-07 05:37:39.584213] E [rpc-clnt.c:346:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fe83aa96fbb] (--> /lib64/libgfrpc.so.0(+0xce11)[0x7fe83a85fe11] (--> /lib64/libgfrpc.so.0(+0xcf2e)[0x7fe83a85ff2e] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x91)[0x7fe83a861521] (--> /lib64/libgfrpc.so.0(+0xf0c8)[0x7fe83a8620c8] ))))) 0-pltfm_data02-client-0: forced unwinding frame type(GlusterFS 4.x v1) op(LOOKUP(27)) called at 2020-10-07 05:37:09.003907 (xid=0x7e6a8c) Current Version: 4.3.4.3-1.el7 - Although we are keen to upgrade, we need stability for this production environment before doing so. This Data Center has 2 x 3 Node clusters (Admin & Platform) which each have a 3 Replica Gluster configuration which is not managed by the self hosted ovirt engine. Any assistance is appreciated. Regards Shimme

3 3

user role
by kim.kargaard＠noroff.no 08 Oct '20

08 Oct '20

Hi all, For a group of users added to ovirt through AD, which role should one add to an ISO for the group to be able to select an ISO when creating VM's in the VM portal? Thanks. Kim

2 1

[ANN] oVirt 4.4.3 Fourth Release Candidate is now available for testing
by Lev Veyde 08 Oct '20

08 Oct '20

oVirt 4.4.3 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Fourth Release Candidate for testing, as of October 8th, 2020. This update is the third in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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>. 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.3 release highlights: http://www.ovirt.org/release/4.4.3/ * 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.3/ [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

Re: Is it possible to backup stopped vm? (ovirt 4.4)
by Eyal Shenitzky 08 Oct '20

08 Oct '20

Hi Lukaz, Backup using the new incremental backup API is supported only for running VMs. On Thu, 8 Oct 2020 at 12:36, Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > While trying to backup stopped VM (with POST on > /ovirt-engine/api/vms/b79b34c0-d8db-43e5-916e-5528ff7bcfbe/backups) I got > the response: > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <fault> > <detail>[Cannot backup VM. The Virtual Machine should be in Up status.]</ > detail> > <reason>Operation Failed</reason> > </fault> > > I found here: > https://www.ovirt.org/develop/release-management/features/storage/increment… > that it should be possible to back up a virtual machine that is not running. > *"If the VM is not running, the system will create a paused, stripped-down > version of the VM, with only backup disks attached, and use libvirt API to > start and stop the backup."* > If you will read until the end of the paragraph you will see that the support for this deferred at this time- We considered alternative solution using qemu-nbd, but According to Eric Blake qemu-nbd does not support yet exposing bitmap info, so we would not be able to provide the change block list. Since creating special paused VM for backing up non-running VM is a lot of work, we may defer support for backing up non-running VMs. > > But it doesn't seem to work. > > 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.* > > _______________________________________________ > 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/QGUVJW5HWQG6W… > -- Regards, Eyal Shenitzky

1 0

oVirt documentation updates
by Sandro Bonazzola 08 Oct '20

08 Oct '20

The oVirt documentation team updated the following guides: - Administration Guide <https://ovirt.org/documentation/administration_guide/> - Data Warehouse Guide <https://ovirt.org/documentation/data_warehouse_guide/> - Disaster Recovery Guide <https://ovirt.org/documentation/disaster_recovery_guide/> - Virtual Machine Management Guide <https://ovirt.org/documentation/virtual_machine_management_guide/> Thanks, -- 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.* * <https://www.redhat.com/it/forums/emea/italy-track>*

1 0

Re: Upgrade Host Compatibility Version
by jb 07 Oct '20

07 Oct '20

Sorry, last time I didn't answer to the mailing list... Here are the output: *CentOS Linux release 8.2.2004 (Core)* I use the kernel-plus, because of an old raid controller. Can this be a problem? ** Jonathan * * * * Am 07.10.20 um 13:21 schrieb Dana Elfassy: > Thanks Jonathan > Can you tell me what is the OS version of the host that you're using? > (cat /etc/redhat-release) > > Dana > > On Mon, Oct 5, 2020 at 4:31 PM jb <jonbae77(a)gmail.com > <mailto:jonbae77@gmail.com>> wrote: > > Hello Dana, > > I added a second host, and tried again, without success. > > The error is unspecific, it just says: *Upgrade of cluster default > failed.* > > Here the engine.log > > > Jonathan > > > > * > * > > Am 05.10.20 um 11:00 schrieb Dana Elfassy: >> Hi Jonathan, >> What is the error you're getting when you're trying to upgrade >> using the upgrade guide? >> Can you also attach the engine log? >> (/var/log/ovirt-engine/engine.log) >> Thanks, >> Dana >> >> On Sun, Oct 4, 2020 at 6:54 PM jb <jonbae77(a)gmail.com >> <mailto:jonbae77@gmail.com>> wrote: >> >> Hello everybody, >> >> for some days I upgrade our environment from ovirt 4.3 to >> 4.4.2 and now >> I stuck on upgrading the host compatibility version. It show >> there a >> compatibility until version 4.4. The VMs have a limit until >> version 4.5 >> and the cluster shows to that I can upgrade them until 4.5. >> >> On the cluster page is also a Upgrade guide, but this fails >> when I try >> that one. At the moment I have only one host to upgrade (no >> hosted >> engine)... >> >> Thanks for helping! >> >> Jonathan >> _______________________________________________ >> 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/OULJ2FCU3CLFQ… >> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/OULJ2FCU3CLFQ…> >>

2 2

oVirt Survey Autumn 2020
by Sandro Bonazzola 07 Oct '20

07 Oct '20

As we continue to develop oVirt 4.4, the Development and Integration teams at Red Hat would value insights on how you are deploying the oVirt environment. Please help us to hit the mark by completing this short survey. The survey will close on October 18th 2020. If you're managing multiple oVirt deployments with very different use cases or very different deployments you can consider answering this survey multiple times. *Please note the answers to this survey will be publicly accessible*. This survey is under oVirt Privacy Policy available at https://www.ovirt.org/site/privacy-policy.html . The survey is available https://forms.gle/bPvEAdRyUcyCbgEc7 -- 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.*

3 4

ldap auth problem after upgrade from 4.4.1 to 4.4.2
by Jiří Sléžka 07 Oct '20

07 Oct '20

Hi, I just upgraded my HE to 4.4.2 but now I cannot login using my ldap aaa profile anymore. We are using Novell/NetIQ E-directory (load ballanced by haproxy, probably not important...) In 4.4.1 I was hit by removed TLSv1 (which is the newest protocol supported by our edir) from default crypto policies but I was able revert it by update-crypto-policies --set LEGACY after upgrade to 4.4.2 the error is server_error: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) but our ldap server is reachable from ovirt, I tested it via (also ldaps and startls variants are working) ldapsearch -H ldap://ldap1.slu.cz -x -D cn=*****,ou=******,o=su -w '************' -b 'o=su' As a workaround I tried to set plain ldap protocol in profile cat /etc/ovirt-engine/aaa/CRO.properties include = <rfc2307-edir.properties> vars.server = ldap1.slu.cz vars.port = 389 vars.user = cn=*****,ou=******,o=su vars.password = ************** pool.default.serverset.single.server = ${global:vars.server} pool.default.serverset.single.port = ${global:vars.port} pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} pool.default.ssl.startTLS = false pool.default.ssl.enable = false #pool.default.ssl.protocol = TLSv1 #pool.default.ssl.startTLSProtocol = TLSv1 #pool.default.ssl.insecure = true sequence-init.init.100-my-edir-init-vars = my-edir-init-vars sequence.my-edir-init-vars.010.description = set baseDN sequence.my-edir-init-vars.010.type = var-set sequence.my-edir-init-vars.010.var-set.variable = simple_baseDN sequence.my-edir-init-vars.010.var-set.value = o=su #search.default.search-request.derefPolicy = ALWAYS but the error is the same... ovirt-engine-extensions-tool aaa login-user --profile=CRO --user-name=my_user .... WARNING: [ovirt-engine-extension-aaa-ldap.authn::SU-LDAP-authentication] TLS/SSL insecure mode ... WARNING: [ovirt-engine-extension-aaa-ldap.authn::auth.CRO.slu.cz] Cannot initialize LDAP framework, deferring initialization. Error: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) ... INFO: API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='CRO' user='my_user' Password: ... WARNING: [ovirt-engine-extension-aaa-ldap.authn::auth.CRO.slu.cz] Cannot initialize LDAP framework, deferring initialization. Error: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) Oct 01, 2020 10:57:37 AM org.ovirt.engine.exttool.core.ExtensionsToolExecutor main SEVERE: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) debug with tcpdump reveals only that connection is made and there are only "bindRequest" and "bindResponse success" messages visible (with correct tcp handshake and close) and nothing more any help would be appreciated Cheers, Jiri

4 8

engine-setup in 4.4.2 not using yum/dnf proxy?
by Gianluca Cecchi 07 Oct '20

07 Oct '20

Hello, I'm testing upgrade from 4.3.10 to 4.4.2 for a standalone manager with local database environment. I configured the new engine system as a CentOS 8.2 with a proxy in /etc/yum.conf (that is a link to /etc/dnf/dnf.com) and that worked for all the steps until engine-setup. Now I get this [root@ovmgr1 ~]# engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20201006112458-p84x9i.log Version: otopi-1.9.2 (otopi-1.9.2-1.el8) [ INFO ] DNF Downloading 1 files, 0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloaded CentOS-8 - AppStream [ INFO ] DNF Errors during downloading metadata for repository 'AppStream': .... [ ERROR ] Execution of setup failed and I see in netstat during the phase tcp 0 1 10.4.192.43:33418 18.225.36.18:80 SYN_SENT so it seems it is not using the proxy. Do I have to put proxy info into any other file? Thanks, Gianluca

2 2

Upgrade oVirt from 4.3.10 to 4.4.2 and AD users
by Gianluca Cecchi 06 Oct '20

06 Oct '20

Hello, I'm upgrading a standalone engine with local database and with 3 hosts from oVirt 4.3.10 to 4.4.2 and I'm cross checking both oVirt and RHV documents. In my oVirt environment I have integration with AD for web admin access. Inside RHV upgrade guide docs there is this statement regarding manager upgrade: " Install optional extension packages if they were installed on the Red Hat Virtualization Manager 4.3 machine. # yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j NOTE The configuration for these package extensions must be manually reapplied because they are not migrated as part of the backup and restore process. " In my case I had ovirt-engine-extension-aaa-ldap and ovirt-engine-extension-aaa-misc installed on 4.3.10. So after "engine-backup --mode=restore ...." command I executed: [root@ovmgr1 ~]# yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc Last metadata expiration check: 0:01:11 ago on Tue 06 Oct 2020 11:23:04 AM CEST. Dependencies resolved. ========================================================================================== Package Arch Version Repository Size ========================================================================================== Installing: ovirt-engine-extension-aaa-ldap noarch 1.4.1-1.el8 ovirt-4.4 127 k ovirt-engine-extension-aaa-misc noarch 1.1.0-1.el8 ovirt-4.4 37 k Installing dependencies: unboundid-ldapsdk noarch 4.0.14-2.el8 ovirt-4.4-centos-ovirt44 4.0 M Transaction Summary ========================================================================================== Install 3 Packages Total download size: 4.2 M Installed size: 4.5 M and followed the next upgrade flow steps. After finishing the engine upgrade with the "engine-setup" step, it seems actually that I can still connect to my engine with my AD accounts, so that I don't have to do any manual step described... Does it match any one other experience? Gianluca

2 1

oVirt Node 4.4.2 is now generally available
by Sandro Bonazzola 06 Oct '20

06 Oct '20

oVirt Node 4.4.2 is now generally available The oVirt project is pleased to announce the general availability of oVirt Node 4.4.2 , as of September 25th, 2020. This release completes the oVirt 4.4.2 release published on September 17th 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… ) How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.2 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.2 (redeploy in case of already being on 4.4.2). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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 Node 4.4.2 Release? oVirt Node has been updated, including: - oVirt 4.4.2: http://www.ovirt.org/release/4.4.2/ - Ansible 2.9.13: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ - Advanced Virtualization 8.2.1 See the release notes [1] for installation instructions and a list of new features and bugs fixed. 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/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/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

6 27

Re: Is it possible to backup stopped vm? (ovirt 4.4)
by Nir Soffer 06 Oct '20

06 Oct '20

On Tue, Oct 6, 2020 at 4:08 PM Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > > Hello, > While trying to backup stopped VM (with POST on /ovirt-engine/api/vms/b79b34c0-d8db-43e5-916e-5528ff7bcfbe/backups) I got the response: > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <fault> > <detail>[Cannot backup VM. The Virtual Machine should be in Up status.]</detail> > <reason>Operation Failed</reason> > </fault> Yes, this is not supported now. > I found here: https://www.ovirt.org/develop/release-management/features/storage/increment… that it should be possible to back up a virtual machine that is not running. > "If the VM is not running, the system will create a paused, stripped-down version of the VM, with only backup disks attached, and use libvirt API to start and stop the backup." This is a possible solution we considered, but it is not implemented yet. The next line is: Since creating special paused VM for backing up non-running VM is a lot of work, we may defer support for backing up non-running VMs. We got a request to implement this from other backup vendor, and we are discussing the possible solutions with platform folks. Nir

1 0

Is it possible to backup stopped vm? (ovirt 4.4)
by Łukasz Kołaciński 06 Oct '20

06 Oct '20

Hello, While trying to backup stopped VM (with POST on /ovirt-engine/api/vms/b79b34c0-d8db-43e5-916e-5528ff7bcfbe/backups) I got the response: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <detail>[Cannot backup VM. The Virtual Machine should be in Up status.]</detail> <reason>Operation Failed</reason> </fault> I found here: https://www.ovirt.org/develop/release-management/features/storage/increment… that it should be possible to back up a virtual machine that is not running. "If the VM is not running, the system will create a paused, stripped-down version of the VM, with only backup disks attached, and use libvirt API to start and stop the backup." But it doesn't seem to work. 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

Re: OVN Geneve tunnels not been established
by Konstantinos Betsis 06 Oct '20

06 Oct '20

I did a restart of the ovn-controller, this is the output of the ovn-controller.log 2020-09-11T10:54:07.566Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovn-controller.log 2020-09-11T10:54:07.568Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2020-09-11T10:54:07.568Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2020-09-11T10:54:07.570Z|00004|main|INFO|OVS IDL reconnected, force recompute. 2020-09-11T10:54:07.571Z|00005|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:07.571Z|00006|main|INFO|OVNSB IDL reconnected, force recompute. 2020-09-11T10:54:07.685Z|00007|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:07.685Z|00008|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:08.685Z|00009|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:08.800Z|00010|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:08.800Z|00011|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:08.800Z|00012|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: waiting 2 seconds before reconnect 2020-09-11T10:54:10.802Z|00013|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:10.917Z|00014|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:10.917Z|00015|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:10.917Z|00016|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: waiting 4 seconds before reconnect 2020-09-11T10:54:14.921Z|00017|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:15.036Z|00018|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:15.036Z|00019|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:15.036Z|00020|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: continuing to reconnect in the background but suppressing further logging I have also done the vdsm-tool ovn-config OVIRT_ENGINE_IP OVIRTMGMT_NETWORK_DC This is how the OVIRT_ENGINE_IP is provided in the ovn controller, i can redo it if you wan. After the restart of the ovn-controller the OVIRT ENGINE still shows only two geneve connections one with DC01-host02 and DC02-host01. Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144" hostname: "dc02-host01" Encap geneve ip: "DC02-host01_IP" options: {csum="true"} Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c" hostname: "DC01-host02" Encap geneve ip: "DC01-host02" options: {csum="true"} I've re-done the vdsm-tool command and nothing changed.... again....with the same errors as the systemctl restart ovn-controller On Fri, Sep 11, 2020 at 1:49 PM Dominik Holler <dholler(a)redhat.com> wrote: > Please include ovirt-users list in your reply, to share the knowledge and > experience with the community! > > On Fri, Sep 11, 2020 at 12:12 PM Konstantinos Betsis <k.betsis(a)gmail.com> > wrote: > >> Ok below the output per node and DC >> DC01 >> node01 >> >> [root@dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC01-NODE01*" >> >> node02 >> >> [root@dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC01-NODE02*" >> >> DC02 >> node01 >> >> [root@dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC02-NODE01*" >> >> > Looks good. > > >> DC01 node01 and node02 share the same VM networks and VMs deployed on top >> of them cannot talk to VM on the other hypervisor. >> > > Maybe there is a hint on ovn-controller.log on dc01-node02 ? Maybe > restarting ovn-controller creates more helpful log messages? > > You can also try restart the ovn configuration on all hosts by executing > vdsm-tool ovn-config OVIRT_ENGINE_IP LOCAL_OVIRTMGMT_IP > on each host, this would trigger > > https://github.com/oVirt/ovirt-provider-ovn/blob/master/driver/scripts/setu… > internally. > > >> So I would expect to see the same output for node01 to have a geneve >> tunnel to node02 and vice versa. >> >> > Me too. > > >> On Fri, Sep 11, 2020 at 12:14 PM Dominik Holler <dholler(a)redhat.com> >> wrote: >> >>> >>> >>> On Fri, Sep 11, 2020 at 10:53 AM Konstantinos Betsis <k.betsis(a)gmail.com> >>> wrote: >>> >>>> Hi Dominik >>>> >>>> OVN is selected as the default network provider on the clusters and the >>>> hosts. >>>> >>>> >>> sounds good. >>> This configuration is required already during the host is added to oVirt >>> Engine, because OVN is configured during this step. >>> >>> >>>> The "ovn-sbctl show" works on the ovirt engine and shows only two >>>> hosts, 1 per DC. >>>> >>>> Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144" >>>> hostname: "dc01-node02" >>>> Encap geneve >>>> ip: "X.X.X.X" >>>> options: {csum="true"} >>>> Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c" >>>> hostname: "dc02-node1" >>>> Encap geneve >>>> ip: "A.A.A.A" >>>> options: {csum="true"} >>>> >>>> >>>> The new node is not listed (dc01-node1). >>>> >>>> When executed on the nodes the same command (ovn-sbctl show) times-out >>>> on all nodes..... >>>> >>>> The output of the /var/log/openvswitch/ovn-conntroller.log lists on all >>>> logs >>>> >>>> 2020-09-11T08:46:55.197Z|07361|stream_ssl|WARN|SSL_connect: unexpected >>>> SSL connection close >>>> >>>> >>>> >>> Can you please compare the output of >>> >>> ovs-vsctl --no-wait get open . external-ids:ovn-remote >>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-type >>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-ip >>> >>> of the working hosts, e.g. dc01-node02, and the failing host dc01-node1? >>> This should point us the relevant difference in the configuration. >>> >>> Please include ovirt-users list in your replay, to share the knowledge >>> and experience with the community. >>> >>> >>> >>>> Thank you >>>> Best regards >>>> Konstantinos Betsis >>>> >>>> >>>> On Fri, Sep 11, 2020 at 11:01 AM Dominik Holler <dholler(a)redhat.com> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Thu, Sep 10, 2020 at 6:26 PM Konstantinos B <k.betsis(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Hi all >>>>>> >>>>>> We have a small installation based on OVIRT 4.3. >>>>>> 1 Cluster is based on Centos 7 and the other on OVIRT NG Node image. >>>>>> >>>>>> The environment was stable till an upgrade took place a couple of >>>>>> months ago. >>>>>> As such we had to re-install one of the Centos 7 node and start from >>>>>> scratch. >>>>>> >>>>> >>>>> To trigger the automatic configuration of the host, it is required to >>>>> configure ovirt-provider-ovn as the default network provider for the >>>>> cluster before adding the host to oVirt. >>>>> >>>>> >>>>>> Even though the installation completed successfully and VMs are >>>>>> created, the following are not working as expected: >>>>>> 1. ovn geneve tunnels are not established with the other Centos 7 >>>>>> node in the cluster. >>>>>> 2. Centos 7 node is configured by ovirt engine however no geneve >>>>>> tunnel is established when "ovn-sbctl show" is issued on the engine. >>>>>> >>>>> >>>>> Does "ovn-sbctl show" list the hosts? >>>>> >>>>> >>>>>> 3. no flows are shown on the engine on port 6642 for the ovs db. >>>>>> >>>>>> Does anyone have any experience on how to troubleshoot OVN on ovirt? >>>>>> >>>>>> >>>>> /var/log/openvswitch/ovncontroller.log on the host should contain a >>>>> helpful hint. >>>>> >>>>> >>>>> >>>>>> Thank you >>>>>> _______________________________________________ >>>>>> 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/LBVGLQJBWJF3E… >>>>>> >>>>>

3 30