Public bug reported:
Rally scenario which creates VMs with floating IPs at a high rate
sometimes fails with SSHTimeout when trying to connect to the VM by
floating IP. At the same time pings to the VM are fine.
It appeared that VMs may sometimes fail to get public key from metadata.
That happens because metadata proxy process was started after VM boot.
Further analysis showed that l3 agent on compute node was not notified
about new VM port at the time this port was created.
** Affects: neutron
Importance: High
Assignee: Oleg Bondarev (obondarev)
Status: In Progress
** Tags: l3-dvr-backlog liberty-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1521524
Title:
With DVR enabled instances sometimes fail to get metadata
Status in neutron:
In Progress
Bug description:
Rally scenario which creates VMs with floating IPs at a high rate
sometimes fails with SSHTimeout when trying to connect to the VM by
floating IP. At the same time pings to the VM are fine.
It appeared that VMs may sometimes fail to get public key from
metadata. That happens because metadata proxy process was started
after VM boot.
Further analysis showed that l3 agent on compute node was not notified
about new VM port at the time this port was created.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521524/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
