Comment 14 for bug 1953165
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
We should not allow duplicated IPv4/IPv6 addresses. As commented by Bence, we are not currently providing metadata HA (we never did). Instead of allowing a configuration that could lead to potential errors, we should catch the error and not spawn the metadata server in the DHCP agent. At the same time, we should spawn a thread monitoring the interface. If the DHCP agent hosting the metadata server goes down, the others should try to configure the interface (metadata IPv4 or IPv6 addresses) and spawn the server (as proposed in [1]).
[1]https:/