- Users - oVirt List Archives

Upgrade from 4.2 directly to 4.5
by Vinícius Ferrão 11 Jul '22

11 Jul '22

Hello, I would like to know if I can do an oVirt upgrade directly from 4.2 to 4.5. I don’t have a free host to upgrade the oVirt Node, so I was hoping that would be possible to fire up a new engine (with restore-backup) on the old oVirt Nodes and later on upgrade the hosts. Is this possible? Thank you.

2 5

gluster service on the cluster is unchecked on hci cluster
by Jiří Sléžka 11 Jul '22

11 Jul '22

Hi, I would like to change CPU Type in my oVirt 4.4.10 HCI cluster (based on 3 glusterfs/virt hosts). When I try to I got this error Error while executing action: Cannot disable gluster service on the cluster as it contains volumes. As I remember I had Gluster Service enabled on this cluster but now both (Enable Virt Services and Enable Gluster Service) checkboxes are grayed out and Gluster Service is unchecked. Also Storage / Volumes displays my volumes... well, displays one brick on particular host in unknown state (? mark) which is new situation. As I can see from command line all bricks are online, no healing in progress, all looks good... I am not sure if the second issue is relevant to first one so main question is how can I (re)enable gluster service in my cluster? Thanks in advance, Jiri

1 0

VM access to infiniband network
by Roberto Bertucci 09 Jul '22

09 Jul '22

Hi all, i am facing a problem while trying to associate a Mellanox infiniband interface to a network and using it for VM traffic. vdsm log shows the following message: The bridge <bridge name> cannot use IP over InfiniBand interface <interface name> as port. Please use RoCE interface instead. Did anybody face the same problem and solve it? Actually ib interface is configured with an ip address and we are mounting NFS filesystems on cluster nodes through infiniband network.

2 4

How to set static IP when creating VM?
by msjang＠kisti.re.kr 08 Jul '22

08 Jul '22

Hi, all. I've used cockpit-machine, qemu-kvm for 2 years for my services, and I tried to use ovirt for a month. I've use virt-edit to configure ifcfg-eth0 for static IP as my company does not allow DHCP. I've use virt-customize to set default root password. How can I set static IP and root password when creating VM? Currently, I use virt-edit, virt-customize after I set saslpasswd2 on image files of oVirt, and it seems not best practice. Best Regards. Minseok Jang

2 1

can't get vm ipv4 address via api
by coolloves＠gmail.com 08 Jul '22

08 Jul '22

