@Tom,
All third party OS' are deployed with the latest LTS ephemeral image or
the one that is default for commissioning.
There are multiple reasons why we always deploy a Ubuntu based OS' with
the same ephemeral image. Examples:
1. If you deploy 'Trusty' with Xenial ephemeral on a hardware for
Yeah we can configure it to mirror back-ports. Just not multiverse, and
we would prefer not to host source either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664248
Title:
On Ubuntu 14.04 with
@tpmullan, could you configure your mirror to mirror backports, as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1664248
Title:
On Ubuntu 14.04 with backports pocket
@tpmullan, could you configure your mirror to mirror backports, as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664248
Title:
On Ubuntu 14.04 with backports pocket disabled maas fails to
Do you know why it is trying to pull down source from the repos? I
don't see why the ephemeral image should ever compile anything so this
seems like another useless dependency.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So why does Trusty deploy with an ephemeral image of Trusty? For
example when I deploy centos it uses Xenial to perform the deploy and
everything works fine. It seems like this would be an easy way to
insure that all features are available on all or at least more versions.
This is a very large
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: cloud-init (Ubuntu Trusty)
Importance:
So after banging my head a while trying to find out why this wasn't
working for you, I realized that you were deploying Ubuntu 14.04.
The ability to disable_pockets was introduced in MAAS 2.1, and will only
work when deploying Xenial+. This is because MAAS depends on cloud-init
to do such
