Hi, I don't have this issue in Antelope, which is the current version of our production cloud. In my test cloud on Caracal I can't reproduce it either. For me it works as expected. But this week I saw something at least similar to what you describe. Due to a bug in the dashboard I was also testing detaching interfaces from instances. From neutron perspective detaching seemed to have worked, but there still was some kind of mixup, leading to an instance having two NICs (from neutron's perspective). It turned out to be a nova-compute issue. We had some network maintenance going on, and although 'openstack network agent list' and 'openstack compute service list' were all reported as up, there were still error messages in the logs about missing responses. Basically, I had to restart all nova-compute and neutron services to get out of that situation. So I'd recommend to check the "real" health status of all agents. And it could also be related to udev within the instance, although I wouldn't expect two NICs but eth1 instead of eth0. And where exactly do you see that the VM has two NICs? In the nova interface-list (so from openstack's perspective) or within the VM? If it's the latter, I'd expect some udev rule or something, so related to the VM's image. You can check /etc/udev/rules.d/70-persistent-net.rules (it may be a different path/file) for the current status. Zitat von Nell Jerram <nell@tigera.io>:
I'm not sure why it was originally written, but I have an ancient system test that: - creates a VM attached to one network - finds the VM's port and calls interface_detach for it - checks that the VM is now unpingable - calls interface_attach with the relevant network_id - hard reboots the VM - checks that the VM is now pingable again.
With Yoga, the test passes, and at the end of the test the VM has one NIC, eth0, with an IP address.
With Caracal, the test also passes, but at the end of the test the VM has two NICs: - eth0 with no IP address - eth1 with an IP address.
Diffing the Nova code, it looks like interface_detach and interface_attach might actually have been no-ops in Yoga - although possibly only for a "vdpa" vnic-type, and I'm unsure whether that vnic-type would be relevant to my test setup.
Any ideas about this?
Many thanks - Nell