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.
** 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:
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
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'
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
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
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:
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
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
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
** 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'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
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
*** This bug is a duplicate of bug 868176 ***
https://bugs.launchpad.net/bugs/868176
** This bug is no longer a duplicate of bug 865219
update-alternatives: error: cannot stat
/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
** This bug has been marked a
*** This bug is a duplicate of bug 868176 ***
https://bugs.launchpad.net/bugs/868176
** This bug is no longer a duplicate of bug 865219
update-alternatives: error: cannot stat
/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
** This bug has been marked a
*** This bug is a duplicate of bug 868176 ***
https://bugs.launchpad.net/bugs/868176
** This bug is no longer a duplicate of bug 865219
update-alternatives: error: cannot stat
/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
** This bug has been marked a
*** This bug is a duplicate of bug 868176 ***
https://bugs.launchpad.net/bugs/868176
** This bug has been marked a duplicate of bug 868176
package lightdm-gtk-greeter 1.0.1-0ubuntu1 failed to install/upgrade:
lightdm-gtk-greeter: config file '/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf'
*** This bug is a duplicate of bug 868176 ***
https://bugs.launchpad.net/bugs/868176
** This bug is no longer a duplicate of bug 865219
update-alternatives: error: cannot stat
/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
** This bug has been marked a
*** This bug is a duplicate of bug 868176 ***
https://bugs.launchpad.net/bugs/868176
** Summary changed:
- update-alternatives problem with lightdm-gtk-greeter
+ update-alternatives: error: cannot stat
/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
** Also
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/862129
Title:
samba postrm depends on packages not guaranteed to be configured
To manage
setting importance to High as it breaks puppet deployments.
** Changed in: facter (Ubuntu)
Importance: Undecided = High
** Changed in: facter (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Package changed: update-manager (Ubuntu) = samba (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/873691
Title:
upgrading to Kubuntu 11.10 failed
To manage notifications
SRU verification for Natty:
I have reproduced the problem with whois 5.0.11ubuntu1 in natty and have
verified that the version of whois 5.0.11ubuntu1.1 in -proposed fixes the issue.
Marking as verification-done
--
You received this bug notification because you are a member of Ubuntu
Server
Additional note:
I tried with linux.ua and 5.0.11ubuntu1.1 returns the right record while
5.0.11ubuntu1 doesn't.
** 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
** 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 etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/872553
Title:
[SRU] upon creating a node via juju orchestra,
** 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 etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/791839
Title:
etckeeper runs bzr without a locale set from
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/879052
Title:
user dir binding breaks on nonexistent user
To
** 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 clamav in Ubuntu.
https://bugs.launchpad.net/bugs/882031
Title:
SRU tracking bug for clamav 0.97.3
To manage
** 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 facter in Ubuntu.
https://bugs.launchpad.net/bugs/732953
Title:
can_connect function inside ec2.rb always return
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/894377/+attachment/2607001/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/894377/+attachment/2607002/+files/syslog
** Also affects: mysql-5.1 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: mysql-5.1 (Ubuntu Precise)
Assignee: (unassigned) =
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/894377
Title:
mysql-server failed to upgrade to Precise. mysql main process (4700)
terminated with status 7 respawning
To manage
** Attachment added: dist-upgrade.tgz
https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/894377/+attachment/2607000/+files/dist-upgrade.tgz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
Public bug reported:
Automated Server Upgrade test 2025
this test failed this morning while upgrading the package mysql-server-5.1 on
both amd64 and i386. The upgrade process hangs at Setting up mysql-server-5.1
(5.1.58-1ubuntu3) ...
and the following message is displayed continuously in
Thanks for your report.
I can't reproduce this error with the latest version of
odbcinst1debian2. Is it still an issue for you ?
** Changed in: unixodbc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Autoupgrade testing from oneiric to precise
The base image is a fresh and up to date oneiric installation. During upgrade
the user is prompted to update the following unmodified configuration file:
/etc/cron.d/mailman
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/911244
Title:
prompt to change unmodified conf file /etc/cron.d/mailman during
upgrade from oneiric to precise
To manage
** Attachment added: mailman.dpkg-dist
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/911244/+attachment/2655484/+files/mailman.dpkg-dist
** Changed in: mailman (Ubuntu)
Importance: Undecided = Medium
** Also affects: mailman (Ubuntu Precise)
Importance: Medium
Status:
Public bug reported:
During cleanup vm-build tries to remove loop0ppN but the real name is
loop0pN
TEST CASE:
1. In a terminal run the command:
ubuntu-vm-builder kvm oneiric
EXPECTED RESULT:
An oneiric VM
ACTUAL RESULT:
VM build fails with
File /usr/bin/ubuntu-vm-builder, line 24, in module
** Also affects: vm-builder (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: vm-builder (Ubuntu Precise)
Importance: Undecided = High
** Changed in: vm-builder (Ubuntu Precise)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
** Tags added:
output of ubuntu-vm-builder kvm oneiric
** Attachment added: vmbuilder.log
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/911704/+attachment/2656890/+files/vmbuilder.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
bug introduced by this commit
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/vm-builder/precise/revision/48#VMBuilder/disk.py
** Summary changed:
- vmbuilder fails with device-mapper: remove ioctl failed: No such device or
address - Wrong device name loop0pp1
+ vmbuilder fails
not only the name is wrong but also the devices are already removed when
dmsetup tries to remove them.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/911704
Title:
vmbuilder
** Tags added: iso-testing qa-daily-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/904681
Title:
precise amd64 minimal-virtual install is oversized
To manage notifications about this bug
** Also affects: libnss-ldap (Ubuntu Precise)
Importance: High
Status: New
** Summary changed:
- libnss-ldap:1386 does not install
+ libnss-ldap:i386 does not install
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/873243
Title:
nova-compute-xen depends on xen-linux-system which
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/911704
Title:
vmbuilder fails with device-mapper: remove ioctl failed: No such
device or address -
first failure found on ubuntu-server images build 20120121
** Tags added: rls-mgr-p-tracking
** Also affects: bind9 (Ubuntu Precise)
Importance: High
Status: Triaged
** Changed in: bind9 (Ubuntu Precise)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
--
You
Please don't change the status without a comment
** Changed in: bind9 (Ubuntu Precise)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/920202
Public bug reported:
After upgrade from Oneiric to Precise squid is misconfigured and returns
only 403
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: squid3 3.1.18-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules:
** Also affects: squid3 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: squid3 (Ubuntu Precise)
Importance: Undecided = High
** Changed in: squid3 (Ubuntu Precise)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
** Tags added:
This is a transition from squid2.7 to squid3.
Here are the upgrade logs
** Attachment added: dist-upgrade.tgz
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/924739/+attachment/2706198/+files/dist-upgrade.tgz
--
You received this bug notification because you are a member of Ubuntu
squid.conf
It was modified to use apt-cacher-ng to cache .deb packages.
** Attachment added: etc.squid.tgz
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/924739/+attachment/2706200/+files/etc.squid.tgz
--
You received this bug notification because you are a member of Ubuntu
Server
1 - 100 of 518 matches
Mail list logo
