Ec2 metadata traffic on "undercloud" requires careful routing when hosting nova/quantum metadata

[Clint Byrum]

One must take care to make sure that during initialization a baremetal node can still reach its original Ec2 style metadata service at 169.254.169.254. Networking configurations may cause the default route to change. The symptom of this is that every time the node is rebooted its SSH Host key changes because cloud-init thinks that its instance ID changed.

[Robert Collins (lifeless)]

One wrinkle here is that br-ctlplane will stop access to the metadata server because ovs comes up too late.

[Robert Collins (lifeless)]

One possible thing we could do is push a 169.254 route to the box via extra routes.

[polfilm (polfilm)]

Related? Unable ssh onto overcloud instances (failing to connect to metadata server) https://bugs.launchpad.net/tripleo/+bug/1281174

[Steven Hardy (shardy)]

This bug was reported against an old version of TripleO, and may no longer be valid.

Since it was reported before the start of the liberty cycle (and our oldest stable
branch is stable/liberty), I'm marking this incomplete.

Please reopen this (change the status from incomplete) if the bug is still valid
on a current supported (stable/liberty, stable/mitaka or trunk) version of TripleO,
thanks!

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]