- Users - oVirt List Archives

ovirt AD issue
by Jason Keltz 04 Feb '21

04 Feb '21

A while back, I had reconfigured my oVirt engine to auth based on my Samba AD server, and everything was working perfectly fine. oVirt version 4.3.10.4-1. Today, I tried to login with my account into engine and I see: server_error: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(sun.security.validator.ValidatorException: No trusted certificate found), ldapSDKVersion=4.0.7, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58 I recently added a secondary domain controller with Samba, and I realize now that there is an error. Since I didn't pre-initialize samba with a TLS certificate, it generated a new CA, and certificate and key for the second server. Since I'm not using the same CA as the first server, ovirt engine (which only has the CA of the first server) won't be able to talk to the second server... no problem.... I will fix that eventually. However, when I re-ran "ovirt-engine-extension-aaa-ldap-setup", and followed the exact steps I did before, ovirt is connecting to the first server, failing with the above error, then connecting to the second server, and the same error. The CA hasn't changed for the first server, nor has the certificate/key. I verified that the CA certificate that I am giving ovirt is matching with the exact CA certificate of the first server. How can I debug further? Jason.

1 0

Recovery from power outage
by Roderick Mooi 04 Feb '21

04 Feb '21

Hi! We had a power outage and all our servers (oVirt hosts) went down. When they started up neither the hosted-engine nor VMs were started. hosted-engine --vm-status says: You must run deploy first I tried running deploy with various options but ultimately get stuck at: The Host ID is already known. Is this a re-deployment on an additional host that was previously set up (Yes, No)[Yes]? ... [ ERROR ] Failed to execute stage 'Closing up': <urlopen error [Errno 113] No route to host> OR The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? No [ ERROR ] Re-deploying the engine VM over a previously (partially) deployed system is not supported. Please clean up the storage device or select a different one and retry. NOTES: 1. This is oVirt v3.6 (legacy install, I know...) 2. We do have daily engine backups (.bak files) [till the day the power failed] Any advice/assistance appreciated. Thanks! Roderick

3 13

self hosted-engine deploy fails on network
by Nardus Geldenhuys 03 Feb '21

03 Feb '21

