Local provider fails when an unrelated /home/ubuntu directory exists
Bug #1328958 reported by
Max Brustkern
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Ian Booth | ||
1.21 |
Fix Released
|
Medium
|
Ian Booth | ||
juju-core (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
I'm trying to init and bootstrap the juju local provider on utopic. I keep getting a chown: invalid user error:
max@eden:~$ rm -rf .juju
max@eden:~$ juju init
A boilerplate environment configuration file has been written to /home/max/
Edit the file to configure your juju environment and run bootstrap.
max@eden:~$ juju switch local
amazon -> local
max@eden:~$ juju bootstrap
uploading tools for series [utopic precise trusty]
Logging to /home/max/
chown: invalid user: ‘ubuntu:ubuntu’
Bootstrap failed, destroying environment
ERROR exit status 1
max@eden:~$
Changed in juju-core: | |
status: | New → Incomplete |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: local-provider |
summary: |
- Local provider assumes a local "ubuntu" user exists + Local provider run on cloud images want ubuntu user |
summary: |
- Local provider run on cloud images want ubuntu user + Local provider run on server images requires an ubuntu user |
Changed in juju-core: | |
milestone: | none → 1.22 |
Changed in juju-core: | |
milestone: | 1.22 → 1.21-beta4 |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 1.21-beta4 → 1.22 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core (Ubuntu): | |
status: | Triaged → Fix Released |
To post a comment you must log in.
I came across this on Trusty using ppa:juju/stable :
$ dpkg-query -W juju-core juju-local 0ubuntu1~ 14.04.1~ juju1 0ubuntu1~ 14.04.1~ juju1
juju-core 1.18.4-
juju-local 1.18.4-
So on Trusty, an ordinary user's desktop will not have an ubuntu user, and the local environment is completely broken on it.
It seems to me that for proper test coverage, the test environment also needs to be changed to not have an ubuntu user. I can understand why Juju must make assumptions about such a user (since cloud images ship with one), but this demonstrates why it is essential that the local environment is tested without one.