** Changed in: cloud-init
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/941955
Title:
util.islxc() method is broken without
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/941955
Title:
util.islxc() method is broken without is-lxc-container
To manage
This was fixed in revno 529.
** Changed in: cloud-init
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/941955
Title:
util.islxc() method
Per stgraber, I should mimic the code in /etc/init/container-detect.conf [1]
in the case where there is no 'running-in-container' (which is the new
replacement for lxc-is-container).
--
[1]
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/941955
Title:
util.islxc() method is broken without is-lxc-container
To manage notifications
This bug was fixed in the package cloud-init - 0.6.3~bzr530-0ubuntu1
---
cloud-init (0.6.3~bzr530-0ubuntu1) precise; urgency=low
* New upstream snapshot.
- fix DataSourceNoCloud seeded from local or cmdline (LP: #942695)
- change 'islxc' to 'iscontainer' and use
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/941955
Title:
util.islxc() method is broken without is-lxc-container
To manage notifications about this bug go to:
(I suspect you know this, but it's kind of hard to find because it's
been renamed and switched packages: you should now use /bin/running-in-
container which ships with upstart)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
On Mon, 27 Feb 2012, Serge Hallyn wrote:
(I suspect you know this, but it's kind of hard to find because it's
been renamed and switched packages: you should now use /bin/running-in-
container which ships with upstart)
I did not know this. you probably should lay down a symlink or some other
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = High
** Changed in: cloud-init
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
10 matches
Mail list logo
