Comment 8 for bug 1743966
Revision history for this message
| Andres Rodriguez (andreserl) wrote Re: Trusty deployments fail when custom archives are configured | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
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 environment doesn't.
The reason this is an issue is becuase that instead of creating an additional reposiutory with the software, a custom mirror is being created, with additional packages, and completely re-signed.