There are at least two ways this could be fixed: 1. To backport the cloud-init change to Trusty; note that cloud-init is backwards-compatible and widely tested, but also widely in use 2. To have MAAS generate stanzas in both formats, selecting the right one according to the ephemeral environment being used.
It would be worth considering what will happen as cloud-init continues to evolve and our LTS backlog grows due to ESM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743966 Title: Trusty deployments fail when custom archives are configured To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1743966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
