Public bug reported:
cloud-init 0.7.9-48-g1c795b9-0ubuntu1~16.04.1
Cloud init generated /etc/network/interfaces.d/50-cloud-init.cfg for a
network configuration of two vlan'ed networks, on top of a bond, of two
interfaces.
The generated config did not work, as the bond specified "bond-slaves
none", there were also bond_* settings specified on the interfaces,
which I believe are redundant.
Comparing the config generated by this cloud-init with another instance
of similar type, I have removed the extrac bond_* settings from the
cloud init generated config, and also specified "bond-salves" on the
bond stanza, and disabled the cloud-init network config via snippet as
advised at the top of the file.
This made networking come up.
I will attach, the generated 50-cloud-init.cfg; diff of applied
differences; as well as the journal logs of both boots (broken and
working).
Imho cloud-init should generate bond-slaves stanzas with the interfaces
names.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684092
Title:
cloud-init in xenial generates bond configs that do not appear to work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1684092/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
