HCI Deployment oVirt 4.5
Hello oVirt Team I'm in the process of deploying a three-node oVirt hyperconverged platform and from the cockpit interface of the deployment node I keep running into the same error. The system finishes the gluster deployment phase (sometimes) and then prompts to continue with the hosted engine deployment but then fails immediately complaining about the naming convention of my network interfaces. My network interfaces are 802.3ad bonds configured during the installation process of each node using "bondx" naming convention consistent across all three nodes. Any wisdom or pointers would be appreciated.
"No valid network interface has been found If you are using Bonds or VLANs Use the following naming conventions: " However I am using a supported naming convention. I've searched the forums and the general WWW and read the articles that match my errors. i've tried some of the options that are referenced in the articles but still no forward motion. Is this a common problem that somebody else has already solved and I just am not finding it on the web ?
On Tue, Jun 28, 2022 at 5:50 PM Clint Boggio <clint.boggio@gmail.com> wrote:
"No valid network interface has been found If you are using Bonds or VLANs Use the following naming conventions: "
However I am using a supported naming convention. I've searched the forums and the general WWW and read the articles that match my errors. i've tried some of the options that are referenced in the articles but still no forward motion.
Is this a common problem that somebody else has already solved and I just am not finding it on the web ?
Did you use classic bonding and not teaming, correct? What output from the "ip a" command? And "nmcli con show" command? Also, if I remember correctly, the graphical workflow is not supported, at least in the downstream product, RHV, for HCI deployment; possibly not so tested in upstream oVirt too? In fact at the landing page for RHV 4.4 (comprising 4.4-SP1, that matches somehow oVirt 4.5.x): https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4 there is only the command line based document for self-hosted engine deployment Gianluca
I did use classic bonding and not teaming. I'm trying to install hyperconverged three node oVirt cluster with self hosted engine. I've done it before in the 4.3 world but not in the 4.4 or 4.5 world. I'm using the cockpit method for deploying the cluster from the first node from the documentation. Should I reload the nodes and create the bonds from the nmcli command line instead of from the installation gui ? output from 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: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000 link/ether e4:43:4b:61:a9:b0 brd ff:ff:ff:ff:ff:ff 3: ens3f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether a0:36:9f:b8:97:9c brd ff:ff:ff:ff:ff:ff 4: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000 link/ether e4:43:4b:61:a9:b0 brd ff:ff:ff:ff:ff:ff permaddr e4:43:4b:61:a9:b1 5: ens3f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether a0:36:9f:b8:97:9c brd ff:ff:ff:ff:ff:ff permaddr a0:36:9f:b8:97:9e 6: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether e4:43:4b:61:a9:b2 brd ff:ff:ff:ff:ff:ff 7: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether e4:43:4b:61:a9:b3 brd ff:ff:ff:ff:ff:ff 8: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 2e:9e:5f:6d:50:7b brd ff:ff:ff:ff:ff:ff 9: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 46:26:b5:a2:3a:0a brd ff:ff:ff:ff:ff:ff 10: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:b8:97:9c brd ff:ff:ff:ff:ff:ff inet 10.66.23.100/24 brd 10.66.23.255 scope global noprefixroute ovirtmgmt valid_lft forever preferred_lft forever inet6 fe80::a236:9fff:feb8:979c/64 scope link noprefixroute valid_lft forever preferred_lft forever 11: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e4:43:4b:61:a9:b0 brd ff:ff:ff:ff:ff:ff inet 10.55.21.100/24 brd 10.55.21.255 scope global noprefixroute bond1 valid_lft forever preferred_lft forever inet6 fe80::d70:c3f8:851c:c388/64 scope link noprefixroute valid_lft forever preferred_lft forever 12: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovirtmgmt state UP group default qlen 1000 link/ether a0:36:9f:b8:97:9c brd ff:ff:ff:ff:ff:ff 15: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 Output From nmcli con show: ovirtmgmt b33ee040-938b-40ac-a52a-b3192c7ac9f3 bridge ovirtmgmt bond1 770d63df-62ea-4908-ae26-7887d3cdea4f bond bond1 bond0 09a0fb7f-98da-43cd-8013-461c0884c64d ethernet ens3f0 bond0 a5637915-df3f-408c-a8dd-004795599028 ethernet ens3f1 bond0 ca2b3e59-879f-4040-a4e6-62d0bb0a08e7 bond bond0 bond1 459d6944-d017-4b54-a657-2eeaeccb9efa ethernet eno2 bond1 e58b10ee-77e8-4254-a66d-baf3c295d559 ethernet eno1 bond2 731b08c8-2dc8-456a-aadb-4693f9b51bd8 ethernet -- bond2 3b7a36be-101e-47ab-a351-7a887cc07b70 ethernet -- bond2 83c07c03-629a-4f90-b6bd-16e29b2f5f3e bond -- eno1 1a1d7226-fa0c-4527-b0da-7465213c561b ethernet -- eno2 1eacb960-00b7-4778-a692-1c34d64cce3f ethernet -- eno3 7d7b633a-99da-4272-93af-13596f63a308 ethernet -- eno4 c537f2d3-3d17-487c-a89a-5d91f5536a18 ethernet -- ens3f0 fb63f81f-08b8-4d01-975e-9b35cd9bedcc ethernet -- ens3f1 a50979ea-e6b4-4da5-90cd-1cb1c320abb8 ethernet --
Today I reloaded all three nodes with the 4.5.1 ovirt node appliance iso. During the install I used the gui to bond the two 10gig interfaces using the recommended naming convention. I prepped the nodes according to the documentation and invoked the cockpit installation method from node1. The gluster portion of the hyperconverged deployment went well. When the gluster portion of the deployment was finished I proceeded to the hosted engine deployment phase in the cockpit environment. The system immediately threw that same interface error. "No valid network interface has been found If you are using Bonds or VLANs Use the following naming conventions:" [root@hprvsr0 ~]# nmcli con show NAME UUID TYPE DEVICE bond0 c3823f14-4856-42f9-85a0-19370933a0ac bond bond0 bond1 25c9f64c-1cce-4b5f-93dd-488ee5c32729 bond bond1 virbr0 6ddf263d-a7df-4976-83c6-b241659c1023 bridge virbr0 eno1 05208633-17f2-48b4-b8a7-d7ed006eb929 ethernet eno1 eno2 c2720d01-f9c2-4f15-a63d-4a2214b1246b ethernet eno2 ens3f0 2c585f34-4f1d-4c46-8c04-f15749e09158 ethernet ens3f0 ens3f1 39b53c5b-9bfc-47ae-b659-b23320e612ab ethernet ens3f1 eno1 6981185b-2e06-4df7-ab1b-d161b2e3fd9f ethernet -- eno2 6b896a93-4e88-4e08-8d5e-2a48b33eb30e ethernet -- eno3 caf0d4e4-88e3-46cd-a3a7-26797697f6ec ethernet -- eno4 c945f081-872c-4756-910c-1749c6eb0cf2 ethernet -- ens3f0 6cfcb97b-aaf0-4536-99ea-7a85c44d5a5c ethernet -- ens3f1 b9d39a15-14df-4433-a1af-f05f5b88282e ethernet -- Anybody got any ideas ?
change to bond0 and try again, some time it might have hardcoded in the recent codes..
cockpit-ovirt is deprecated for hosted-engine deployment, try cli using "hosted-engine --deploy" instead. if it fails, please share ovirt-hosted-engine-setup log files located in /var/log/ovirt-hosted-engine-setup/ (especially the ovirt-hosted-engine-setup-ansible-get_network_interfaces-*.log) On Wed, Jun 29, 2022 at 7:13 AM dhanaraj.ramesh--- via Users < users@ovirt.org> wrote:
change to bond0 and try again, some time it might have hardcoded in the recent codes.. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/S2SBURTQ2N2DYJ...
Thank you very much for the tip. I was able to successfully deploy the engine appliance on the gluster configuration that I deployed previously from the cockpit interface. I cannot log into the management portal via username and password and it appears as though keycloak is the culprit. I'll open another thread for that problem. Thank you again for your help.
participants (4)
-
Asaf Rachmani -
Clint Boggio -
dhanaraj.ramesh＠yahoo.com -
Gianluca Cecchi