New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENI format - configuring metadata network-interfaces with iface defined twice but different family breaks all networking on cloud-init instance #3105
Comments
Launchpad user Andreas(andreas-redhat-bugs) wrote on 2018-01-26T16:04:26+00:00 Description of problem: The following breaks networking:
According to https://wiki.debian.org/NetworkConfiguration , this should work, though:
If you want to add an IPv6 address, too, append something like:
+++ And https://manpages.debian.org/jessie/ifupdown/interfaces.5.en.html The following works correctly:
Additional info: Working instance: ./sosreport-20180125-075718/svc-1-lvsrouter/var/log/cloud-init-output.log
result not working:
|
Launchpad user Andreas(andreas-redhat-bugs) wrote on 2018-01-26T16:21:13+00:00 Tested with cloud-init-0.7.9-20.el7.x86_64 |
Launchpad user Ryan(ryan-redhat-bugs) wrote on 2018-01-26T18:30:53+00:00 I don't believe this is intended to work. Did defining the interface twice previously work for the customer? The current upstream release explicitly errors out when you do this with a parse error. |
Launchpad user Andreas(andreas-redhat-bugs) wrote on 2018-01-26T19:38:14+00:00 Hi, cloud-init upstrea in cloudinit/net/eni.py
a) iface eth2 inet static a) b) inet will define ifaces['eth2']['family'] as 'inet' and then on the next pass with inet6, The actual error message doesn't seem to figure in any of the collected customer data, but from the above, it seems pretty clear that the ENI format accepts only one interface and not different tuples of iface/family. |
Launchpad user Andreas(andreas-redhat-bugs) wrote on 2018-01-26T19:44:20+00:00 I'm bringing this upstream ... http://cloudinit.readthedocs.io/en/latest/topics/network-config-format-eni.html#network-config-eni states that:
From https://manpages.debian.org/jessie/ifupdown/interfaces.5.en.html - the man page doesn't seem to say anything else about duplicate iface declarations with different families:
According to https://wiki.debian.org/NetworkConfiguration , this should work, though:
|
Launchpad user Andreas Karis(akaris) wrote on 2018-01-26T19:46:12.538341+00:00 I'm bringing this upstream ... http://cloudinit.readthedocs.io/en/latest/topics/network-config-format-eni.html#network-config-eni states that:
From https://manpages.debian.org/jessie/ifupdown/interfaces.5.en.html - the man page doesn't seem to say anything else about duplicate iface declarations with different families:
According to https://wiki.debian.org/NetworkConfiguration , this should work, though:
|
Launchpad user Andreas Karis(akaris) wrote on 2018-01-26T19:49:00.018223+00:00 The implementation doesn't seem to like this, though: cloud-init upstrea in cloudinit/net/eni.py
a) iface eth2 inet static a) b) inet will define ifaces['eth2']['family'] as 'inet' and then on the next pass with inet6, The actual error message doesn't seem to figure in any of the collected customer data, but from the above, it seems pretty clear that the ENI format accepts only one interface and not different tuples of iface/family. |
Launchpad user Ryan Harper(raharper) wrote on 2019-07-19T20:49:32.545135+00:00 Thanks for filing the bug. The ifupdown eni parser in eni.py does not handle reading multiple stanzas of the same interface; however it is support in eni; so this is a bug in the eni format parser. |
This bug was originally filed in Launchpad as LP: #1745671
Launchpad details
Launchpad user Andreas Karis(akaris) wrote on 2018-01-26T19:45:38.021665+00:00
Description of problem:
Configuring metadata network-interfaces with "iface eth2 inet6 static" breaks all networking on cloud-init instance. This only works when configuring a sub interface.
The following breaks networking:
According to https://wiki.debian.org/NetworkConfiguration , this should work, though:
+++
If you're configuring it manually then something like this will set the default gateway (network, broadcast and gateway are optional):
If you want to add an IPv6 address, too, append something like:
+++
And https://manpages.debian.org/jessie/ifupdown/interfaces.5.en.html
+++
Options are usually indented for clarity (as in the example above) but are not required to be.
+++
The following works correctly:
Additional info:
result working:
Working instance: ./sosreport-20180125-075718/svc-1-lvsrouter/var/log/cloud-init-output.log
result not working:
The text was updated successfully, but these errors were encountered: