/proc/cgroups
#subsys_namehierarchy num_cgroups enabled
debug 0 1 1
cpu 0 1 1
cpuacct 0 1 1
freezer 0 1 1
/proc/self/cgroup is empty
There is no /var/log/upstart/cgroup-lite.log file and I verified that
the upstart job
And the content of fstab
/system/etc # cat fstab
# override the forced fsck from /lib/init/fstab, we use a bindmount which
confuses mountall
/dev/root / rootfs defaults0 0
# swap file
/SWAP.swap noneswapsw 0 0
--
You received
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Ondrej Kubik (w-ondra)
--
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/1551150
Title:
devel-proposed -
android container log with cgroup-lite installed and content of
mountinfo from the same boot.
** Attachment added: "mountinfo.out"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584668/+files/mountinfo.out
--
You received this bug notification because
And syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584669/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
The phone uses upstart. I'll try to get the content of mountinfo
--
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/1551150
Title:
devel-proposed - android lxc container fails to start
To
With cgroup-lite install the error message is different:
lxc-start 20160229153538.890 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 -
cgroupfs failed to detect cgroup metadata
lxc-start 20160229153538.890 ERRORlxc_start - start.c:lxc_spawn:1026
- failed initializing cgroup support
I installed cgroup-lite 1.10 but it still doesn't boot.
--
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/1551150
Title:
devel-proposed - android lxc container fails to start
To manage
cgroup-lite is not installed:
un cgroup-lite
ii systemd:armhf 229-1ubuntu4
I cannot paste the content of /proc/mounts because I only have adb in
recovery (the devices fails before adb starts otherwise)
--
You
dmesg from a system that doesn't boot.
** Attachment added: "dmesg.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551150/+attachment/4584338/+files/dmesg.out
** Description changed:
Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
~ # cat /data/system-data/var/log/lxc/android.log
lxc-start 20160229125348.090 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 -
cgroupfs failed to detect cgroup metadata
lxc-start 20160229125348.091 ERRORlxc_start - start.c:lxc_spawn:1026
- failed initializing cgroup support
** Description changed:
Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
- ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on
- other devices do not boot and hang on the boot logo.
+ ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent
+
changes list between 446 and 447.
** Attachment added: "446-447.changes"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584311/+files/446-447.changes
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
Public bug reported:
current build number: 204
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
when the current date of the device is in the future, ntpdate fails with
'Invalid Argument'
For example:
* current date: passed
root@ubuntu-phablet:~# date
mardi 15 décembre
** Description changed:
current build number: 204
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
when the current date of the device is in the future, ntpdate fails with
'Invalid Argument'
For example:
* current date: passed
root@ubuntu-phablet:~#
** Changed in: canonical-devices-system-image
Status: Confirmed => 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/1516971
Title:
LXC's preserve_ns fails on < 3.8
It is also affecting devel-proposed phone images cf bug 1516971
--
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/1516037
Title:
lxc-start fails with 1.1.5-0ubuntu1
To manage
I confirm that the phone boots successfully after downgrading liblxc1,
lxc and python3-lxc to version 1.1.4-0ubuntu3
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
**
** This bug is no longer a duplicate of bug 1516037
lxc-start fails with 1.1.5-0ubuntu1
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Assignee:
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
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/1508744
Title:
Upgrade to Ubuntu 15.10 Broken:
Here are all the logs you requested. The first dbus-send command hangs and the
second works.
Perhaps it is a coincidence but the problem seems to be triggered when the
systems running out of memory, killed webapp-container and tries to restore
gmail webapp (or maybe any other webapp)
In syslog
*** This bug is a duplicate of bug 1377332 ***
https://bugs.launchpad.net/bugs/1377332
I'm marking this report as duplicate of 1377332 since this is the original
issue and apport was the symptom.
I created bug 1396160 for apport specific issue.
** This bug has been marked a duplicate of
Public bug reported:
Upgrade test from Precise AMD64 to Trusty with nearly all of main
installed.
Note that nova.conf has not been manually modified before upgrade.
From apt-term.log:
Setting up nova-common (1:2014.1~rc2-0ubuntu1) ...
Installing new version of config file
I'm reopening this report, it is still an issue with krb5 1.12+dfsg-
2ubuntu3
** Changed in: krb5 (Ubuntu Trusty)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
New apt.log for P-T upgrade
See also bug 1304702 for an upgrade with the same failure from S to T
** Attachment added: apt_krb5_1.12+dfsg-2ubuntu3.log
https://bugs.launchpad.net/ubuntu/trusty/+source/krb5/+bug/1304403/+attachment/4076761/+files/apt_krb5_1.12%2Bdfsg-2ubuntu3.log
--
You
** Also affects: krb5 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Precise to Trusty - all of main - fails: The package
'postgresql-server-dev-9.1' is marked for removal but it's in the removal
blacklist
+ Precise to Trusty - all of main - fails: Broken transition
Public bug reported:
When option --help is passed as template argument, lxc-create creates
the base directory structure of the container. Then next call to lxc-
create with the same name will fail because the container already
exists.
TEST CASE:
1. $ sudo lxc-create -n test--help -t ubuntu -- -h
** Summary changed:
- lxc-create shouldn't create container when template is called with --help
argument
+ lxc-create shouldn't create container when template is called with --help
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
test--help is the name of the container, it is just a bad name. Sorry
for the confusion.
You can try with
lxc-create -n lp1267367 -t ubuntu -- -h
or any name.
** Changed in: lxc (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of
** Changed in: cherrypy3 (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cherrypy3 in Ubuntu.
https://bugs.launchpad.net/bugs/1244910
Title:
dep8 test failed: missing test
Public bug reported:
During the provisioning of a local VM with cloud-init and parted 2.3.14,
cc_growpart fails in auto grow mode with the following error:
===
2013-08-14 08:07:02,117 - util.py[DEBUG]: Running command ['parted',
'resizepart', '/dev/vda', '1'] with allowed return codes [0]
Public bug reported:
pygopherd is installed and started during autopkgtest of squid3 [1] as
part of the test depedencies. But the run never ends until pygopherd is
stopped/killed.
The service should ever be stopped as part of the test cleanup, or
autopkgtest should kill all the remaining
I'm reopening because I can reproduce it on different hardware, but it
doesn't fail when running the same command twice and it seems a bit
racy. I'm searching for a way to reliably reproduce that problem.
** Changed in: lxc (Ubuntu)
Status: Invalid = Confirmed
** Changed in: lxc (Ubuntu)
This is reproducible on several systems, but only the 1rst time I start
a container when /sys/fs/cgroup/devices/lxc/NAME/ doesn't already
exist.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724404/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc.default.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724406/+files/lxc.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Tags added: apparmor apport-collected
** Description changed:
With kernel 3.10.0 lxc-create fails with the following error:
lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012'
is setup.
lxc-start 1372673552.852 DEBUGlxc_cgroup -
With otto from lp:otto I can reproduce the problem with the command:
$ sudo ./bin/otto -d create -u lp1196518-$RANDOM
~/iso/ubuntu/saucy-desktop-amd64.iso
The write(fd, value, strlen(value)) in do_cgroup_set in cgroup.c fails
with Invalid Argument
If the command is executed a second time with
apport information
** Attachment added: lxc-net.default.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724405/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724403/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxcsyslog.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724407/+files/lxcsyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
For the moment, the workaround is to remove lxc.cgroup.devices.deny from
the config file, which is okay in our case since the machines are just
test hosts, but is not in the general case.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bot-stop-nagging
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724623/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724626/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724622/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724620/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Description changed:
With kernel 3.10.0 lxc-create fails with the following error:
lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012'
is setup.
lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called
for subsys devices
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724618/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724625/+files/Lsusb.txt
--
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/1196518
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724619/+files/CRDA.txt
--
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/1196518
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724621/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724624/+files/Lspci.txt
--
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/1196518
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724631/+files/UdevDb.txt
--
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/1196518
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724628/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724632/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc-net.default.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724634/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724630/+files/RfKill.txt
--
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/1196518
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724633/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxcsyslog.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724636/+files/lxcsyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724627/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc.default.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724635/+files/lxc.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1196518/+attachment/3724629/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Here is a minimal test case to reproduce the problem:
NAME=test-deny-${RANDOM}
echo lxc.hook.mount = /usr/share/lxc/hooks/mountcgroups /tmp/${NAME}.lxc
lxc-create -t ubuntu -n $NAME -f /tmp/${NAME}.lxc -- -r saucy
lxc-start -n $NAME
From what I understand, setting devices.deny or .allow = a is
** Attachment added: fstab
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720321/+files/fstab
--
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/1196518
Title:
** Attachment added: pre-mount.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720323/+files/pre-mount.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Attachment added: config
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720320/+files/config
--
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/1196518
Title:
** Attachment added: post-stop.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720322/+files/post-stop.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
With kernel 3.10.0 lxc-create fails with the following error:
lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012'
is setup.
lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called
for subsys devices name
** Attachment added: saucy-i386-20130701-1012.log.broken
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720325/+files/saucy-i386-20130701-1012.log.broken
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
** Attachment added: pre-start.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720324/+files/pre-start.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I confirm the regression in upstart 1.8-0ubuntu1.1 in Raring which also exists
in 1.8-0ubuntu7 in Saucy caused by a typo in upstart.postinst:
83 elif dpkg --compare-version $UPSTART_VERSION_RUNNING ge 1.6.1;
then
The right option is --compare-versions
--
You received this bug
Public bug reported:
When a container is started with the python API the log file
/var/log/lxc/NAME.log is empty. This is pretty annoying to debug pre-
start hook issues for example.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: lxc 0.9.0-0ubuntu7
ProcVersionSignature: Ubuntu
Confirmed on Saucy with openssh 6.2p1-2
** Changed in: openssh (Ubuntu)
Importance: Undecided = Critical
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Fixed in 0.9.0-0ubuntu1
** Changed in: lxc (Ubuntu)
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/1161827
Title:
lxc-start-ephemeral:
Public bug reported:
In the man page of lxc-start-ephemeral the option '-n' is documented:
SYNOPSIS
lxc-start-ephemeral [-o] [-n] [-d] [--bdir] [--user] [--key]
[--union-type] [--keep-data] [COMMAND]
[...]
[-n] Name of the ephemeral container (defaults to a random suffix).
But
Moving to flash-kernel
LXC do not rootfs modifications from the templates. The proposed fix in
attached branch do the equivalent of then environment variable
FLASH_KERNEL_SKIP and skips flash-kernel run inside LXC container by checking
the result of 'running-in-container'
** Package changed:
** Also affects: walinuxagent (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: walinuxagent (Ubuntu Quantal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
BTW if you don't have a board to reproduce this issue, it is also reproducible
in an armhf container created with:
$ sudo lxc-create -n raring-arm -t ubuntu -- -r raring -a armhf
then install python3-lxc into this container
--
You received this bug notification because you are a member of
Public bug reported:
Raring armv7l
lxc: 0.9.0~rc1-0ubuntu1
flash-kernel: 3.0~rc.4ubuntu29
initramfs-tools: 0.103ubuntu0.7
When the kernel is upgraded inside an armhf LXC container running on armv7l,
the upgrade fails with:
===
Setting up initramfs-tools (0.103ubuntu0.7) ...
update-initramfs:
It is even more annoying because if you specify apt_upgrade: true in a
cloud-config script and there is a package that triggers kernel hooks,
then it breaks the provisioning of the lxc guest.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
it breaks even without that directive.
Another test case to run on a day with a package upgrade that will run
kernel hooks
1. Create the user-data file with the following content:
88888
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: {
Public bug reported:
Raring AMD64
cloud-init 0.7.2~bzr795-0ubuntu1
During the provisioning of an LXC guest with the template ubuntu-cloud,
cloud-init executes the hook resizefs and fails with:
2013-03-26 15:11:09,545 - util.py[DEBUG]: Running resizefs (module
'cloudinit.config.cc_resizefs'
Public bug reported:
Raring ARM
python3-lxc: 0.9.0~rc1-0ubuntu1
On ARM python3 module lxc failed to import. This breaks commands like
lxc-ls
TEST CASE:
1. On an ARM device run the following command:
$ python3 -c import lxc
ACTUAL RESULT:
$ python3 -c import lxc
Traceback (most recent call
Public bug reported:
Currently it is not possible to use the template ubuntu-cloud with armhf
because i386 and amd64 are hard-coded. It is perfectly valid to use this
template with an armhf image if the host architecture is also ARM.
For example the following commands works successfully (after
** Attachment added: cloud-init.log
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1155652/+attachment/3575721/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
When creating a container with template ubuntu-cloud the service
cloud-final is not executed resulting in a incomplete installation.
TEST CASE:
1. Copy the user-data script in attachment to a local directory (you can remove
the package list to go faster)
2. Create a new
It could be another instance of bug 1103881. If I remove the dist-
upgrade from the user-data file cloud-final is executed as expected.
Here are the packages that would be upgraded with a Raring beta1 tarball:
The following NEW packages will be installed:
libudev1
The following packages will
Public bug reported:
During a cloud image initialization, the service cloud-final is never
executed if the cloud-config script contains an upgrade directive and
upstart is part of the upgraded packages:
TESTCASE:
1. Download a cloud image from http://cloud-images.ubuntu.com/raring/ with an
cloud-config script used by lp:auto-package-testing
** Attachment added: cloud-config.txt
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+attachment/3497984/+files/cloud-config.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Attachment added: LP1103881.dmesg
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+attachment/3498350/+files/LP1103881.dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Attachment added: LP1103881.syslog
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+attachment/3498351/+files/LP1103881.syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Public bug reported:
With latest cloud images and the cloud-init script below the user
'ubuntu' cannot sudo. The user is a member of adm but not admin.
==
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: { expire: False }
ssh_pwauth: True
** Changed in: qemu-kvm (Ubuntu Precise)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/997978
Title:
KVM images lose connectivity with
qemu-user-static was installed on the system when I have been able to
reproduce this error (installed on 2012-06-06 from apt log files)
I tried again this morning, and it works correctly. The main difference
is that qemu-user-static has been upgraded from 1.0.50-2012.03-0ubuntu3
to
** Changed in: qemu-linaro (Ubuntu)
Status: Confirmed = 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/1017847
Title:
qemu segfaults when creating an armhf
Public bug reported:
Upgrade to cloud-init 0.7.0~bzr659-0ubuntu1 on Quantal fails with the
following error:
$ sudo apt-get install cloud-init
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
cloud-init
1
The problem persists on Quantal with all updates applied:
$ sudo lxc-create -n quantal-armhf -t ubuntu -- -r quantal -a armhf
[...]
Fetched 22.1 MB in 60s (365 kB/s)
Public bug reported:
On Quantal, after I shutdown an lxc-container the following message is
displayed in syslog every 10s:
Aug 20 21:50:23 sark kernel: [50270.380638] unregister_netdevice: waiting for
lo to become free. Usage count = 1
Aug 20 21:50:34 sark kernel: [50280.617544]
--
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/1039196
Title:
unregister_netdevice: waiting for lo to become free. message after
shutting down an lxc container
To manage
1 - 100 of 518 matches
Mail list logo