i am using 4.4.10 . if i login to ovirt manager website,i can see vm's ip info, nic1 网络名称 vlan11 IPv4 192.168.11.238 IPv6 fe80::8b0d:288f:bbb:3c19 MAC 56:6f:4e:14:00:00 while run the command,i could get lot of infos about vm,for example below,but i can't find vm's ipaddress.please help me.thanks! curl -k -H "Accept: application/json" -H "Authorization: xxxxxxxxxxxxxx" https://enginexxxxx.com/ovirt-engine/api/vms { "guest_operating_system": { "architecture": "x86_64", "codename": "", "distribution": "CentOS Linux", "family": "Linux", "kernel": { "version": { "build": "0", "full_version": "3.10.0-862.el7.x86_64", "major": "3", "minor": "10", "revision": "862" } }, "version": { "full_version": "7", "major": "7" } }, "guest_time_zone": { "name": "CST", "utc_offset": "+08:00" }, "next_run_configuration_exists": "false", "run_once": "false", "start_time": 1656494158035, "status": "up", "stop_time": 1656493463353, "host": { "href": "/ovirt-engine/api/hosts/7ba743ab-5cbc-4472-ab6c-b95be8eed569", "id": "7ba743ab-5cbc-4472-ab6c-b95be8eed569" }, "original_template": { "href": "/ovirt-engine/api/templates/2c70e56e-80e2-41fb-8fce-5cdaf71935d6", "id": "2c70e56e-80e2-41fb-8fce-5cdaf71935d6" }, "template": { "href": "/ovirt-engine/api/templates/00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000" }, "actions": { "link": [{ "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/shutdown", "rel": "shutdown" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/start", "rel": "start" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/stop", "rel": "stop" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/suspend", "rel": "suspend" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/reset", "rel": "reset" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/detach", "rel": "detach" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/ticket", "rel": "ticket" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/cancelmigration", "rel": "cancelmigration" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/commitsnapshot", "rel": "commitsnapshot" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/clone", "rel": "clone" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/freezefilesystems", "rel": "freezefilesystems" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/logon", "rel": "logon" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/maintenance", "rel": "maintenance" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/previewsnapshot", "rel": "previewsnapshot" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/autopincpuandnumanodes", "rel": "autopincpuandnumanodes" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/reboot", "rel": "reboot" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/migrate", "rel": "migrate" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/reordermacaddresses", "rel": "reordermacaddresses" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/thawfilesystems", "rel": "thawfilesystems" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/undosnapshot", "rel": "undosnapshot" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/export", "rel": "export" }] }, "name": "centos-test2", "description": "", "comment": "", "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0", "id": "18f940ef-e74c-4c45-b8c8-042945e530d0", "bios": { "boot_menu": { "enabled": "false" }, "type": "q35_sea_bios" }, "cpu": { "architecture": "x86_64", "topology": { "cores": "1", "sockets": "8", "threads": "1" } }, "display": { "address": "192.168.13.191", "allow_override": "false", "certificate": { "content": "-----BEGIN CERTIFICATE-----\nxxxx\n-----END CERTIFICATE-----\n", "organization": "ejy365.com", "subject": "O=ejy365.com,CN=192.168.13.191" }, "copy_paste_enabled": "true", "disconnect_action": "LOCK_SCREEN", "file_transfer_enabled": "true", "monitors": "1", "port": "5900", "secure_port": "5901", "smartcard_enabled": "false", "type": "spice" }, "io": { "threads": "1" }, "memory": "17179869184", "migration": { "auto_converge": "inherit", "compressed": "inherit", "encrypted": "inherit" }, "origin": "ovirt", "os": { "boot": { "devices": { "device": ["hd"] } }, "type": "rhel_7x64" }, "sso": { "methods": { "method": [{ "id": "guest_agent" }] } }, "stateless": "false", "type": "server", "usb": { "enabled": "false" }, "cluster": { "href": "/ovirt-engine/api/clusters/9fd83c65-adbf-483d-b6cc-2b5aec4d17f1", "id": "9fd83c65-adbf-483d-b6cc-2b5aec4d17f1" }, "link": [{ "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/katelloerrata", "rel": "katelloerrata" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/permissions", "rel": "permissions" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/tags", "rel": "tags" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/affinitylabels", "rel": "affinitylabels" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/graphicsconsoles", "rel": "graphicsconsoles" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/cdroms", "rel": "cdroms" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/nics", "rel": "nics" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/watchdogs", "rel": "watchdogs" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/snapshots", "rel": "snapshots" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/applications", "rel": "applications" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/hostdevices", "rel": "hostdevices" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/numanodes", "rel": "numanodes" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/reporteddevices", "rel": "reporteddevices" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/sessions", "rel": "sessions" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/backups", "rel": "backups" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/checkpoints", "rel": "checkpoints" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/diskattachments", "rel": "diskattachments" }, { "href": "/ovirt-engine/api/vms/18f940ef-e74c-4c45-b8c8-042945e530d0/statistics", "rel": "statistics" }], "cpu_shares": "0", "creation_time": 1656466718984, "delete_protected": "false", "high_availability": { "enabled": "false", "priority": "1" }, "large_icon": { "href": "/ovirt-engine/api/icons/3cc4f676-4aea-48b5-bfe9-b1b8db5585e3", "id": "3cc4f676-4aea-48b5-bfe9-b1b8db5585e3" }, "memory_policy": { "ballooning": "true", "guaranteed": "11452547072", "max": "68719476736" }, "migration_downtime": "-1", "multi_queues_enabled": "true", "placement_policy": { "affinity": "pinned" }, "serial_number": { "policy": "host" }, "small_icon": { "href": "/ovirt-engine/api/icons/8bcef820-00d7-4845-b73f-57516e06afd2", "id": "8bcef820-00d7-4845-b73f-57516e06afd2" }, "start_paused": "false", "storage_error_resume_behaviour": "kill", "time_zone": { "name": "Asia/Shanghai" }, "virtio_scsi_multi_queues_enabled": "false", "cpu_profile": { "href": "/ovirt-engine/api/cpuprofiles/50250d96-e65f-415a-9af1-5c59fbf5d474", "id": "50250d96-e65f-415a-9af1-5c59fbf5d474" } }

2 3

cluster compatibility version 4.7
by Staniforth, Paul 07 Jul '22

