- Users - oVirt List Archives

Q: Strange ping timeouts/network issues when 1 node is down
by Andrei Verovski 12 Jul '21

12 Jul '21

Hi, I have observed strange ping timeouts/network issues when one of nodes is down, for example, for RAM upgrade. Powering up and connecting node back solves this. Each node have 2 networks (connected to different Ethernet interfaces), ovirtmgmt 192.168.0.xxx and DMZ 192.168.1.x. Additionally, time consuming operations like VM cloning causes increase of ping latency to ALL nodes from local workstations. VM cloning should load only 1 node but it should not affect the whole ovirt mgmt network on all nodes. How to fix this issue? Thanks in advance for any help. Andrei

1 0

glusterfs health-check failed, (brick) going down
by Jiří Sléžka 11 Jul '21

11 Jul '21

Hello, I have 3 node HCI cluster with oVirt 4.4.6 and CentOS8. For time to time (I belive) random brick on random host goes down because health-check. It looks like [root@ovirt-hci02 ~]# grep "posix_health_check" /var/log/glusterfs/bricks/* /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07 07:13:37.408184] M [MSGID: 113075] [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix: health-check failed, going down /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07 07:13:37.408407] M [MSGID: 113075] [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still alive! -> SIGTERM /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07 16:11:14.518971] M [MSGID: 113075] [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix: health-check failed, going down /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07 16:11:14.519200] M [MSGID: 113075] [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still alive! -> SIGTERM on other host [root@ovirt-hci01 ~]# grep "posix_health_check" /var/log/glusterfs/bricks/* /var/log/glusterfs/bricks/gluster_bricks-engine-engine.log:[2021-07-05 13:15:51.983327] M [MSGID: 113075] [posix-helpers.c:2214:posix_health_check_thread_proc] 0-engine-posix: health-check failed, going down /var/log/glusterfs/bricks/gluster_bricks-engine-engine.log:[2021-07-05 13:15:51.983728] M [MSGID: 113075] [posix-helpers.c:2232:posix_health_check_thread_proc] 0-engine-posix: still alive! -> SIGTERM /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-05 01:53:35.769129] M [MSGID: 113075] [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix: health-check failed, going down /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-05 01:53:35.769819] M [MSGID: 113075] [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still alive! -> SIGTERM I cannot link these errors to any storage/fs issue (in dmesg or /var/log/messages), brick devices looks healthy (smartd). I can force start brick with gluster volume start vms|engine force and after some healing all works fine for few days Did anybody observe this behavior? vms volume has this structure (two bricks per host, each is separate JBOD ssd disk), engine volume has one brick on each host... gluster volume info vms Volume Name: vms Type: Distributed-Replicate Volume ID: 52032ec6-99d4-4210-8fb8-ffbd7a1e0bf7 Status: Started Snapshot Count: 0 Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: 10.0.4.11:/gluster_bricks/vms/vms Brick2: 10.0.4.13:/gluster_bricks/vms/vms Brick3: 10.0.4.12:/gluster_bricks/vms/vms Brick4: 10.0.4.11:/gluster_bricks/vms2/vms2 Brick5: 10.0.4.13:/gluster_bricks/vms2/vms2 Brick6: 10.0.4.12:/gluster_bricks/vms2/vms2 Options Reconfigured: cluster.granular-entry-heal: enable performance.stat-prefetch: off cluster.eager-lock: enable performance.io-cache: off performance.read-ahead: off performance.quick-read: off user.cifs: off network.ping-timeout: 30 network.remote-dio: off performance.strict-o-direct: on performance.low-prio-threads: 32 features.shard: on storage.owner-gid: 36 storage.owner-uid: 36 transport.address-family: inet storage.fips-mode-rchecksum: on nfs.disable: on performance.client-io-threads: off Cheers, Jiri

3 3

export VM from oVirt engine 3.5
by fddi＠comcast.net 11 Jul '21

11 Jul '21

Hello, I am trying to export a bunch o VM from oVirt version 3.5 The problem is that there is no OVA support for exporting them. I also tryed to export VMs into OVA format using ovirtsdk4 which anyway won't work on oVirt 3.5. I can successfully export to a NFS partition but for each VM there are several qcow v2 files which I suppose to be the VM image and its snapshots. How to identify the correct file to represent the current VM status ? If I delete all the snapshots, will I end up with only one valid qcow v2 image that I can use ?

3 2

passing data between guacamole and xrdp server
by Jason Keltz 10 Jul '21

10 Jul '21

Hi. I have a custom use case where I would like to have two guacamole RDP connections that point to the same host, but the underlying xrdp start script would initialize one connection slightly different than the other. I don't see a simple way that I can pass anything between Guacamole and the xrdp server which would allow the script to determine which connection the user chose in guac? I thought *maybe* "client name" under "Basic Settings" but it seems to apply to Windows only. It would be neat to be able to pass environment variables in. Thanks, Jason.

1 0

Gluster deploy error!
by Patrick Lomakin 10 Jul '21

10 Jul '21

