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. -- 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 archive keys 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
