Max: any joy? My conclusion for now is:
When running a local environment, Juju uses the existence of /home/ubuntu to determine if the ubuntu user is special. Instead, it should pay attention to what user my original user was (before sudo-ing, etc). I understand that when deploying to any other environment the ubuntu user is special; Juju doesn't seem to correctly differentiate between these two cases. I guess the same code path is followed in both cases, or something? -- 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/1328958 Title: Local provider run on server images requires an ubuntu user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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
