Public bug reported:
TLDR: when MAAS is configured to use custom archives, Trusty deployments
fail.
When custom archive configurations are in use, MAAS renders cloud-init
config which cloud-init reads in order to set up apt details.
The cloud-init config format it renders is only compatible with the
cloud-init in Xenial. That version is currently:
0.7.9-153-g16a7302f-0ubuntu1~16.04.2
It looks something like this:
apt:
source1:
source: "deb http://packages.chef.io/repos/apt/stable
$RELEASE main"
key: |
-----BEGIN PGP PUBLIC KEY BLOCK-----
I fetched that example from
http://cloudinit.readthedocs.io/en/latest/topics/examples.html
The cloud-init version in Trusty is 0.7.5-0ubuntu1.22 and the equivalent
stanza looks like this:
apt_sources:
- source: "deb http://apt.opscode.com/ $RELEASE-0.10 main"
key: |
-----BEGIN PGP PUBLIC KEY BLOCK-----
I fetched that example from
http://cloudinit.readthedocs.io/en/0.7.7/topics/examples.html
Looking at src/maasserver/compose_preseed.py:get_archive_config() it
seems that MAAS only supports the Xenial-hosted version's format. That
breaks the custom archives feature.
** Affects: maas
Importance: Undecided
Status: New
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu)
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/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
