© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
No, we're not doing anything with floating IPs at all, as far as this VM is concerned. The VM is created with only a fixed IP from a tenant network that's attached to an external network via a router.
These are the only logs in l3-agent around the time the VM was created:
--snip--
2020-01-02 20:42:40.506 31081 INFO neutron.
2020-01-02 20:42:40.507 31081 INFO neutron.
--snip--
I'm wondering if this is possible if the fixed IP attached to the VM was previously associated with an older VM, and the floating IP was attached to that? The ip rule could be leftover from the previous association. Just a wild idea, given the lack of errors in the logs.