I have reproduced the issue again on a fresh Trusty cloud image. It
reproduces reliably just by removing the ubuntu user first. Exact
reproduction steps below.
Juju requires the machines it provisions to have an ubuntu user.
That's fine, but Juju must not assume that the local user has an
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: local-provider
** Summary changed:
- Local provider assumes a local ubuntu user exists
+ Local provider run on cloud images want ubuntu user
--
You received this
I have reproduced the issue again on a fresh Trusty cloud image. It
reproduces reliably just by removing the ubuntu user first. Exact
reproduction steps below.
Juju requires the machines it provisions to have an ubuntu user.
That's fine, but Juju must not assume that the local user has an
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: local-provider
** Summary changed:
- Local provider assumes a local ubuntu user exists
+ Local provider run on cloud images want ubuntu user
--
You received this
** Changed in: juju-core
Status: New = Incomplete
--
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 assumes a local ubuntu user exists
To
The Juju CI tests do two non obvious things to test the local provider.
1. Never su to the testing account. Always log directly in.
2. Always export USER=jenkins so that juju knows which user owns the containers.
--
You received this bug notification because you are a member of Ubuntu
Server
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
** Changed in: juju-core
Status: New = Incomplete
--
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
The Juju CI tests do two non obvious things to test the local provider.
1. Never su to the testing account. Always log directly in.
2. Always export USER=jenkins so that juju knows which user owns the containers.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
My steps to reproduce on a Trusty cloud image (off the top of my head -
let me know if you have any problems):
1. sudo adduser --disabled-password --gecos '' otheruser
2. echo 'otheruser ALL=(ALL) NOPASSWD:ALL'|sudo tee --append /etc/sudoers
3. sudo add-apt-repository ppa:juju/stable
4. sudo
Filed bug 1332820 for test coverage.
--
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 assumes a local ubuntu user exists
To manage notifications
Filed bug 1332820 for test coverage.
--
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:
My steps to reproduce on a Trusty cloud image (off the top of my head -
let me know if you have any problems):
1. sudo adduser --disabled-password --gecos '' otheruser
2. echo 'otheruser ALL=(ALL) NOPASSWD:ALL'|sudo tee --append /etc/sudoers
3. sudo add-apt-repository ppa:juju/stable
4. sudo
14 matches
Mail list logo