Hi oVirt land Hope you are well. Running into this issue, I hope you can help. Centos7 and it is updated. Ovirt 4.3, latest packages. My network config: [root@mob-r1-d-ovirt-aa-1-01 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff 3: ens1f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff 4: enp11s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:90:fa:c2:d2:50 brd ff:ff:ff:ff:ff:ff 5: enp11s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:90:fa:c2:d2:54 brd ff:ff:ff:ff:ff:ff 21: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff inet6 fe80::290:faff:fec2:d248/64 scope link valid_lft forever preferred_lft forever 22: bond0.1131@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff inet 172.18.206.184/23 brd 172.18.207.255 scope global bond0.1131 valid_lft forever preferred_lft forever inet6 fe80::290:faff:fec2:d248/64 scope link valid_lft forever preferred_lft forever [root@mob-r1-d-ovirt-aa-1-01 network-scripts]# cat ifcfg-bond0 BONDING_OPTS='mode=1 miimon=100' TYPE=Bond BONDING_MASTER=yes PROXY_METHOD=none BROWSER_ONLY=no IPV6INIT=no NAME=bond0 UUID=c11ef6ef-794f-4683-a068-d6338e5c19b6 DEVICE=bond0 ONBOOT=yes [root@mob-r1-d-ovirt-aa-1-01 network-scripts]# cat ifcfg-bond0.1131 DEVICE=bond0.1131 VLAN=yes ONBOOT=yes MTU=1500 IPADDR=172.18.206.184 NETMASK=255.255.254.0 GATEWAY=172.18.206.1 BOOTPROTO=none MTU=1500 DEFROUTE=yes NM_CONTROLLED=no IPV6INIT=yes DNS1=172.20.150.10 DNS2=172.20.150.11 I get the following error: [ INFO ] TASK [ovirt.hosted_engine_setup : Generate output list] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exists] [ INFO ] skipping: [localhost] Please indicate a nic to set ovirtmgmt bridge on: (bond0, bond0.1131) [bond0.1131]: Please specify which way the network connectivity should be checked (ping, dns, tcp, none) [dns]: .. .. .. .. .. [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exists] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The selected network interface is not valid"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up And if I create the ifcfg-ovirtmgmt as a bridge it fails later. What is the correct network setup for my bond configuration to do a self hosted-engine setup ? Regards Nar

2 1

Changes between Node NG 4.4.3 and 4.4.4
by Shantur Rathore 03 Feb '21

03 Feb '21

Hi, I have a node 4.4.3 install and it works perfectly for PCI passthrough. After I upgraded to Node NG 4.4.4 the PCI passthrough leads to server resets. There are no logs in the kernel messages just before reset apart from vfio-pci enabling the device. So, I assume there is some change related to the kernel or vfio-pci driver in the newer 4.4.4 version. How / Where can I see the differences between Node NG releases? Thanks, Shantur

1 1

Single Node 4.3 to 4.4 help
by Wesley Stewart 03 Feb '21

03 Feb '21

I have read through many posts and I think this process seems fairly simple. https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3 But I just wanted to see if anyone had any gotchas. I am thinking of either using - RHEL8 (Using developer program, probably best best atm) - Ovirt Node (Is ovirt node being deprecated since it is based on centos?) - Rocky Linux/AlmaLinux/Clear Linux From my understanding I should: - Enter global maintenance - Make a full engine backup - Reinstall to a supported OS - Deploy ovirt engine using backup. Looking forward to trying out Ovirt 4.4!

1 0

Ovirt VLAN Primer
by David Johnson 03 Feb '21

03 Feb '21

Good morning all, On my ovirt 4.4.4 cluster, I am trying to use VLan's to separate VM's for security purposes. Is there a usable how-to document that describes how to configure the vlan's so they actually function without taking the host into non-operational mode? Thank you in advance. Regards, David Johnson

3 13

NodeNG persistence for custom vdsm hooks and firmware
by Shantur Rathore 03 Feb '21

03 Feb '21

Hi all, I have NodeNG 4.4.4 installed and want to know what is the best way of persisting custom vdsm hooks and some firmware binaries across updates. I tried to update to 4.4.5-pre and lost my hooks and firmware. Thanks, Shantur

1 0

Storage domain problems. oVirt 4.4.4.
by Yury Valitsky 02 Feb '21

02 Feb '21

Hi, all. I deployed a new oVirt 4.4.4 installation and imported FC storage domains. However, two storage domains turned out to be empty - they did not have virtual machines in the "VM import" tab, the virtual disks appeared in the "disk import" tab with empty aliases. I downloaded and viewed the OVF_STORE - the old information was partially overwritten by the new one with an empty number of VMs. Trying to restore the VM configuration information, I deployed a backup of the old hosted engine. Version is also 4.4.4. Thus, it was possible to restore OVF_STORE of the first problematic disk domain. But the second storage domain gave an error when updating OVF_STORE. The same error occurs when trying to export a VM or copy a virtual disk to another known good storage domain. At the same time, I successfully download disks from the second storage domain to my PC by clicking the Download button and saving *.raw. But snapshots cannot be saved like this. 1. How can I overwrite OVF_STORE on the second storage domain? If for this I need to restore the oVirt metadata on the storage domain, how can I do it correctly? 2. How can I download VM configuration that has been saved in the hosted engine? Thanks in advance for your help. WBR, Yury Valitsky

1 1

ovirt 4.4 and CentOS 8 and multipath with Equallogic
by Gianluca Cecchi 02 Feb '21

02 Feb '21

Hello, I'm upgrading some environments from 4.3 to 4.4. Storage domains are iSCSI based, connected to an Equallogic storage array (PS-6510ES), that is recognized such as this as vendor/product in relation to multipath configuration # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: DELL Model: PERC H730 Mini Rev: 4.30 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi15 Channel: 00 Id: 00 Lun: 00 Vendor: EQLOGIC Model: 100E-00 Rev: 8.1 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi16 Channel: 00 Id: 00 Lun: 00 Vendor: EQLOGIC Model: 100E-00 Rev: 8.1 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi17 Channel: 00 Id: 00 Lun: 00 Vendor: EQLOGIC Model: 100E-00 Rev: 8.1 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi18 Channel: 00 Id: 00 Lun: 00 Vendor: EQLOGIC Model: 100E-00 Rev: 8.1 Type: Direct-Access ANSI SCSI revision: 05 # Passing from 4.3 to 4.4 implies passing from CentOS 7 to 8. The vendor is not in multipath "database" (it wasn't in 6 and 7 too) In 7 I used this snip to get no_path_retry set: # VDSM REVISION 1.5 # VDSM PRIVATE defaults { . . . no_path_retry 4 . . . } . . . devices { device { # These settings overrides built-in devices settings. It does # not apply to devices without built-in settings (these use the # settings in the "defaults" section), or to devices defined in # the "devices" section. all_devs yes no_path_retry 4 } device { vendor "EQLOGIC" product "100E-00" path_selector "round-robin 0" path_grouping_policy multibus path_checker tur rr_min_io_rq 10 rr_weight priorities failback immediate features "0" } } and confirmation of applied config with # multipath -l 36090a0c8d04f21111fc4251c7c08d0a3 dm-14 EQLOGIC ,100E-00 size=2.4T features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=0 status=active |- 16:0:0:0 sdc 8:32 active undef running `- 18:0:0:0 sde 8:64 active undef running 36090a0d88034667163b315f8c906b0ac dm-13 EQLOGIC ,100E-00 size=2.0T features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=0 status=active |- 15:0:0:0 sdb 8:16 active undef running `- 17:0:0:0 sdd 8:48 active undef running and # multipath -r -v3 | grep no_path_retry Jan 29 11:51:17 | 36090a0d88034667163b315f8c906b0ac: no_path_retry = 4 (config file default) Jan 29 11:51:17 | 36090a0c8d04f21111fc4251c7c08d0a3: no_path_retry = 4 (config file default) In 8 I get this; see also the strange line about vendor or product missing, but it is not true... # multipath -l Jan 29 11:52:02 | device config in /etc/multipath.conf missing vendor or product parameter 36090a0c8d04f21111fc4251c7c08d0a3 dm-13 EQLOGIC,100E-00 size=2.4T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='round-robin 0' prio=0 status=active |- 16:0:0:0 sdc 8:32 active undef running `- 18:0:0:0 sde 8:64 active undef running 36090a0d88034667163b315f8c906b0ac dm-12 EQLOGIC,100E-00 size=2.0T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='round-robin 0' prio=0 status=active |- 15:0:0:0 sdb 8:16 active undef running `- 17:0:0:0 sdd 8:48 active undef running # multipath -r -v3 | grep no_path_retry Jan 29 11:53:54 | device config in /etc/multipath.conf missing vendor or product parameter Jan 29 11:53:54 | set open fds limit to 8192/262144 Jan 29 11:53:54 | loading /lib64/multipath/libchecktur.so checker Jan 29 11:53:54 | checker tur: message table size = 3 Jan 29 11:53:54 | loading /lib64/multipath/libprioconst.so prioritizer Jan 29 11:53:54 | foreign library "nvme" loaded successfully Jan 29 11:53:54 | delegating command to multipathd So in my opinion it is currently using queue if no path in 8 Can anyone give me any insight about the message and about how to force the no_path_retry? Perhaps any major change in multipath from 7 to 8? The 8 config is this one: # VDSM REVISION 2.0 # VDSM PRIVATE defaults { . . . polling_interval 5 . . . # We use a small number of retries to protect from short outage. # Assuming the default polling_interval (5 seconds), this gives # extra 20 seconds grace time before failing the I/O. no_path_retry 16 . . . } # Blacklist internal disk blacklist { wwid "36d09466029914f0021e89c5710e256be" } # Remove devices entries when overrides section is available. devices { device { # These settings overrides built-in devices settings. It does # not apply to devices without built-in settings (these use the # settings in the "defaults" section), or to devices defined in # the "devices" section. #### Not valid any more in RH EL 8.3 #### all_devs yes #### no_path_retry 16 } device { vendor "EQLOGIC" product "100E-00" path_selector "round-robin 0" path_grouping_policy multibus path_checker tur rr_min_io_rq 10 rr_weight priorities failback immediate features "0" } } Thanks in advance, Gianluca

5 15

Mellanox SR-IOV
by Jorge Visentini 02 Feb '21

02 Feb '21

Hi. I have a Mellanox card with two ports and I enabled SR-IOV, however in Engine it shows only 1 of the ports with SR-IOV enabled. I shared it on the host through the CLI and shared it right but the VMs do not travel and the Engine shows that only one of the ports is divided. When I try to divide by the Engine, it shows the error of the attached print. Is this information correct or am I doing something wrong? [image: photo_2021-02-02_13-07-49.jpg] [image: photo_2021-02-02_12-37-56.jpg] [image: Screenshot_10.jpg] [image: Screenshot_11.jpg] -- Att, Jorge Visentini +55 55 98432-9868

1 0