07 Jul '22

Hello When we try to complete the upgrade to 4.5.1 there is a failure to upgrade the cluster to compatibly version 4.7 Cannot update compatibility version of Vm/Template: [HostedEngine], Message: There was an attempt to change Hosted Engine VM values that are locked. Also somehow the cluster had changed to Cluster Node Type of Virt only but there was an error due to started volumes when trying to change the Cluster from the WebUI. I fixed this by changing it in the DB. Thanks, Paul S. To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

1 0

virtio-net name enp1s0 and not expected ens3
by Ladislav Humenik 07 Jul '22

07 Jul '22

Hallo, looking for some hint where one can change the guest network name (not with udev rules) but rather is there somewhere a code in ovirt/libvirt? We have one from scratch installed ovirt engine (4.4.10.4-1.el8), where all guests have enp*s* network name, all others engines (like 13 upgraded recently from 4.3.10 to 4.4.10) have ens* network name. In redhat KB https://access.redhat.com/solutions/3709641 is explained how is the naming of virtio-net working What is also different, there is missing ID_NET_NAME_SLOT in udevadm output: ~]$ udevadm info /sys/class/net/enp1s0/ P: /devices/pci0000:00/0000:00:02.0/0000:01:00.0/virtio0/net/enp1s0 E: DEVPATH=/devices/pci0000:00/0000:00:02.0/0000:01:00.0/virtio0/net/enp1s0 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1041 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=enp1s0 E: ID_NET_NAME_MAC=enx001a4a08000e E: ID_NET_NAME_PATH=enp1s0 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-0000:01:00.0 E: ID_PATH_TAG=pci-0000_01_00_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=enp1s0 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp1s0 E: TAGS=:systemd: E: USEC_INITIALIZED=3826556 Expected output of udeavm would be: ~]$ udevadm info /sys/class/net/ens3 P: /devices/pci0000:00/0000:00:03.0/virtio0/net/ens3 E: DEVPATH=/devices/pci0000:00/0000:00:03.0/virtio0/net/ens3 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1000 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=ens3 E: ID_NET_NAME_MAC=enx001a4a070167 E: ID_NET_NAME_PATH=enp0s3 E: ID_NET_NAME_SLOT=ens3 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-0000:00:03.0 E: ID_PATH_TAG=pci-0000_00_03_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=ens3 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens3 E: TAGS=:systemd: E: USEC_INITIALIZED=3487875 Tested with different OSes like centos/debian, always the same output. -- Ladislav Humenik

1 0

virtio-net name enp1s0 and not expected ens3
by Ladislav Humenik 07 Jul '22

07 Jul '22

Hallo, looking for some hint where one can change the guest network name (not with udev rules) but rather is there somewhere a code in ovirt/libvirt? We have one from scratch installed ovirt engine (4.4.10.4-1.el8), where all guests have enp*s* network name, all others engines (like 13 upgraded recently from 4.3.10 to 4.4.10) have ens* network name. In redhat KB https://access.redhat.com/solutions/3709641 is explained how is the naming of virtio-net working What is also different, there is missing ID_NET_NAME_SLOT in udevadm output: ~]$ udevadm info /sys/class/net/enp1s0/ P: /devices/pci0000:00/0000:00:02.0/0000:01:00.0/virtio0/net/enp1s0 E: DEVPATH=/devices/pci0000:00/0000:00:02.0/0000:01:00.0/virtio0/net/enp1s0 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1041 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=enp1s0 E: ID_NET_NAME_MAC=enx001a4a08000e E: ID_NET_NAME_PATH=enp1s0 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-0000:01:00.0 E: ID_PATH_TAG=pci-0000_01_00_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=enp1s0 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp1s0 E: TAGS=:systemd: E: USEC_INITIALIZED=3826556 Expected output of udeavm would be: ~]$ udevadm info /sys/class/net/ens3 P: /devices/pci0000:00/0000:00:03.0/virtio0/net/ens3 E: DEVPATH=/devices/pci0000:00/0000:00:03.0/virtio0/net/ens3 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1000 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=ens3 E: ID_NET_NAME_MAC=enx001a4a070167 E: ID_NET_NAME_PATH=enp0s3 E: ID_NET_NAME_SLOT=ens3 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-0000:00:03.0 E: ID_PATH_TAG=pci-0000_00_03_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=ens3 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens3 E: TAGS=:systemd: E: USEC_INITIALIZED=3487875 Tested with different OSes like centos/debian, always the same output. -- Ladislav Humenik Systemadministrator / VI IT Operations Hosting Infrastructure IONOS SE | Hinterm Hauptbahnhof 5 | 76137 Karlsruhe | Deutschland

