This bug is believed to be fixed in cloud-init in version 18.4. If this is still a problem for you, please make a comment and set the state back to New
Thank you. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1784699 Title: cloud-init not setting mac address for bond or bridge in bionic Status in cloud-init: Fix Released Bug description: When deploying bionic, cloud-init doesn't set the mac address for the bond or bridge interface, which causes issues when there's expectations between MAC/IP mappings. For example, in Bionic: curtin config sent (/etc/cloud/cloud.cfg.d/50-curtin-networking.cfg): http://paste.ubuntu.com/p/25GnQXQVhn/ neplan config written to netplan (/etc/netplan/50-cloud-init.cfg): http://paste.ubuntu.com/p/XGQRzjGTDm/ The result is that each interface have a different MAC address from those told in the configuration: ip addr sh: http://paste.ubuntu.com/p/25GnQXQVhn/ This results in inconsistency which was configured and intended by the user, vs what it was actually written. For example, in Xenial, the issue above doesn't exist and the result is as expected: curtin config: http://paste.ubuntu.com/p/DmFvryXdwm/ e/n/i config: http://paste.ubuntu.com/p/fsXYpmMzCb/ ip addr sh: http://paste.ubuntu.com/p/wXXSTNfwHK/ Also note that in my configuration, I kept the same mac addresses for bridges/bond as the physical interfaces, but if I were to randomize those or choose other ones, the behavior is the same. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1784699/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp