The killing metadata process is handled by update_isolated_metadata_proxy. It was added to ensure to spawn metadata proxy process for network with ipv4 subnet added later after ipv6 subnet. However it also kills any metadata proxy process in dhcp namespace for network without isolated network. However the method doesn't get called when network(subnet) is deleted from router. As result, there is no metadata proxy in dhcp namespace to provide VM with metadata service in the scenario described in description. Please correct me if I am wrong. Thanks.
The killing metadata process is handled by update_ isolated_ metadata_ proxy. It was added to ensure to spawn metadata proxy process for network with ipv4 subnet added later after ipv6 subnet. However it also kills any metadata proxy process in dhcp namespace for network without isolated network. However the method doesn't get called when network(subnet) is deleted from router. As result, there is no metadata proxy in dhcp namespace to provide VM with metadata service in the scenario described in description. Please correct me if I am wrong. Thanks.
https:/ /github. com/openstack/ neutron/ blob/bd193cba73 bd4de41bd3a5c5a 693f86797e56b8b /neutron/ agent/dhcp/ agent.py# L476-L488