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 ?