Public bug reported:
when bootstrapping a Precise amd64 container the following error is displayed
in the log.
"""
dpkg: regarding .../inetutils-ping_2%3a1.8-6_amd64.deb containing
inetutils-ping:
inetutils-ping conflicts with ping
iputils-ping provides ping and is present and unpacked but no
** Attachment added: "bootstrap.log"
https://bugs.launchpad.net/bugs/996839/+attachment/3137737/+files/bootstrap.log
--
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/996839
Title:
con
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/986159
Title:
squid3 open file descriptors limit is set incorrect
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/930916
Title:
[SRU] amavis start-stop script fails to stop a
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/988520
Title:
After failed auth, subsequent auths in same context f
Public bug reported:
A script created a container which name starts with a '-' ( -lo-
quantal-i386 in this case )
Then calls to lxc-ls and lxc-list fail with:
$ lxc-ls
-lo-quantal-i386
ls: invalid option -- '-'
Try `ls --help' for more information.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
P
--
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/1006332
Title:
lxc-ls fails if name of a container starts with '-'
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Public bug reported:
When multiple containers (template ubuntu) are created simultaneously
only the first container is successfully created, others fail with
"failed to execute template 'ubuntu'"
This is a very common scenario in automated tests.
TEST CASE:
Run the following script with sudo
"""
--
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/1007483
Title:
lxc fails to create containers concurrently
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
Public bug reported:
The template lxc-ubuntu uses a dpkg configuration file to enable a
foreign architecture when qemu-*-static is installed.
Starting from 1.16.2 dpkg added new dpkg --add-architecture and
--remove-architecture commands to track supported architectures.
The configauration file
--
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/1017862
Title:
Migrate to dpkg --add-architecture to track foreign architecture in
template lxc-ubuntu
To manage notifications about thi
** Tags added: rls-q-incoming
** Also affects: lxc (Ubuntu Quantal)
Importance: Undecided
Status: Confirmed
--
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/1017862
Title:
Migr
This is bug 1017862
--
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 container on an amd64 host
To manage notifications about this bu
I get it systematically on my system with latest updates applied. Do you
have any advice how to troubleshoot it ?
--
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 segf
Public bug reported:
With the backing store 'none' the container root filesystem will be a
directory under /var/lib/lxc/container/rootfs
It'd be nice to be able to store the root filesystem in a user defined
location and per container. Setting rootfs in lxc.conf doesn't work with
lxc-create.
--
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/1019398
Title:
Allow creation of container root filesystem in a user defined location
To manage notifications about this bug go to:
https:
Public bug reported:
Current implementation of lxc-wait wait forever until the container reach a
states passed in argument.
If for some reason the container hangs (in my case it was blocking while trying
to bind mount a device) lxc-wait never exit the wait loop.
It'd be nice to have a timeout o
--
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/1020179
Title:
Add a timeout option to lxc-wait
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lx
** Summary changed:
- tomcat7 test failed: AssertionError: ['tcp6 0 0 :::8080 :::* LISTEN 898/java '
+ tomcat7 not running on port 8005 after installation
** Changed in: tomcat7 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Ser
SRU verification for Precise:
I have reproduced the problem with krb5 1.10+dfsg~beta1-2ubuntu0.1 in
precise-updates and have verified that the version of krb5
1.10+dfsg~beta1-2ubuntu0.2 in -proposed fixes the issue.
Marking as verification-done
** Description changed:
I was trying to upgrad
SRU verification for Precise:
I have reproduced the problem with mailman 1:2.1.14-3 in precise and have
verified that the version of mailman 1:2.1.14-3ubuntu0.1 in -proposed fixes the
issue.
Marking as verification-done
** Tags removed: verification-needed
** Tags added: verification-done
--
Public bug reported:
Oneiric to Precise Upgrade i386|amd64
dpkg-query -W -f '${Conffiles}'|grep obsolete reports the following obsolete
files after upgrade:
bind9
/etc/bind/named.conf.options
Reference
https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job/precise-u
I cannot tell for the moment, it is not possible to install an armhf
container on an amd64 host due to gcc 4.7.1-7ubuntu1 failing to build on
armhf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.n
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] unregister_netde
--
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 notificatio
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:
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 upg
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 1.2.0-2012.09-0
** 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 containe
** 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
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
ssh_authorized_keys:
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
out
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, whic
** 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.
https://bugs.l
** 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.
https://bugs
** 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.
https://bugs.launchpad.net/bug
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 co
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 be
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 ca
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 th
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 Ubunt
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: de
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 subscrib
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:
8<8<8<8<8<
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: { ex
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 () failed
Traceback (most recent call last):
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: lx
** 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 walin
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 t
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: non-
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 Ubunt
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 3.9.0-1.5-ge
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 noti
** 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.
https://bugs.launchpad.net/bugs/11
** 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.
https://bugs.launchpad.net/bugs/11
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 lxc/saucy-i386-20130701-
** 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.
https://bugs.launchpad.net/bugs/11
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// 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.
https://bugs.launchpad.net/bugs/
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.
https
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.
https://bugs.launchpad.net/
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 - cg
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.
https://bugs.launch
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.
https://bugs.launchpad.net/bugs/119
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.
https://bugs.launchpad.net/bugs
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.
https://bugs.launchpad.net/bugs/119
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.
https://bugs.launchpad.net/
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.
https://bugs.launchpad.net/bugs/1
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.
https://bugs.launchpad.ne
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.
https://bugs.launchpad.net/bugs
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
T
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.
https://bugs.launchpad.ne
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/119651
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.
https://bugs.launchpad.net/
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.
https://bugs.launchpad.net/bugs/119
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.
https://bugs.launch
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/119651
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.
https://bugs.launchpad.net/bu
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.
https://bugs.launchpad.net/bugs
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.
https://bugs.launchpa
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.
https://bugs.launchpad.net/
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.
https
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
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 children
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] (shell
Thanks for your report.
The relevant error is
---
Starting OpenLDAP: slapd - failed.
The operation failed but no output was produced. For hints on what went
wrong please refer to the system's logfiles (e.g. /var/log/syslog) or
try running the daemon in Debug mode like via "slapd -d 16383" (warn
*** This bug is a duplicate of bug 442941 ***
https://bugs.launchpad.net/bugs/442941
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 442941, so it is being marked as such. Please look at
Thanks for your report.
The relevant error is
---
Setting up slapd (2.4.21-0ubuntu5) ...
Backing up /etc/ldap/slapd.d/ in /var/backups/slapd-2.4.21-0ubuntu4...
done.
Starting OpenLDAP: slapd - failed.
The operation failed but no output was produced. For hints on what went
wrong please refer
*** This bug is a duplicate of bug 514963 ***
https://bugs.launchpad.net/bugs/514963
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 514963, so it is being marked as such. Please look at
We are closing this bug report because it lacks the information we need to
investigate the problem, as described in the previous comments. Please reopen
it if you can give us the missing information, and don't hesitate to submit bug
reports in the future.
To reopen the bug report you can click
Thanks for your report.
The relevant error is
---
Configurando samba (2:3.4.0-3ubuntu5.6) ...
* Starting Samba daemons
...fail!
invoke-rc.d: initscript samba, action "start" failed.
dpkg: erro processando samba (--configure):
sub-processo script post-installation instalado retornou estad
Thanks for your report.
Could you please attach all the files in /var/log/dist-upgrage/ . The
file term.log contains the installation error for the package bacula-
director-mysql
by the way, do you have mysql installed locally and running ?
** Package changed: update-manager (Ubuntu) => bacula (
*** This bug is a duplicate of bug 512096 ***
https://bugs.launchpad.net/bugs/512096
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 512096, so it is being marked as such. Please look at
1 - 100 of 538 matches
Mail list logo
