Comment 1 for bug 1932136

I did a bit of digging here. One of the issues is that eno2 on pangoro is considered disconnected. If you don't configure the interface and log in to pangoro, you can see with 'ip link' that eno2 doesn't have a CARRIER.

If you manually configure the interface, it does come up after a while. I tried to ping a known host, but the first 9 pings were lost. Only after that, the interface started receiving traffic.

That's most likely a cabling or switch configuration issue. I would suggest that you look into that, since I would think that would cause problems in the Openstack deployment itself.

The reason it works in 2.9, is that we don't properly detect that there's no link. I tried commissioning a machine with a NIC that didn't have a cable attached, and in 2.9 it was still reported as "link_connected" and "enabled". While in 3.0, it's properly reported as not connected, and not enable.

I don't think it makes sense to change 3.0 to work like in 2.9 in that regard, since that's clearly a bug that got fixed.

We might consider to mark the interface as enabled if you explicitly set the vlan of the interface, like you do. On the other hand, I think you should be aware of the fact that you're configuring a device that isn't connected. So we might also want to error out, and require the user to explicitly enable the interface first.

SolQA, what do you think?