@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 which
Trusty's default kernel does not include support for, then the
deployment process will succeed, but the deployed machine won't work.
2. Similarly, if you deploy 'Zesty' with a Xenial ephemeral image, on a
machine for which Xenial doesn't have drivers for, then the deployment
process will fail altogether.
That said, I did a bit more digging and I need to correct my previous
statement. MAAS/cloud-init/curtin do not support configuring 'components' nor
'sources' for the Ubuntu mirrors:
* components = main, restricted, universe, multiverse
* source = deb-src
Configuring pockets for the Ubuntu mirrors is supported though.
* pockets = *-updates, *-security, *-backports
Changing this as a wishlist.
** No longer affects: cloud-init (Ubuntu Trusty)
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Triaged
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Confirmed
** Changed in: maas
Status: Incomplete => Triaged
** Summary changed:
- On Ubuntu 14.04 with backports pocket disabled maas fails to boot the
ephemeral image
+ Can't disable a backports pocket on Ubuntu 14.04
** Summary changed:
- Can't disable a backports pocket on Ubuntu 14.04
+ Can't disable a backports pocket when deploying Ubuntu 14.04
--
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:
Can't disable a backports pocket when deploying Ubuntu 14.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1664248/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
