** Package changed: pip (Ubuntu) = python-pip (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250980
Title:
package pip (not installed) failed to install/upgrade: trying to
overwrite
** Package changed: pip (Ubuntu) = python-pip (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046231
Title:
pip's man page is out of date
To manage notifications about this bug go to:
Public bug reported:
Ubuntu unbundles urllib3 from requests, but the Python metadata for the
python-requests package is missing urllib3 - which needs to be pinned to
the exact version that requests had bundled to avoid failures (at least
while their support model is
Public bug reported:
Ubuntu unbundles urllib3 from requests, but the Python metadata for the
python-requests package is missing urllib3 - which needs to be pinned to
the exact version that requests had bundled to avoid failures (at least
while their support model is
** Changed in: subunit
Importance: High = Wishlist
** Summary changed:
- Test failures if subunit module is installed
+ Test failures if tests are run from an installed copy of subunit
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: subunit
Importance: High = Wishlist
** Summary changed:
- Test failures if subunit module is installed
+ Test failures if tests are run from an installed copy of subunit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: docker.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603244
Title:
docker - Cannot start container
To manage notifications about this bug
It is in suggests. This means that the default behaviour - the happy
path - for users is poor. Ubuntu's kernels support aufs, and aufs is the
default graph driver.
At a minimum I'd suggest recommends.
But aufs-tools is a) tiny - Installed-Size: 228 and b) has no further
deps (other than libc) -
Public bug reported:
Oct 06 14:48:13 linux-dev docker[1317]:
time="2016-10-06T14:48:13.909019154+13:00" level=error msg="Couldn't run
auplink before unmount /var/lib/docker/tmp/docker-aufs-union929083141: exec:
\"auplink\": executable file not found in $PATH"
Oct 06 14:48:29 linux-dev
Public bug reported:
The docs
https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes#Upgrading_from_Ubuntu_16.10
say to use do-release-upgrade but:
$ sudo do-release-upgrade
Checking for a new Ubuntu release
No new release found.
Asking for a development version instead throws a traceback:
$ sudo
Public bug reported:
The docs
https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes#Upgrading_from_Ubuntu_16.10
say to use do-release-upgrade but:
$ sudo do-release-upgrade
Checking for a new Ubuntu release
No new release found.
Asking for a development version instead throws a traceback:
$ sudo
Public bug reported:
When I upgraded to bionic, samba broke. The failure was nonobvious until
I ran it in interactive mode.
testparm should be able to check I think?
anyhow, the config issue was that vfs_aio_linux had been removed, but my
config still said
vfs objects = aio_linux
and testparm
Public bug reported:
Since https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881239 the
vfs_aio_linux driver was removed, but the manpage for was not, which was
very confusing in debugging why things weren't working.
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
Photo of failed machine at https://photos.app.goo.gl/UGofDoh2DdDvNTMM8
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
hint if testing this - add module_blacklist=bcache to your kernel boot
line to boot and reset the metadata :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809748
Title:
8k bcache NULL pointer
** Description changed:
- Photo of failed machine at https://photos.app.goo.gl/UGofDoh2DdDvNTMM8
+ Photo of failed machine, and video of a second lockup at
+ https://photos.app.goo.gl/9qUxysZ4LN1NRdrA7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic
Public bug reported:
Sorry that this is a little vague, I ran into it and didn't run it down
to ground; this was on the cosmic daily server installer build.
hardware: 4 HDD;s, 1 NVMe SSD.
configuration: 1x 512MB ESP per drive, then for the HDDs the second partition
for an mdraid raid5 set.
after doing a wipefs on the cache drive the BUG still occured; wipefs's
the backing drive corrected that. I haven't yet tried wiping just the
backing drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sb.magicok
sb.first_sector 8 [match]
sb.csum 5A3217E583DB5B86 [match]
sb.version 0 [cache device]
dev.label (empty)
dev.uuid2a9e0dfd-acd0-4750-85ae-b347d7580e2b
dev.sectors_per_block 16
dev.sectors_per_bucket
cache superblock info - sb.magicok
sb.first_sector 8 [match]
sb.csum 5A3217E583DB5B86 [match]
sb.version 0 [cache device]
dev.label (empty)
dev.uuid2a9e0dfd-acd0-4750-85ae-b347d7580e2b
dev.sectors_per_block 16
after doing a wipefs on the cache drive the BUG still occured; wipefs's
the backing drive corrected that. I haven't yet tried wiping just the
backing drive.
** Summary changed:
- 8k bcache cache NULL pointer deref on mount / can't boot
+ 8k bcache NULL pointer deref on mount / can't boot
--
I can reproduce adding such a cache triggering an OOPS in 18.10:
make-bcache -o 7741440 -w 8k -B /dev/md127 -C /dev/nvme0n1p2
RIP 0010:create_empty_buffers+0x29/0x110
CallTrace
create_page_buffers
block_read_full_page
check_disk_change
__add_to_page_cache_locked
blkdev_readpage
...
--
You
[ 2938.649666] bcache: register_bcache() error /dev/nvme0n1p2: Bad block/bucket
size
[ 2945.532897] bcache: register_bdev() registered backing device md127
[ 2945.533124] BUG: unable to handle kernel NULL pointer dereference at
0008
[ 2945.533863] PGD 0 P4D 0
[ 2945.535162] Oops:
This should perhaps be moved to the kernel; its not clear that userspace
is doing anything wrong. I've filed #1809748 for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662407
Title:
bcache
Public bug reported:
After creating a bcache cache device with an 8k block size (see
#1662407), a kernel oops happens every time device is probed.
I'm not sure that there is any userspace bug present in #1662407 at all
- it may just be kernel. I've attached a dmesg there, but can't actually
get
Public bug reported:
Install was in a hyperV vm.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: xrdp 0.9.9-1
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Sat Feb 8 08:41:55
I've moved this back to Ubuntu where it belongs - there's no software
changes needed to Launchpad that I can see : making the wiki page better
or clearer etc. If the consensus within Ubuntu is that a different
solution would be better, then please do bring this discussion back to
Launchpad itself.
Just created a new VM and wondered why enhanced mode logins in hyper-V
weren't working and encountered this.
$ uname -a
Linux cognite-lifeless 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor
Can confirm the Azure kernel also fixes enhanced sessions when combined
with appropriate windows side metadata shenanigans.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766857
Title:
[Hyper-V]
Public bug reported:
They seem to pair ok, but don't show up as sound hardware, either
microphone or speaker/headphones.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic
That was when the USB-power/HDMI/DP adapter was plugged in the other side. The
relevant log entries from lower down are:
```
[622581.193592] usb 3-8: new high-speed USB device number 71 using xhci_hcd
[622581.342507] usb 3-8: device descriptor read/all, error -71
[622581.469590] usb 3-8: new
Public bug reported:
Not sure if this should be on kvm or libvirt etc. Anyhow, back in 2017
kvm with nested enabled running hyper-v running vms was documented as
being a thing that works, but trying to make that work today I'm just
getting blue screens and recovery boots of Windows.
cat
Public bug reported:
I have some early dell 4k 60hz screens - the ones which report 2 panels
internally for DP 60Hz - horrid hack I know; I recently got a new XPS
laptop and put Ubuntu on it.
That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens
I bought two slightly different
Thank you for the response. I think these might fall into the third
category of 'VESA is its own special story' ?
I bought both the adapters from the dell configurator at the time I
bought the machine.
This is the part that flakes:
https://www.dell.com/en-us/shop/accessories/apd/470-acfc
The
It is super snappy but doesn't work any better: one of the external
monitors, or the other but not both.
I'm unfamiliar with Wayland, and Googling around has not found any
equivalent tools to xrandr to let me interrogate what the system thinks
is going on, so I've included a screenshot of the
Public bug reported:
https://en.wikipedia.org/wiki/MD5#Collision_vulnerabilities - MD5 is
comprehensively broken at this point. Debsums still claims to be using
md5.
Perhaps it is time to either remove debsums as being insufficient to the
task, or upgrade the hash that debsums uses to a stronger
FWIW I encountered the same Operation not permitted error upgrading from
19.10 to 20.04, in a hyper-V VM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874620
Title:
error: failed to register the
Public bug reported:
I have a MS LifeCam Cinema, which is known to work with Ubuntu in the
past, though forum posts show it no longer working as of ~18.04.
I recently went back to Ubuntu as an actual desktop OS with 20.04 on a
dell xps 13, which has a somewhat average webcam in the lid, so tried
I've looked through all the stacks of running processes and can't see
anything that looks tpg / iscsi related present that could be holding
the mutex - at least per
https://github.com/torvalds/linux/blob/818dbde78e0f4f11c9f804c36913a7ccfc2e87ad
- but perhaps the Ubuntu kernel has some patch that
Public bug reported:
I have a block device exported from zfs, and from time to time it drops
off the network, after which operations such as targetctl restore will
hang.
When it hangs it is stuck in core_tpg_del_initiator_node_acl:
```
[<0>] core_tpg_del_initiator_node_acl+0x8e/0x120
Public bug reported:
```
systemctl suspend-then-hibernate
Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep"
not supported
```
Note the verb change!
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.3-3ubuntu3
ProcVersionSignature: Ubuntu
Still a problem in hirsute
** Attachment added: "bluetooth settings UI"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+attachment/5512392/+files/Screenshot%20from%202021-07-21%2009-43-30.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Well, its hard to run the openstack test suite in a container
*without* qemu-kvm, because python-libvirt depends on libvirt depends
on qemu-kvm.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
On Fri, Dec 21, 2012 at 9:20 AM, Serge Hallyn
1078...@bugs.launchpad.net wrote:
@lifeless,
the upstart job is only responsible for setting up the kvm kernel module
and related kernel settings. With my new proposed change, the upstart
job would detect it's in a container and consider itself
Public bug reported:
$ sudo lxc-start -n lucid-test-lp -lDEBUG
lxc-start: No cgroup mounted on the system
lxc-start: failed to spawn 'lucid-test-lp'
robertc@lifelessdesktop:~$ mount
/dev/mapper/isw_bichcdfhcg_ARRAY0p6 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc
robertc@lifelessdesktop:~$ sudo lxc-start -n lucid-test-lp -linfo -o /tmp/output
lxc-start: No cgroup mounted on the system
lxc-start: failed to spawn 'lucid-test-lp'
robertc@lifelessdesktop:~$ less /tmp/output
lxc-start 1357584051.325 INFO lxc_conf - tty's configured
lxc-start
robertc@lifelessdesktop:~$ sudo lxc-start -n lucid-test-lp -ldebug -o
/tmp/output
lxc-start: No cgroup mounted on the system
lxc-start: failed to spawn 'lucid-test-lp'
robertc@lifelessdesktop:~$ less /tmp/output
lxc-start 1357584371.308 DEBUGlxc_conf - allocated pty '/dev/pts/3'
(4/5)
robertc@lifelessdesktop:~$ cat /proc/self/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=8129608k,nr_inodes=2032402,mode=755 0 0
devpts /dev/pts devpts
cat /etc/mtab
/dev/mapper/isw_bichcdfhcg_ARRAY0p6 / ext4 rw,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
robertc@lifelessdesktop:~$ less /etc/init/cgroup-lite.conf
description mount available cgroup filesystems
author Serge Hallyn serge.hal...@canonical.com
start on mounted MOUNTPOINT=/sys
pre-start script
test -x /bin/cgroups-mount || { stop; exit 0; }
test -d /sys/fs/cgroup || {
robertc@lifelessdesktop:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See
sudo cat /proc/1/mountinfo
15 20 0:14 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
16 20 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
17 20 0:5 / /dev rw,relatime - devtmpfs udev
rw,size=8129608k,nr_inodes=2032402,mode=755
18 17 0:11 / /dev/pts rw,nosuid,noexec,relatime -
sudo cat /proc/1/mountsrobertc@lifelessdesktop:~$ sudo cat /proc/1/mounts
[sudo] password for robertc:
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs
robertc@lifelessdesktop:~$ cat /proc/self/mountinfo
15 20 0:14 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
16 20 0:3 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
17 20 0:5 / /dev rw,relatime - devtmpfs udev
rw,size=8129608k,nr_inodes=2032402,mode=755
18 17 0:11 / /dev/pts
robertc@lifelessdesktop:~$ sudo ls /sys/fs/cgroup
robertc@lifelessdesktop:~$ echo $?
0
robertc@lifelessdesktop:~$ ls -d /sys/fs/cgroup
/sys/fs/cgroup
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
status cgroup-lite
cgroup-lite start/running
--
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/1096771
Title:
error 'No cgroup mounted on the system' but cgroup mounted
To manage
exec 21 1/run/cgroup.debug
exec 21 1/run/cgroup.debug
set -x
cgroup.debug during boot: (.1)
cat /run/cgroup.debug.1
+ grep /sys/fs/cgroup /proc/mounts
+ [ -n ]
+ grep -v ^# /etc/fstab
+ grep -q cgroup
+ grep -q cgroup /proc/mounts
+ [ ! -e /proc/cgroups ]
+ mount -t tmpfs -o
ls /etc/init
acpid.conf console-setup.conf friendly-recovery.conf
modemmanager.conf mountkernfs.sh.conf procps.conf
ssh.conf upstart-socket-bridge.conf
alsa-restore.confcontainer-detect.confgdm.conf
Please open this upstream - using 127.0.0.1 as the visible hostname
would never be sensible IMO.
--
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/1098641
Title:
visible_hostname
(Though I think 3.3.3 may be fixed).
--
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/1098641
Title:
visible_hostname defaults to hostname of first http_port IP, not
get_hostname()
Public bug reported:
Running
sudo lxc-create -n troveclient -t ubuntu -- --bindhome $(whoami) -a i386
is hanging:
lxc-create: No config file specified, using the default config
/etc/lxc/default.conf
I've left it for 15+ m with no further output.
ProblemType: Bug
DistroRelease: Ubuntu
When I ctrl-C it I get
^CDelete subvolume '/var/lib/lxc/troveclient/rootfs'
lxc-create: aborted
--
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/1193594
Title:
lxc-create hanging
To
Oh and yes, / is btrfs, and /var/lib/lxc is on that fs.
--
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/1193594
Title:
lxc-create hanging
To manage notifications about this bug go to:
ps -ef | pastebinit
http://paste.ubuntu.com/5796412/
sudo lsof
http://paste.ubuntu.com/5796420/
Yes, I see no sign of debootstrap happening
While hung:
ps -ef | pastebinit
http://paste.ubuntu.com/5796427/
--
You received this bug notification because you are a member of Ubuntu
Server Team,
*** This bug is a duplicate of bug 1182540 ***
https://bugs.launchpad.net/bugs/1182540
Indeed, that worked - thanks. Will everyone upgrading encounter this? If
so, perhaps a forced flush on new version runs would be a good idea?
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1182540 ***
https://bugs.launchpad.net/bugs/1182540
Ok cool - thanks!
--
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/1193594
Title:
lxc-create
(Note that chunked is a MUST requirement for http 1.1 clients)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/870448
Title:
check_http fails to decode chunked encoding
Public bug reported:
Unpacking replacement mountall ...
dpkg: error processing /var/cache/apt/archives/mountall_2.15.3_i386.deb
(--unpack):
unable to make backup link of `./lib/init/fstab' before installing new
version: Invalid cross-device link
** Affects: lxc (Ubuntu)
Importance:
Public bug reported:
Setting up udev (151-12.3) ...
mknod: `/lib/udev/devices/ppp': Operation not permitted
dpkg: error processing udev (--configure):
subprocess installed post-installation script returned error exit status 1
I realise that this is arguably a config issue, or a udev issue.
Would it be appropriate to open a lucid task on udev?
--
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/902865
Title:
lucid udev upgrade failure on oneiric hosted lxc container
To manage
*** This bug is a duplicate of bug 902190 ***
https://bugs.launchpad.net/bugs/902190
Ah, I missed that (because its fix released and I searched in the
default context).
I will dup this on that bug. Will there be an SRU ?
** This bug has been marked a duplicate of bug 902190
udev fails to
*** This bug is a duplicate of bug 902190 ***
https://bugs.launchpad.net/bugs/902190
On Tue, Dec 13, 2011 at 5:20 AM, Serge Hallyn 902...@bugs.launchpad.net wrote:
*** This bug is a duplicate of bug 902190 ***
https://bugs.launchpad.net/bugs/902190
@Robert:
an SRU to oneiric is under
@gary @serge - that dhcp vs dhcp3 thing is probably a case where the
script needs to handle both: the dhcp client version changed between
lucid and oneiric.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Tags added: easy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tickcount in Ubuntu.
https://bugs.launchpad.net/bugs/625798
Title:
Don't use int constants with a long data type.
To manage notifications about this bug go to:
I don't have time to commit to this bug. Also please ask before
assigning - I am subscribed so can claim things myself :-)
** Changed in: txaws
Assignee: Robert Collins (lifeless) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Hi, the wiki page I was following had no container, it was using an
implicit one or something - that gave me the impression it could just
act as an isolation layer around / , isolating only the things
configured (e.g. dev access, or networking).
That said, lxc-execute with an ephemeral mode looks
Thanks Serge!
--
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/981955
Title:
lxc-execute without config does not seem to work in precise
To manage notifications about this bug go to:
** Changed in: launchpad
Assignee: Martin Pool (mbp) = (unassigned)
** No longer affects: launchpad
--
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/936762
Title:
lxc-ubuntu
the squid patch looks reasonable to me; please forward to the squid-dev
list with a [PATCH] subject.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid3 gets killed
To reproduce, use the ec2 provider in juju (from precise) to talk to the
cluster, and fire up a number of instances in rapid succession - e.g.
8-10.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
On Mon, Jul 23, 2012 at 11:50 AM, Julian Edwards
1027...@bugs.launchpad.net wrote:
To clarify, why would someone very likely would want to query by the
mac address. What's the use case?
If they are staring at a rack full of hardware, one of which has a
fault light lit, the only data they have
This is http://bugs.squid-cache.org/show_bug.cgi?id=2752
** Bug watch added: Squid Bugzilla #2752
http://bugs.squid-cache.org/show_bug.cgi?id=2752
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
Public bug reported:
$ sudo lxc-create -n sso -t ubuntu -- --help
No config file specified, using the default config
/usr/lib/lxc/templates/lxc-ubuntu -h|--help [-a|--arch] [-b|--bindhome user]
[--trim] [-d|--debug]
[-F | --flush-cache] [-r|--release release] [ -S | --auth-key keyfile]
** Changed in: eucalyptus (Ubuntu)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/519062
Title:
Unable to connect to Eucalyptus Service
** Changed in: vmbuilder
Status: Fix Committed = Fix Released
--
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/546536
Title:
--help and --version should be available
*** This bug is a duplicate of bug 1050351 ***
https://bugs.launchpad.net/bugs/1050351
Public bug reported:
lxc-start-ephemeral command
e.g. lxc-start-ephemeral run-my-tests
does 'exit 0' after running the command - see handle_container.
This masks the exit code the command provides, and
Public bug reported:
use lxc-start-ephemeral to start four ephemeral containers
then lxc-ls reports twice as many as it should:
$ ls /var/lib/lxc/
lptests lptests-temp-1FaKWwb lptests-temp-c8jcW0W lptests-temp-qoZ6ncr
lptests-temp-wbvIQLE
jenkins@ip-10-218-67-147:~$ watch lxc-ls
$ lxc-ls
Public bug reported:
Something about qemu-nbd -r -c /dev/nbd0 someimg leaves cruft behind -
subsequent connections get marked readonly.
This is on quantal, haven't checked precise or raring.
To demonstrate:
# use one image
qemu-img create -f qcow2 /tmp/1.qcow2 100M
sudo qemu-nbd -c /dev/nbd2
Quick code read - I think that this block:
if (flags NBD_FLAG_READ_ONLY) {
int read_only = 1;
TRACE(Setting readonly attribute);
if (ioctl(fd, BLKROSET, (unsigned long) read_only) 0) {
int serrno = errno;
LOG(Failed setting
http://paste.ubuntu.com/1352684/ is a debdiff, uploading the source
format 3 patch as well
** Attachment added: Force the readonly bit to the appropriate state on
startup.
** Attachment added: qemu-kvm_1.2.0+noroms-0ubuntu3.dsc
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431097/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3.dsc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: qemu-kvm_1.2.0+noroms-0ubuntu3_source.changes
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431098/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3_source.changes
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Fixed patch - I had my sense inverted...
http://paste.ubuntu.com/1352711/
** Attachment added: Corrected patch
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1077838/+attachment/3431143/+files/qemu-kvm_1.2.0%2Bnoroms-0ubuntu3.debian.tar.gz
** Patch removed: Force the readonly bit to
Public bug reported:
The KSM_ENABLED setting (on by default) for the qemu-kvm job fails under
lxc but the kernel files still appear writable. Thats likely an lxc bug
(either in defaults or device mapping), but there is no need for qemu-
kvm's job to fail if those settings can't be written to
http://paste.ubuntu.com/1356944/ has a debdiff of the (trivial) fix,
adjusted to not version conflict with my nbd patch.
--
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/1078530
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=180886 is the Debian
bug of record. We (squid) need signoff from all contributors ever to add
such an excemption, and I'm fairly sure thats impossible. Work is going
on to use GNUTLS I think.
** Bug watch added: Debian Bug tracker #180886
Public bug reported:
I'm on oneiric and ran
sudo lxc-create -n ensemble-0 -t ubuntu -f /etc/lxc/local.conf -- -r oneiric
the config file is
lxc.network.type=veth
lxc.network.link=virbr0
lxc.network.flags=up
Setting up apt (0.8.15.4ubuntu2) ...
ERROR: Can't find the archive-keyring
Is the
Seems to be coming from apt-key update being called in apts postinst;
which is perhaps a bit crackful given theres no guarantee of being
online.
** Package changed: lxc (Ubuntu) = apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
The following recipe appears to reliably nuke a lxc i386 lucid container
running on a oneiric amd64 host:
lxc-start -n name
(login)
sudo poweroff -n
- hangs
in another terminal
sudo lxc-stop -n name
then
sudo lxc-start -n name
shows
sudo lxc-start -n lucid-test-lp
init:
Further investigation shows that just:
logging into the new container
installing some packages (see https://dev.launchpad.net/Running/LXC)
and calling lxc-stop from another terminal
will cause this.
Am progressing with shorter and shorter tests
** Summary changed:
- container start failure
1 - 100 of 1475 matches
Mail list logo
