I do not this issue. None of our own machines have an ubuntu user and juju works. Juju requires the machines it provisions to have an ubuntu user.
Juju uses the login user as the identity for the local db and containers. The user account that is doing the deploy must export USER=<user>, this is the default behaviour in ubuntu, but extraordinary user/sh configuration will skip this step, then juju doesn't know who owns the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328958 Title: Local provider assumes a local "ubuntu" user exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
