Public bug reported:
When starting OVN migration workload, some of the workload VMs (usually only
one of them) is not accessible via ssh. As can be seen in console logs the VM
is not able to retrieve metadata.
This is basically due to bug https://bugs.launchpad.net/neutron/+bug/1813787 -
nova
starts vm faster then local dvr router is ready thus during the vm's boot
process when vm asks for metadata, there is (yet) no haproxy ready to process
those requests.
If I create router and attach subnet before starting VMs the issue does not
happen. So it seems like the order of the workload creation should be changed.
** Affects: neutron
Importance: Undecided
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1947547
Title:
Sporadic metadata issues when creating OVN migration workload
Status in neutron:
In Progress
Bug description:
When starting OVN migration workload, some of the workload VMs (usually only
one of them) is not accessible via ssh. As can be seen in console logs the VM
is not able to retrieve metadata.
This is basically due to bug https://bugs.launchpad.net/neutron/+bug/1813787
- nova
starts vm faster then local dvr router is ready thus during the vm's boot
process when vm asks for metadata, there is (yet) no haproxy ready to process
those requests.
If I create router and attach subnet before starting VMs the issue does not
happen. So it seems like the order of the workload creation should be changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1947547/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