1 0

Error after restoring hosted-engine
by Roberto Bertucci 07 Jul '22

07 Jul '22

Hello, after restoring hosted-engine from a backup, i have several problems. Let's start with the first, other threads for others... I can't see hosted-engine vm in vm list. Looking at engine log, i see the following: 2022-07-05 16:51:26,330+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-49) [4c8e10ac] null architecture type, replacing with x86_64, VM [HostedEngine] 2022-07-05 16:51:26,332+02 INFO [org.ovirt.engine.core.bll.HostedEngineImporter] (EE-ManagedThreadFactory-engine-Thread-4932) [4c8e10ac] Try to import the Hosted Engine VM 'VM [HostedEngine]' 2022-07-05 16:51:26,334+02 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Lock Acquired to object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_NAME, 4daba166-3da4-4220-8a56-5ddadf83015d=VM]', sharedLocks='[4daba166-3da4-4220-8a56-5ddadf83015d=REMOTE_VM]'}' 2022-07-05 16:51:26,335+02 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Error during ValidateFailure.: java.lang.NullPointerException at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.validator.VmValidator.isBiosTypeSupported(VmValidator.java:467) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ImportVmCommandBase.validate(ImportVmCommandBase.java:158) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ImportVmCommand.validate(ImportVmCommand.java:220) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.internalValidateInTransaction(CommandBase.java:824) at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:140) at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:157) ........ ........ 2022-07-05 16:51:26,335+02 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Lock freed to object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_NAME, 4daba166-3da4-4220-8a56-5ddadf83015d=VM]', sharedLocks='[4daba166-3da4-4220-8a56-5ddadf83015d=REMOTE_VM]'}' 2022-07-05 16:51:26,335+02 ERROR [org.ovirt.engine.core.bll.HostedEngineImporter] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Failed importing the Hosted Engine VM Is there any way to solve this issue? Web management interface is working except for the fact that i can't add new nodes and forget a storage domain which is no more existent. Thank you, Roberto

2 3

4.5.1 hyperconverged install failure "No valid network interface has been found"
by Dax Kelson 07 Jul '22

07 Jul '22

TL;DR hyperconverged install. Gluster install works, hosted engine fails with "no valid network interface has ben found" I have a three node hyperconverged cluster that had previously been running oVirt 4.4 successfully. A fully wipe and clean install of 4.5.1 was attempted with: ovirt-node-ng-installer-4.5.1-2022062306.el8.iso On each node, there are two statically configured 10Gb ethernet interfaces (and some unused 1Gb interfaces) enp5s0f0 - ovirt management/VM network (default gateway is on this network) enp5s0f1 - gluster network (isolated network) Name resolution is done via /etc/hosts on each node: 100.64.0.7 node1-ovirt node1-ovirt.local 100.64.0.8 node2-ovirt node2-ovirt.local 100.64.0.9 node3-ovirt node3-ovirt.local 100.79.192.1 node1-ovirt-storage node1-ovirt-storage.local 100.79.192.2 node2-ovirt-storage node2-ovirt-storage.local 100.79.192.3 node3-ovirt-storage node3-ovirt-storage.local Attempting to install the hosted engine fails with: *System data could not be retrieved!* *No valid network interface has been found* *If you are using Bonds or VLANs Use the following naming conventions:* - VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128, enp3s0.50) - Bond interfaces: bond*number* (for example, bond0, bond1) - VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50, bond1.128) * Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad * Networking teaming is not supported and will cause errors Here is the network setup on node1: [root@node1-ovirt ovirt]# ip -4 addr ls 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 6: enp5s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 inet 100.64.0.7/20 brd 100.64.15.255 scope global noprefixroute enp5s0f0 valid_lft forever preferred_lft forever 7: enp5s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 inet 100.79.192.1/24 brd 100.79.192.255 scope global noprefixroute enp5s0f1 valid_lft forever preferred_lft forever 8: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever [root@node1-ovirt ovirt]# My troubleshooting is that the failure is /probably/ coming from this file, but I'm not sure why: /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml Help? Thanks! Dax Kelson

1 1