** Changed in: juju
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930430
Title:
lxc-ls requires root access after deploying an LXC instance
** Changed in: juju
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930430
Title:
lxc-ls requires root access after deploying an LXC instance
It would appear that the problem happens because of twistd's default
behavior when daemonizing. It always sets umask to 0077. On non-local
images, we don't daemonize because the agents are run via upstart in
--nodaemonize mode.
I have a fix for this in the local-cloud-img branch, which is to
I've just noticed this with some of the unit tests, afaik this is some
change in lxc behavior.
$ lxc-ls
kapil-dev-0-template kapil-dev-wordpress-0 monitoring
/usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied
ls: cannot access kapil-dev-wordpress-0: No such file or
Quoting Kapil Thangavelu (930...@bugs.launchpad.net):
I've just noticed this with some of the unit tests, afaik this is some
change in lxc behavior.
I don't think it's a change in lxc behavior. I think it's a change in
the umask which juju has set when it calls lxc-start.
lxc passes a
** Also affects: juju
Importance: Undecided
Status: New
** Changed in: juju
Status: New = Triaged
** Changed in: juju
Importance: Undecided = High
** Changed in: juju
Milestone: None = 0.6
--
You received this bug notification because you are a member of Ubuntu
Server
I encountered with this issue when I was trying to destroy a local
environment. I have no problem to bootstrap/deploy service locally.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hi Jamie,
I started seeing this with juju 0.5.1+bzr563-0juju2~precise1, to which I
recently upgraded. With 0.5+bzr531-0ubuntu1.2 (also in precise) it
works.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
This is odd, I seem to have lost a bunch of comments - meaning I must
have added them to the wrong bug!
The gist is, this is not a bug in lxc in my opinion. Lxc creates the
/sys/fs/cgroup/xyz/lxc directories using mkdir(2) passing 0755 as the
mode. That mode is masked with the task's umask.
Thanks, Jamie, I will try to reproduce with your recipe.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930430
Title:
lxc-ls requires root access after deploying an LXC instance
To
@Jamie,
to help me gauge priority - is this in any way blocking you? If not I'll
mark it as low priority since sudo is a workaround :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
This is not blocking me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/930430
Title:
lxc-ls requires root access after deploying an LXC instance
To manage notifications about this
** Changed in: juju (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: juju (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are
If I first
lxc-create -t ubuntu -n oneiric
lxc-start -n oneiric
(and then shut that down)
and then do juju bootstrap and deploy, it goes fine. It seems like juju
is chmod'ing the lxc cgroup directories, but I don't see where (or why).
--
You received this bug notification because you
14 matches
Mail list logo
