- Users - oVirt List Archives

Re: issue connecting 4.3.8 node to nfs domain
by Jorick Astrego 09 Feb '20

09 Feb '20

On 2/6/20 1:44 PM, Amit Bawer wrote: > > > On Thu, Feb 6, 2020 at 1:07 PM Jorick Astrego <jorick(a)netbulae.eu > <mailto:jorick@netbulae.eu>> wrote: > > Here you go, this is from the activation I just did a couple of > minutes ago. > > I was hoping to see how it was first connected to host, but it doesn't > go that far back. Anyway, the storage domain type is set from engine > and vdsm never try to guess it as far as I saw. I put the host in maintenance and activated it again, this should give you some more info. See attached log. > Could you query the engine db about the misbehaving domain and paste > the results? > > # su - postgres > Last login: Thu Feb 6 07:17:52 EST 2020 on pts/0 > -bash-4.2$ LD_LIBRARY_PATH=/opt/rh/rh-postgresql10/root/lib64/ > /opt/rh/rh-postgresql10/root/usr/bin/psql engine > psql (10.6) > Type "help" for help. > engine=# select * from storage_domain_static where id = > 'f5d2f7c6-093f-46d6-a844-224d92db5ef9' ; engine=# select * from storage_domain_static where id = 'f5d2f7c6-093f-46d6-a844-224d92db5ef9' ; id | storage | storage_name | storage_domain_type | storage_type | storage_domain_format_type | _create_date | _update_date | recoverable | la st_time_used_as_master | storage_description | storage_comment | wipe_after_delete | warning_low_space_indicator | critical_space_action_blocker | first_metadata_device | vg_metadata_device | discard_after_delete | backup | warning_low_co nfirmed_space_indicator | block_size --------------------------------------+--------------------------------------+--------------+---------------------+--------------+----------------------------+-------------------------------+-----------------------------+-------------+--- -----------------------+---------------------+-----------------+-------------------+-----------------------------+-------------------------------+-----------------------+--------------------+----------------------+--------+--------------- ------------------------+------------ f5d2f7c6-093f-46d6-a844-224d92db5ef9 | b8b456f0-27c3-49b9-b5e9-9fa81fb3cdaa | backupnfs | 1 | 1 | 4 | 2018-01-19 13:31:25.899738+01 | 2019-02-14 14:36:22.3171+01 | t | 1530772724454 | | | f | 10 | 5 | | | f | f | 0 | 512 (1 row) Regards, Jorick > > On 2/6/20 11:23 AM, Amit Bawer wrote: >> >> >> On Thu, Feb 6, 2020 at 11:07 AM Jorick Astrego >> <jorick(a)netbulae.eu <mailto:jorick@netbulae.eu>> wrote: >> >> Hi, >> >> Something weird is going on with our ovirt node 4.3.8 install >> mounting a nfs share. >> >> We have a NFS domain for a couple of backup disks and we have >> a couple of 4.2 nodes connected to it. >> >> Now I'm adding a fresh cluster of 4.3.8 nodes and the >> backupnfs mount doesn't work. >> >> (annoying you cannot copy the text from the events view) >> >> The domain is up and working >> >> ID:f5d2f7c6-093f-46d6-a844-224d92db5ef9 >> Size:10238 GiB >> Available:2491 GiB >> Used:7747 GiB >> Allocated:3302 GiB >> Over Allocation Ratio:37% >> Images:7 >> Path:*.*.*.*:/data/ovirt >> NFS Version:AUTO >> Warning Low Space Indicator:10% (1023 GiB) >> Critical Space Action Blocker:5 GiB >> >> But somehow the node appears to thin thinks it's an LVM >> volume? It tries to find the VGs volume group but fails... >> which is not so strange as it is an NFS volume: >> >> >> Could you provide full vdsm.log file with this flow? >> >> >> 2020-02-05 14:17:54,190+0000 WARN (monitor/f5d2f7c) >> [storage.LVM] Reloading VGs failed >> (vgs=[u'f5d2f7c6-093f-46d6-a844-224d92db5ef9'] rc=5 >> out=[] err=[' Volume group >> "f5d2f7c6-093f-46d6-a844-224d92db5ef9" not found', ' >> Cannot process volume group >> f5d2f7c6-093f-46d6-a844-224d92db5ef9']) (lvm:470) >> 2020-02-05 14:17:54,201+0000 ERROR (monitor/f5d2f7c) >> [storage.Monitor] Setting up monitor for >> f5d2f7c6-093f-46d6-a844-224d92db5ef9 failed (monitor:330) >> Traceback (most recent call last): >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", >> line 327, in _setupLoop >> self._setupMonitor() >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", >> line 349, in _setupMonitor >> self._produceDomain() >> File "/usr/lib/python2.7/site-packages/vdsm/utils.py", >> line 159, in wrapper >> value = meth(self, *a, **kw) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", >> line 367, in _produceDomain >> self.domain = sdCache.produce(self.sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 110, in produce >> domain.getRealDomain() >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 51, in getRealDomain >> return self._cache._realProduce(self._sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 134, in _realProduce >> domain = self._findDomain(sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 151, in _findDomain >> return findMethod(sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 176, in _findUnfetchedDomain >> raise se.StorageDomainDoesNotExist(sdUUID) >> StorageDomainDoesNotExist: Storage domain does not exist: >> (u'f5d2f7c6-093f-46d6-a844-224d92db5ef9',) >> >> The volume is actually mounted fine on the node: >> >> On NFS server >> >> Feb 5 15:47:09 back1en rpc.mountd[4899]: authenticated >> mount request from *.*.*.*:673 for /data/ovirt (/data/ovirt) >> >> On the host >> >> mount|grep nfs >> >> *.*.*.*:/data/ovirt on >> /rhev/data-center/mnt/*.*.*.*:_data_ovirt type nfs >> (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,nolock,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=*.*.*.*,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=*.*.*.*) >> >> And I can see the files: >> >> ls -alrt /rhev/data-center/mnt/*.*.*.*:_data_ovirt >> total 4 >> drwxr-xr-x. 5 vdsm kvm 61 Oct 26 2016 >> 1ed0a635-67ee-4255-aad9-b70822350706 >> -rwxr-xr-x. 1 vdsm kvm 0 Feb 5 14:37 __DIRECT_IO_TEST__ >> drwxrwxrwx. 3 root root 86 Feb 5 14:37 . >> drwxr-xr-x. 5 vdsm kvm 4096 Feb 5 14:37 .. >> >> >> >> >> >> Met vriendelijke groet, With kind regards, >> >> Jorick Astrego >> * >> Netbulae Virtualization Experts * >> ------------------------------------------------------------------------ >> Tel: 053 20 30 270 info(a)netbulae.eu >> <mailto:info@netbulae.eu> Staalsteden 4-3A KvK 08198180 >> Fax: 053 20 30 271 www.netbulae.eu <http://www.netbulae.eu> >> 7547 TA Enschede BTW NL821234584B01 >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFTO5WBLVLGTV… >> > > > > > Met vriendelijke groet, With kind regards, > > Jorick Astrego > * > Netbulae Virtualization Experts * > ------------------------------------------------------------------------ > Tel: 053 20 30 270 info(a)netbulae.eu <mailto:info@netbulae.eu> > Staalsteden 4-3A KvK 08198180 > Fax: 053 20 30 271 www.netbulae.eu <http://www.netbulae.eu> 7547 > TA Enschede BTW NL821234584B01 > > > ------------------------------------------------------------------------ > Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------

