Description of problem: Vm cannot access the metadata ip which stops VM from getting keypair and can't access the VM Version-Release number of selected component (if applicable): RHOSP16.1.6 How reproducible: Everytime Steps to Reproduce: 1. Create a network and subnet 2. Create VM 3. VM gets created successfully and it fails to inject keys Actual results: VM cannot reach metadata for the very time Expected results: All VMs should reach metadata. Additional info: May be similar to https://bugs.launchpad.net/neutron/+bug/1928164
Hello Team, Here are the series to steps to reproduce the issue 1. Create a new network and subnet for that network. 2. Instances using that network/subnet can be created and are able to reach the metadata agent on arbitrary compute nodes. 3. Once all instances using that network/subnet are deleted from a compute node, the metadata agent is removed, since it is no longer needed. 4. Afterwards, creating new instances using that network/subnet on such a compute node will lead to the metadata agent being re-created, but it is now in a bad state (unrelated to the netns issues I saw yesterday) and can no longer be reached by the VMs. Thank You
I'm closing this BZ for now, the OpenStack related is bug 1970948 and the progress can be tracked there. Please feel free to re-open if it's needed for some tracking but from the development standpoint everything is in bug 1970948. *** This bug has been marked as a duplicate of bug 1970948 ***