This looks a lot like a Trusty-specific issue to me, and nothing to do with sudo. When did CI move to Trusty?
Trusty no longer has the /etc/lxc/auto directory, and instead the LXC container config file has an attribute that says the container should be auto-started with the machine. Jesse has an in-progress CL that addresses this by checking if the auto directory exists before attempting to create the auto-start symlink. Cheers, Andrew On Sat, Jan 25, 2014 at 1:53 PM, Curtis Hovey-Canonical < [email protected]> wrote: > I reported https://bugs.launchpad.net/juju-core/+bug/1272590 > "cannot deploy with lxc with new sudo rules" > > In summary, since the new rules break CI scripting, I have tested > 1.17.1 local deployments myself. I cannot deploy local services, nor > can I destroy them cleanly (/me reported a separate bug to track that > azure and openstack are shutting down machines instead of deleting > them) > > Our choices are: > 1. Release any way. Note that local provider is broken. > Release 1.17.2 a day or two later when we have a fix. > > 2. Fix the issue. I think we need to manually test still, but maybe > CI will work without changes. > > 3. Rollback the sudo/lxc changes. > > > -- > Curtis Hovey > Canonical Cloud Development and Operations > http://launchpad.net/~sinzui > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