2 4

Installing hosts w/o node installer
by Christian Reiss 08 Feb '20

08 Feb '20

Hey folks, quick question: If I would like to use specific versions (contained within the host) and craft myself a specific environment for the hosts am I correct to assume that only installing the ovirt repo and a gluster version of my choice (cough, 7.0) would suffice? Then adding the host via an engine (and taking the ususal steps as you would for an ovirt node: ssh keys et all)? To my understanding the rollout is done via ansible so packages will be installed if not present? The installation is pretty vague on this point (https://www.ovirt.org/download/) 1. Enable the Base, Optional, and Extra repositories 2. Install Cockpit and the cockpit-ovirt-dashboard plugin: 3. Enable Cockpit 4. Open the firewall 5. - 9. Deploy using a hosted engine. So, by using a remote engine (aka, like an additional host): 1. Enable the Base, Optional, and Extra repositories the end? I would use CentOS 7 as a base which I am very familiar with. I would also setup Gluster by hand so "Only" the virtualization part needs to be done. This would, among other things, grant me perfect host recovery options for a 1-host disaster case. We are looking at a base CentOS7 install without any deep modifications (except for some packages etc). Enjoy your weekend, all! :-) -Christian. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon christian(a)reiss.nrw \ / Campaign X against HTML XMPP chris(a)alpha-labs.net / \ in eMails WEB christian-reiss.de, reiss.nrw GPG Retrieval http://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

1 0

Re: Win Server 2k19 and BlueIris
by Robert Webb 08 Feb '20

08 Feb '20

FYI This also fixed the previous issues I was having with 2k19 servers that I was trying to migrate the disk image from Proxmox that was throwing the BSOD of KMODE EXCEPTION. From: Robert Webb <rwebb(a)ropeguru.com> Sent: Saturday, February 8, 2020 11:30 AM To: users <users(a)ovirt.org> Subject: [ovirt-users] Re: Win Server 2k19 and BlueIris Update: So after some digging, it seems this has been reported as an issue many times. As a workaround, I added the an entry to the kvm.conf in modprobe.d directory of ignore_msrs=1 and that allowed Blue Iris to boot. Would be nice to have an actual fix for this instead of a workaround. Would really like to know why kvm is thing that ia32_debugctl is not a valid cpu option. From: Robert Webb Sent: Saturday, February 8, 2020 10:33 AM To: users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: Win Server 2k19 and BlueIris So I have been running Windows Server 2019 on Proxmox VE with Blue Iris NVR. Tried to migrate the qcow disk over to oVirt, and like other Win2k19 servers, they all give a BSOD with a KMODE error. Last night I installed 2k19 from scratch, installed the latest drivers I could find, oVirt-toolsSetup-4.3-3.el7, and proceeded to load up Blue Iris. As soon as I go to start Blue Iris, the VM hangs, then gives a BSOD with SYSTEM SERVICE EXCEPTION. Looking at the debug log on the ovirt node the VM is running, there one entry that gets created on each crash with, "kvm [4723]: vcpu1 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop". Running on oVirt node 4.3.8, cluster cpu is Intel Westmere IBRS SSBD Family, pc-i440fx-rhel7.6.0, and the physical cpu is 24x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz. Any ideas?

1 0

Re: Win Server 2k19 and BlueIris
by Robert Webb 08 Feb '20

08 Feb '20

Update: So after some digging, it seems this has been reported as an issue many times. As a workaround, I added the an entry to the kvm.conf in modprobe.d directory of ignore_msrs=1 and that allowed Blue Iris to boot. Would be nice to have an actual fix for this instead of a workaround. Would really like to know why kvm is thing that ia32_debugctl is not a valid cpu option. From: Robert Webb Sent: Saturday, February 8, 2020 10:33 AM To: users <users(a)ovirt.org> Subject: Win Server 2k19 and BlueIris So I have been running Windows Server 2019 on Proxmox VE with Blue Iris NVR. Tried to migrate the qcow disk over to oVirt, and like other Win2k19 servers, they all give a BSOD with a KMODE error. Last night I installed 2k19 from scratch, installed the latest drivers I could find, oVirt-toolsSetup-4.3-3.el7, and proceeded to load up Blue Iris. As soon as I go to start Blue Iris, the VM hangs, then gives a BSOD with SYSTEM SERVICE EXCEPTION. Looking at the debug log on the ovirt node the VM is running, there one entry that gets created on each crash with, "kvm [4723]: vcpu1 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop". Running on oVirt node 4.3.8, cluster cpu is Intel Westmere IBRS SSBD Family, pc-i440fx-rhel7.6.0, and the physical cpu is 24x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz. Any ideas?

1 0

Win Server 2k19 and BlueIris
by Robert Webb 08 Feb '20

08 Feb '20

So I have been running Windows Server 2019 on Proxmox VE with Blue Iris NVR. Tried to migrate the qcow disk over to oVirt, and like other Win2k19 servers, they all give a BSOD with a KMODE error. Last night I installed 2k19 from scratch, installed the latest drivers I could find, oVirt-toolsSetup-4.3-3.el7, and proceeded to load up Blue Iris. As soon as I go to start Blue Iris, the VM hangs, then gives a BSOD with SYSTEM SERVICE EXCEPTION. Looking at the debug log on the ovirt node the VM is running, there one entry that gets created on each crash with, "kvm [4723]: vcpu1 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop". Running on oVirt node 4.3.8, cluster cpu is Intel Westmere IBRS SSBD Family, pc-i440fx-rhel7.6.0, and the physical cpu is 24x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz. Any ideas?

1 0

[ANN] oVirt 4.3.9 First Release Candidate is now available for testing
by Sandro Bonazzola 08 Feb '20

08 Feb '20

The oVirt Project is pleased to announce the availability of the oVirt 4.3.9 First Release Candidate for testing, as of January 30th, 2020. This update is a release candidate of the nineth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node will be available soon Additional Resources: * Read more about the oVirt 4.3.9 release highlights: http://www.ovirt.org/release/4.3.9/ * 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.3.9/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

VM not getting up
by Crazy Ayansh 08 Feb '20

08 Feb '20

[image: image.png] disk is already attached, All vm on the same server giving same error. Help please.

4 8

3 Node Hyperconverged Install fails with - Error: the target storage domain contains only 46.0GiB of available space while a minimum of 61.0Gi
by Dirk Rydvan 07 Feb '20

07 Feb '20

Hello ovirts, I try to create a 3 Node hyperconverged cluster with the cockpit GUI, but ist fails at last step "5" in Hosted engine setup [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error: the target storage domain contains only 46.0GiB of available space while a minimum of 61.0GiB is required If you wish to use the current target storage domain by extending it, make sure it contains nothing before adding it."} I checked the volumes at all 3 nodes - only node1 shows a mount - node2 and node3 not [root@node1 ~]# df -h Filesystem Size Used Avail Use% Mounted on <snip> node43.infra.qivicon.de:/engine 52G 3.0G 47G 7% /rhev/data-center/mnt/glusterSD/node43.infra.qivicon.de:_engine /dev/mapper/gluster_vg_nvme0n1-gluster_lv_data 500G 34M 500G 1% /gluster_bricks/data /dev/mapper/gluster_vg_nvme0n1-gluster_lv_engine 100G 33M 100G 1% /gluster_bricks/engine /dev/mapper/gluster_vg_nvme0n1-gluster_lv_vmstore 500G 33M 500G 1% /gluster_bricks/vmstore I created the gluster before with: Hosts: node1 node2 node3 Default Gluster values plus cache /gluster_bricks/engine 100GB /dev/nvme0n1 (Arbiter unchecked) /gluster_bricks/data 500GB /dev/nvme0n1 (Arbiter unchecked) /gluster_bricks/vmstore 500GB /dev/nvme0n1 (Arbiter unchecked) cache /dev/nvme1n1 10GB writeback The allredy existing thread does not help: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/W2CM74EU6KPPJ2… Any idea where the problem is? many Thanks in advance

2 1

Re: [Gluster-users] ACL issue v6.6, v6.7, v7.1, v7.2
by Paolo Margara 07 Feb '20

07 Feb '20

Hi, this is interesting, this happen always with gluster 6.6 or only in certain cases? I ask this because I have two ovirt clusters with gluster, both with gluster v6.6, in one case I've upgraded from 6.5 to 6.6 as Strahil, and I haven't hit this bug. When upgrading my clusters I follow exactly the steps reported by Strahil in the bug report, some other things should be different. Greetings, Paolo Il 06/02/20 23:30, Christian Reiss ha scritto: > Hey, > > I hit this bug, too. With disastrous results. > I second this post. > > > On 06.02.2020 19:59, Strahil Nikolov wrote: >> Hello List, >> >> Recently I had upgraded my oVirt + Gluster (v6.5 -> v6.6) and I hit >> an ACL bug , which forced me to upgrade to v7.0 >> >> Another oVirt user also hit the bug when upgrading to v6.7 and he >> had to rebuild his gluster cluster. >> >> Sadly, the fun doesn't stop here. Last week I have tried upgrading >> to v7.2 and again the ACL bug hit me. Downgrading to v7.1 doesn't >> help - so I downgraded to 7.0 and everything is operational. >> >> The bug report for the last issue: >> https://bugzilla.redhat.com/show_bug.cgi?id=1797099 >> >> I have 2 questions : >> 1. What is gluster's ACL evaluating/checking ? Is there an option to >> force gluster not to support ACL at all ? >> >> 2. Are you aware of the issue? That bug was supposed to be fixed a >> long time ago, yet the facts speak different. >> >> Thanks for reading this long post. >> >> Best Regards, >> Strahil Nikolov >> ________ >> >> Community Meeting Calendar: >> >> APAC Schedule - >> Every 2nd and 4th Tuesday at 11:30 AM IST >> Bridge: https://bluejeans.com/441850968 >> >> NA/EMEA Schedule - >> Every 1st and 3rd Tuesday at 01:00 PM EDT >> Bridge: https://bluejeans.com/441850968 >> >> Gluster-users mailing list >> Gluster-users(a)gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users

3 3

OVN issues: no connectivity between VMs on same host
by thkam＠hua.gr 07 Feb '20

07 Feb '20

Hi I am getting some problems setting up an internal networks for our oVirt VMs using the OVN external provider. The ovn-provider was setup during the ovirt engine installation (version 4.3.7.2-1.el7). I then just created a new network with the ovn external provider and tested the connectivity using the corresponding button on the oVirt UI. Two of my VMs are Ubuntu 18.04 servers with ips 10.0.0.101 and 10.0.0.102 with gateways 10.0.0.102 and 10.0.0.101 respectively. So I guess under normal circumstances they should be able to ping each other. I tried disabling the firewalld service on both the host and the ovirtengine but still nothing changed. However I noticed something odd on the firewalld status on the host. With firewalld enabled, I get: [root@ovirt7 ~]# systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled) Active: active (running) since Πεμ 2020-02-06 06:10:38 UTC; 14s ago Docs: man:firewalld(1) Main PID: 4436 (firewalld) Tasks: 2 CGroup: /system.slice/firewalld.service └─4436 /usr/bin/python2 -Es /usr/sbin/firewalld --nofork --nopid Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet1 -j libvirt-O-vnet1' failed: Illegal target name 'libvirt-O-vnet1'. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -F libvirt-I-vnet1' failed: Chain 'libvirt-I-vnet1' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -X libvirt-I-vnet1' failed: Chain 'libvirt-I-vnet1' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -F libvirt-O-vnet1' failed: Chain 'libvirt-O-vnet1' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -X libvirt-O-vnet1' failed: Chain 'libvirt-O-vnet1' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -E libvirt-P-vnet1 libvirt-O-vnet1' failed: Chain 'libvirt-P-vnet1' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -F I-vnet1-mac' failed: Chain 'I-vnet1-mac' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -X I-vnet1-mac' failed: Chain 'I-vnet1-mac' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -F I-vnet1-arp-mac' failed: Chain 'I-vnet1-arp-mac' doesn't exist. Φεβ 06 06:10:39 ovirt7.hua.gr firewalld[4436]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -X I-vnet1-arp-mac' failed: Chain 'I-vnet1-arp-mac' doesn't exist. On the ovirt engine I have: [root@ovirtengine ~]# ovn-sbctl show Chassis "0e225912-6318-4bc3-9c94-8f2ab937876d" hostname: "ovirt3.hua.gr" Encap geneve ip: "10.100.59.53" options: {csum="true"} Chassis "47ff3058-effb-43c2-b9e0-9eaf6c72b1c2" hostname: "ovirt5.hua.gr" Encap geneve ip: "10.100.59.51" options: {csum="true"} Chassis "1fcca34f-6017-4882-8c13-4835dad03387" hostname: localhost Encap geneve ip: "10.100.59.55" options: {csum="true"} Chassis "25d35968-6c3c-4040-ab85-d881d3d524e4" hostname: "ovirt4.hua.gr" Encap geneve ip: "10.100.59.52" options: {csum="true"} Chassis "32697bcc-cc6a-4a59-8424-887d20df2d10" hostname: "ovirt7.hua.gr" Encap geneve ip: "10.100.59.49" options: {csum="true"} Port_Binding "ff31a88f-23f0-48fe-a657-3cd24d51f69e" Port_Binding "01da6ee3-abff-4423-954a-c4abf350e390" Port_Binding "caa870e1-8b6c-48bd-ac61-bfeda8befd10" Chassis "f60100e6-0ee5-4472-8095-cc48b5160f50" hostname: "ovirt6.hua.gr" Encap geneve ip: "10.100.59.50" options: {csum="true"} Chassis "fa7e6cbe-fa7f-46bc-9760-f581725f60a8" hostname: "ovirt2.hua.gr" Encap geneve ip: "10.100.59.54" options: {csum="true"} Chassis "58a9412f-bfad-4c98-9882-d7d006588e0b" hostname: "ovirt9.hua.gr" Encap geneve ip: "10.100.59.47" options: {csum="true"} Chassis "09dc1148-8ce5-425d-8f93-8dbf43fd7828" hostname: "ovirt8.hua.gr" Encap geneve ip: "10.100.59.48" options: {csum="true"} so I guess tunneling is correctly setup right. On the host I am seeing: [root@ovirt7 ~]# ovs-vsctl show 886fe6e5-13ea-4889-ba35-1ac0a422ca23 Bridge br-int fail_mode: secure Port "ovn-1fcca3-0" Interface "ovn-1fcca3-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.55"} Port "ovn-0e2259-0" Interface "ovn-0e2259-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.53"} Port "ovn-fa7e6c-0" Interface "ovn-fa7e6c-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.54"} Port "vnet3" Interface "vnet3" Port "vnet0" Interface "vnet0" Port "ovn-25d359-0" Interface "ovn-25d359-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.52"} Port br-int Interface br-int type: internal Port "ovn-f60100-0" Interface "ovn-f60100-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.50"} Port "ovn-47ff30-0" Interface "ovn-47ff30-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.51"} Port "ovn-58a941-0" Interface "ovn-58a941-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.47"} Port "vnet2" Interface "vnet2" Port "ovn-09dc11-0" Interface "ovn-09dc11-0" type: geneve options: {csum="true", key=flow, remote_ip="10.100.59.48"} ovs_version: "2.11.0" and: [root@ovirt7 ~]# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master trunk state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:32 brd ff:ff:ff:ff:ff:ff 19: eno1.59@eno1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovirtmgmt state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 20: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 2a:92:56:8b:36:b8 brd ff:ff:ff:ff:ff:ff 21: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether c6:70:c8:34:86:85 brd ff:ff:ff:ff:ff:ff 23: br-int: <BROADCAST,MULTICAST> mtu 1442 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether da:49:e1:b0:b2:4e brd ff:ff:ff:ff:ff:ff 25: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 26: eno1.60@eno1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue master vlan60 state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 27: vlan60: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 28: eno1.61@eno1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue master vlan61 state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 29: vlan61: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 30: trunk: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:17:a4:77:00:30 brd ff:ff:ff:ff:ff:ff 39: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc mq master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:6f:2b:f7:00:17 brd ff:ff:ff:ff:ff:ff 40: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc mq master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:6f:2b:f7:00:18 brd ff:ff:ff:ff:ff:ff 41: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:6f:2b:f7:00:0f brd ff:ff:ff:ff:ff:ff 42: vnet3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc mq master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:6f:2b:f7:00:16 brd ff:ff:ff:ff:ff:ff 44: genev_sys_6081: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 06:6c:84:05:bf:6b brd ff:ff:ff:ff:ff:ff I have not found anything useful in the log files. Does anyone have any thoughts? Thanks! Thomas

1 1