Its possible that over time the DHCP assignment to your instances no longer ping. The IP appears and its assigned but regardless of the Security Groups, the IP still doesn’t respond to anything.
Error message: dnsmasq-dhcp: DHCPDISCOVER(tapf7676729-f5) f4:52:14:2a:cb:70 no address available.
The issue is most likely due to the DHCP, you can first check by returning the network ID with:
openstack network list
Afterwards you can check the system which has the Neutron service with:
ip netns | grep 0dcd861c-719d-4bc5-93df-078547cf66c1 returned value: qdhcp-0dcd861c-719d-4bc5-93df-078547cf66c1 It will allow you to get the full value and do a query on the name space: ip netns exec qdhcp-0dcd861c-719d-4bc5-93df-078547cf66c1 ip a returned value: 43: tapf7676729-f5:
mtu 9000 qdisc noqueue state UNKNOWN qlen 1000 link/ether fa:16:3e:95:02:98 brd ff:ff:ff:ff:ff:ff inet 10.4.1.8/16 brd 10.4.255.255 scope global tapf7676729-f5
The full address assignment can be found at:
ps -efa | grep tapf7676729-f5 ip netns exec qdhcp-0dcd861c-719d-4bc5-93df-078547cf66c1 ip a ip netns exec qdhcp-0dcd861c-719d-4bc5-93df-078547cf66c1 ping -c4 10.4.1.207