This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.5
---
cloud-init (0.6.3-0ubuntu1.5) precise-proposed; urgency=low
* debian/update-grub-legacy-ec2: consider kernels bootable on ec2
that are named -generic, in addition to -virtual. This fixes a problem
where
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.5 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Verified. See below.
$ sudo apt-get update sudo apt-get install -y lxc
$ lsb_release -c
Codename: precise
$ dpkg-query --show lxc
lxc 0.7.5-3ubuntu66
$ sudo lxc-clone -o source-precise-amd64 -n patched
$ cat /var/lib/lxc/source-precise-amd64/rootfs/etc/cloud/build.info
build_name:
** Description changed:
+ == Begin SRU Information ==
+ [Impact]
+ Cloud-init in 12.04 has an upstart job named 'cloud-init-nonet' that
+ calls 'start networking' explicitly. This was done to fix a boot
+ deadlock (bug 800824), but it was not the proper fix.
+
+ A much more correct fix is now
I built a precise cloud-init with the 'start networking' removed and
tried starting an lxxc instace with that from current precise daily
(with mountall 2.36.3). This issue persisted.
Steve, did you tihnk this *should* be fixed in precise?
--
You received this bug notification because you are
With the current mountall in precise, 2.36.3, yes - there shouldn't be
any further need to call 'start networking' directly. Are the symptoms
exactly the same as before the mountall fix?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru
--
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/1031065
Title:
cloud-init-nonet runs 'start networking' explicitly
To
Just a note, an SRU of this depends on SRU of mountall 643289.
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Precise)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu Precise)
Importance: Undecided =
This bug was fixed in the package cloud-init - 0.7.0~bzr659-0ubuntu1
---
cloud-init (0.7.0~bzr659-0ubuntu1) quantal; urgency=low
* New upstream snapshot.
* add signal handlers to more cleanly exit
* add logging fallback in case logging fails
* documentation fix for
** 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/1031065
Title:
cloud-init-nonet runs 'start networking' explicitly
To manage notifications about
** Branch linked: lp:~smoser/cloud-init/trunk.lp1031065
--
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/1031065
Title:
cloud-init-nonet runs 'start networking' explicitly
To
There is an 'eth0' defined in /etc/network/interfaces.
And, there is a network device eth0
$ sed -e /^$/d -e '/^#/d' etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
$ ls -l
I built a deb from lp:ubuntu/mountall revno 415.
installed it into a ephemeral image for quantal
commented out 'start networking' from /etc/init/cloud-init-nonet.conf, and got
the /var/log/kern.log at http://paste.ubuntu.com/1198891/ .
it seems something is blockign virutal-filesystems event
Steve,
I've also now tried your mountall in an lxc chroot, and it did not resolve my
issue there either.
I've set up a lxc container as described above, commented out the 'start
networking' and then:
$ sudo ln -sf console /path/to/rootfs/dev/kmsg
$ sudo lxc-start --name=$REL-amd64 --console
The log for the container seems to show reasonable ordering for the
events. It also shows:
cloud-init-nonet waiting 120 seconds for a network device.
cloud-init-nonet gave up waiting for a network device.
6init: cloud-init-nonet main process (31) exited normally
6init: cloud-init-nonet goal
Attaching plaintext console log.
** Attachment added: console.log
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+attachment/3308428/+files/console.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
network-interface (lo) is the only interface job shown, so either
something is going wrong when bringing up this interface that prevents
/etc/network/if-up.d/upstart from emitting the static-network-up event,
or there are other network interfaces configured in
/etc/network/interfaces that have no
Scott, can you please try a test package of mountall built from
lp:ubuntu/mountall? I think I have both the mounting and mounted events
handled correctly there (and in my tests, seemingly faster).
Testing in scenarios other than the cloud boot case would also certainly
be helpful.
--
You
Finding a better solution to the 'start networking' that we have here has lead
me to open bug 1047712.
The case that I was debugging was actually not even improved by the 'start
networking'. The issue that lead us here was that the ephemeral images for
maas that we were trying to refresh have
So, after much discussion [1] we came to the realization of why 'start
networking' was here.
The issue was that the normal case for cloud-images (and ubuntu as a whole) is
that / is mounted ro when /sbin/init starts. When this is the case, /run
will be mounted before /. However, if / is
After reviewing the patches on bug #643289, I see that some further work
will be needed because those patches only adjust the 'mounting' event,
not the 'mounted' event. IMHO we should do both.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: cloud-init (Ubuntu)
Status: Confirmed = Triaged
--
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/1031065
Title:
cloud-init-nonet runs 'start networking'
I was able to recreate the original problem of bug 800824 by doing the
following on a precise instance:
- setup the instance, get source roots of the ubuntu-cloud lxc root:
for r in oneiric precise quantal; do \
sudo lxc-create -t ubuntu-cloud -n source-$r-amd64 -- \
--release $r
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Some conversation in ubuntu-devel yesterday [1]. This seems to have
been caused by the fix for bug 800824. That change [2] was done to
address failure of networking to appear as started a container. Per
Steve, that looks like a wrong workaround for bug #925122.
Hopefully what that means is we
25 matches
Mail list logo
