@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 ephemeral environment, which I'm
guessing its what's affecting you.
As such, can you confirm what customizations you are doing that are
causing the deployment failure ?
** Changed in: maas
Status: Triaged => Incomplete
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
