cloud-init should support changing the NICs present in an instance between boots
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Hello,
I uploaded
bionic-
into glance. I started an Instance. The instance is reachable.
Next i shutdown the instance
openstack server stop <instance-id>
detach the interface
openstack server remove network <instance-id> <network>
afterwards I attach a new interface with the same IP as before
openstack server add fixed ip --fixed-ip-address <IP-address> <instance-id> <network>
then start the instance and the instance is not reachable.
I can reproduce this behaviour with.
bionic-
CentOS-
This does not happen with :
CentOS-
xenial-
trusty-
cirros-
The images are unchanged.
I logged in via local console into ubuntu 18:04. The interface was down and I could see the following logs:
Aug 26 08:38:17 os-steb-pa1 systemd[1]: Starting Apply the settings specified in cloud-config...
Aug 26 08:38:17 os-steb-pa1 networkd-
Aug 26 08:38:17 os-steb-pa1 networkd-
A dhclient -v <interface> started the interface and the the instance got an answer from dhcp and was reachable again.
I logged in via local console into CentOS 7. The interface was also down and I could see the following logs:
Aug 26 09:05:37 os-steb-cl1 network: Bringing up interface eth0: ERROR : [/etc/sysconfig
Aug 26 09:05:37 os-steb-cl1 /etc/sysconfig/
Aug 26 09:05:37 os-steb-cl1 network: [FAILED]
Aug 26 09:05:37 os-steb-cl1 systemd: network.service: control process exited, code=exited status=1
A dhclient -v <interface> started the interface and the the instance got an answer from dhcp and was reachable again.
The problem is the old mac address in
ubuntu 18.04 /etc/netplan/
centos 7 /etc/sysconfig/
Manually changing the mac address in these files to the new one, solves the problem and the instances are reachable again after reboots.
I don't know how the mechanism worked for the older operating systems to establish a network connection after the interface changed via openstack, but this seems to be broken with the newer operating systems.
Environment
=======
1.
Rocky
ii nova-api 2:18.1.
ii nova-common 2:18.1.
ii nova-conductor 2:18.1.
ii nova-consoleauth 2:18.1.
ii nova-novncproxy 2:18.1.
ii nova-placement-api 2:18.1.
ii nova-scheduler 2:18.1.
ii python-nova 2:18.1.
2.
Libvirt + KVM
ii qemu-kvm 1:2.11+
ii libvirt-daemon 4.0.0-1ubuntu8.12 amd64 Virtualization daemon
ii libvirt-
ii libvirt0:amd64 4.0.0-1ubuntu8.12 amd64 library for interfacing with different virtualization systems
ii python-libvirt 4.0.0-1 amd64 libvirt Python bindings
3.
Neutron with OpenVSwitch and dvr_snat
Greets
affects: | nova → cloud-images |
This isn't really a nova problem as far as I can tell, it's a problem with the images.