For posterity, MAAS trusty configuration uses package_mirrors to change
the archive the machines should access. Such configuration does not
support specifying a key for a custom mirror.
That said, the deployed machine will end up with the correct
configuration, but the deployment ephemeral
MAAS does? I am looking at
src/maasserver/compose_preseed.py:get_archive_config() and I don't see
apt_sources anyway.
--
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
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336284
--
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
I'm wondering if you possibly were hitting bug 1744038.
MAAS can declare (and actually, i think *does* declare) both old format
configuration of apt and new format configuration. That would cover
trusty and later. If you declare both, though, there is code in cloud-
init that insists they are
** Changed in: maas
Status: In Progress => Triaged
** Merge proposal unlinked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336284
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
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:
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336284
--
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
** Changed in: maas
Status: Incomplete => In Progress
--
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
@Kiko,
I've tested a deployment of trusty and confirm that the deployed system
does end up with the configuration of the custom repository. This is
because the configuration happens by curtin.
However, the difference between trusty and xenial is that the custom
repository is not available in the
** Tags added: cpe-onsite
** Tags added: 4010
--
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
(Presumably because it's still accepted by cloud-init)
--
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
Note that https://help.ubuntu.com/community/CloudInit still documents
the old stanza format.
--
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
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Importance: Critical => High
--
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:
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Critical
--
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
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
15 matches
Mail list logo