Hello! I have tried to deploy single node vith gluster, but if select "Compression and dedublication" I get an error: TASK [gluster.infra/roles/backend_setup : Create thick logical volume] ********* failed: [host01********] (item={'vgname': 'gluster_vg_sda4', 'lvname': 'gluster_lv_engine', 'size': '1970G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " Volume group \"gluster_vg_sda4\" has insufficient free space (504319 extents): 504320 required.\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "1970G", "vgname": "gluster_vg_sda4"}, "msg": "Creating logical volume 'gluster_lv_engine' failed", "rc": 5}

2 1

change host IP
by radchenko.anatoliy＠gmail.com 10 Jul '21

10 Jul '21

Hi guys, what's the right way to change IP ( or FQDN ) on the host in replica 1 and 3 configuration? Thanks in advance. Best regards.

4 7

Re: Deployed self-hosted engine cannot be reached from network
by Fabrizio Vettore 09 Jul '21

09 Jul '21

[SOLVED] I installed a nested virtualization environment for testing, but I forgot to enable promiscuous mode on the VMware virtual switch. Unfortunately my brain was not correctly connected during configuration Sorry for wasting tour time :( Fabrizio Vettore ICT Manager --------------------------------------- Cifarelli Spa Strada Oriolo 180 27058 Voghera - Italy Lat. 45.006370 - Long. 9.010843

1 0

Deployed self-hosted engine cannot be reached from network
by fabrizio.vettore＠cifarelli.it 09 Jul '21

09 Jul '21

Hi, oVirt Node 4.4.7 i i have just deployed self hosted engine using supplied wizard. Install ended without any error. Now.engine can reach ovirtnode (and viceversa) but cannot reach/be reached by external network. During install node ens192.6 network adapter have been moved to a newly created bridge ovirtmgmt. Bridge routing have been correctly set. Actually ovirtnode can reach external networks (and internet) so I assume routing is OK for the node. I can login to ovirtengine via SSH from ovirtnode (but not from outside) and i can ping/reach the note from ovirtengine but nothing other, even on the some subnet (I have other 2 nodes instaled with adiacent addresses) Routing on the engine is OK (same gateway than node) Tried to redeploy with the same result. Probably it is a a stupid problem but I cannot figure out how to solve it! Any suggestion? Thanks in advance Fabrizio

2 1

Deployed self-hosted engine cannot be reached from network
by fabrizio.vettore＠cifarelli.it 09 Jul '21

09 Jul '21

Hi, oVirt Node 4.4.7 i i have just deployed self hosted engine using supplied wizard. Install ended without any error. Now.engine can reach ovirtnode (and viceversa) but cannot reach/be reached by external network. During install node ens192.6 network adapter have been moved to a newly created bridge ovirtmgmt. Bridge routing have been correctly set. Actually ovirtnode can reach external networks (and internet) so I assume routing is OK for the node. I can login to ovirtengine via SSH from ovirtnode (but not from outside) and i can ping/reach the note from ovirtengine but nothing other, even on the some subnet (I have other 2 nodes instaled with adiacent addresses) Routing on the engine is OK (same gateway than node) Tried to redeploy with the same result. Probably it is a a stupid problem but I cannot figure out how to solve it! Any suggestion? Thanks in advance Fabrizio

1 0

Multiple gateway not working after "big update"
by Lionel Caignec 09 Jul '21

09 Jul '21

Hi, i've just tried to update my sandboxing environmnent after long time without update (i know it's bad...) and i'm facing a problem with multiple gateway. This environment work with 6 hypervisors (centos 8) and one manager on dedicated server, all this baremetal have 2 interface in 2 différent network protected by firewall. All my hypervisords have 2 network for ovirt, one "ovirtmgmt" for management (only SSH and internal admin stuff), the other "ovir_prod" for console, migration, and default gateway. I've 3 hypervisors non updated which i can ping /ssh / ... (according to iptables) on the two interface without problem. But the 3 hypervisors just updated are accessible only on the "ovirt_prod" interface. I'm looking inside ip route/ ip rules it seems to miss something. I always configured my HV by ovirt gui so i does not understand what going wrong. This is ip route/ip rules of my hv, it's like missing ip rules on non working HV The "route-ovirt_prod" file that does not exist on old HV. Working HV (centos 8.3 / vdsm 4.20.26.3-1) : [root@drogo ~]# ip ru 0: from all lookup local 32000: from 10.100.126.0/24 lookup 174358038 32000: from all to 10.100.126.0/24 iif ovirtmgmt lookup 174358038 32000: from 10.5.7.0/24 lookup 168101654 32000: from all to 10.5.7.0/24 iif comte_prod lookup 168101654 32766: from all lookup main 32767: from all lookup default [root@drogo ~]# ip rou default via 10.5.7.254 dev comte_prod proto static metric 425 10.5.7.0/24 dev comte_prod proto kernel scope link src 10.5.7.22 metric 425 10.100.126.0/24 dev ovirtmgmt proto kernel scope link src 10.100.126.22 metric 426 Bugged HV (centos 8.4/ vdsm 4.40.70.6-1) [root@balbo ~]# ip ru 0: from all lookup local 32766: from all lookup main 32767: from all lookup default [root@balbo ~]# ip rou default via 10.5.7.254 dev comte_prod proto static metric 425 10.5.6.0/26 dev enp4s0f1 proto kernel scope link src 10.5.6.6 metric 100 linkdown 10.5.7.0/24 dev comte_prod proto kernel scope link src 10.5.7.25 metric 426 10.100.126.0/24 dev ovirtmgmt proto kernel scope link src 10.100.126.25 metric 425 [root@bingo network-scripts]# cat route-ovirt_prod ADDRESS0=0.0.0.0 NETMASK0=0.0.0.0 GATEWAY0=10.5.7.254 OPTIONS0="table 254" METRIC0=431 Than you for help :) -- Lionel Caignec

2 6