Note that bug 1317680 may be a potential issue here. If you end up in the situation that you've previously synced the same release from both a daily and a released stream, then an attempt to create a container will be unambiguous and thus fail. In that bug the issue was that the user had manually done it locally. Here, the problem may be that Juju trips itself up by ending up in that situation, if Juju mixes use of released and daily streams.
I suppose a wider issue here is that we don't currently have a good answer inside simplestreams for syncing images from multiple streams into the same pool. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
