revno: 1204
committer: decker dec...@personal-army
branch nick: 1.6.2
timestamp: Fri 2010-03-05 01:05:00 -0800
message:
fix LP: #525989
** Changed in: eucalyptus
revno: 1207
committer: decker dec...@hawaii
branch nick: 1.6.2
timestamp: Fri 2010-03-05 22:36:44 -0800
message:
fix LP: #532938
** Changed in: eucalyptus
Status:
I'm sorry, this is not something that we can solve in the qemu-kvm
package that is in Ubuntu Main.
Why not? The standard Ubuntu kernel supports capabilities
(CONFIG_SECURITY_FILE_CAPABILITIES). It is obviously not desirable to
have qemu networking broken by default, or to tell users that they
Jules: I think your issue is different - my bug is about permissions but
the device path is ok. Your bug appears to have some weird device path
- causing the device to not be found. Check your XML definition in
/etc/libvirt/qemu/guest1.xml
--
virsh console does not work (/dev/pts/1: Permission
Kees: I know about the wiki page - I'm the one who edited it to note
this issue. It is not true that file capabilities only work in Lucid - I
am using Karmic and it works fine. libcap2-bin is also not a PAM
package. It is also not true that you need to manually add users to
Public bug reported:
Create a domain xml file. There is nothing special required in the VM
description, the following will suffice:
domain type='kvm'
nametest1/name
uuidcd224bdf-9b8a-e2f7-ef3b-ae7acfd30c1d/uuid
memory524288/memory
currentMemory524288/currentMemory
vcpu1/vcpu
os
This looks like a dupe of bug #103010 - tun/tap networking (necessary
for bridging) does not work in qemu for non-root users.
--
virt-manager Network bridge Operation not permitted
https://bugs.launchpad.net/bugs/519572
You received this bug notification because you are a member of Ubuntu
Server
Architecture: amd64
DistroRelease: Ubuntu 9.10
Package: libvirt-bin 0.7.0-1ubuntu13.1
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-server
Uname: Linux 2.6.31-19-server x86_64
UserGroups: adm admin cdrom
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/40685654/Dependencies.txt
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
** Tags added: apport-collected
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not
Tested update from karmic-proposed - appears to work now. Thanks guys!
--
[SRU] winbind authentication fails after karmic upgrade
https://bugs.launchpad.net/bugs/479955
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
from strace:
futex(0x80cde0, FUTEX_WAIT_PRIVATE, 2, NULL11:38:23.962: error :
qemudInitCpus:1243 : failed to set CPU affinity: Operation not permitted
libvir: QEMU error : failed to set CPU affinity: Operation not permitted
qemudInitCpus:1243 does:
if (sched_setaffinity(vm-vcpupids[i],
That qemudInitCpus function is from src/qemu_driver.c : 1243
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you are a member of Ubuntu
Server Team, which is
You'll need some cd iso's in a directory, then see my samba.conf for
how i create the shares. the share names should match the iso file name
but add a iso- prefix. the mount and unmount scripts will handle
creating the share directories and loop mounting and unmounting the iso
files to it
I've
As the author of the culprit I can tell you this is not a bug and is
indeed the intended behaviour.
cheers.
--
'euca-describe-availability-zones verbose' should show vm types for non-admin
users
https://bugs.launchpad.net/bugs/537464
You received this bug notification because you are a member
** Changed in: eucalyptus
Status: New = Won't Fix
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
please move /etc/eucalyptus/cloud.d/scripts to
/usr/lib/eucalyptus/cloud.d/scripts
https://bugs.launchpad.net/bugs/538546
You received this bug
, for
now. Do you have any other suggestions?
cheers.
chris
--
please move /etc/eucalyptus/cloud.d/scripts to
/usr/lib/eucalyptus/cloud.d/scripts
https://bugs.launchpad.net/bugs/538546
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
@Andrew What Thierry says is correct. More specifically, we need to
provide extra information for admins, but for many tools the normal
user's view needs to be the same as that presented by EC2 or many tools
do not work correctly.
--
'euca-describe-availability-zones verbose' should show vm
This bug still exists on karmic
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Public bug reported:
Binary package hint: awstats
It seems that logresolvemerge.pl forks gzip for each of the zipped
logfiles it's reading, but does not reap them when they have finished,
leading to as many zombie processes as there were log files.
While this is not directly harmful, it does
In this case, Fix-Committed should be interpreted as Fix-Released.
--
Query string authentication does not work in some cases
https://bugs.launchpad.net/bugs/46
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
** Changed in: eucalyptus
Status: New = Confirmed
** Summary changed:
- euca-register sets public by default
+ RegisterImage sets public by default
--
RegisterImage sets public by default
https
** Bug watch added: Debian Bug tracker #412941
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412941
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412941
Importance: Unknown
Status: Unknown
--
qemu no tun/tap networking
Chuck: It's completely reproducible, you just need to run an awstats
job:
a) on a busy website's logs
b) using logresolvemerge.pl to bring together the logs from multiple hosts,
e.g. LogFile=/usr/share/doc/awstats/examples/logresolvemerge.pl
/path/to/server1/access.log*
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
** Changed in: eucalyptus
Status: New = In Progress
--
euca-describe-snapshots gives different output than ec2-describe-snapshots
https://bugs.launchpad.net/bugs/547059
You received this bug
So the problem here is that Owner and RestorableBy were misnamed
(OwnerSet and RestorableBySet, respectively). No change should be
needed to euca2ools or boto.
chris
--
euca-describe-snapshots gives different output than ec2-describe-snapshots
https://bugs.launchpad.net/bugs/547059
You
** Changed in: eucalyptus
Status: Triaged = Fix Released
--
If a cluster is deregistered before a SC, the cloud controller will continue
contacting the SC
https://bugs.launchpad.net/bugs/446858
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Is bug #523148 related to apparmor?
--
apparmor denies save and restore
https://bugs.launchpad.net/bugs/457716
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
*** This bug is a duplicate of bug 463684 ***
https://bugs.launchpad.net/bugs/463684
This bug was only fixed for Lucid?
The docs for Karmic here https://help.ubuntu.com/9.10/serverguide/C
/openldap-server.html are still wrong
--
OpenLDAP server instructions out of date: slapd no longer
The documentation for Karmic is still wrong:
https://help.ubuntu.com/9.10/serverguide/C/openldap-server.html
--
openldap sections in ubuntu server guide not updated for packages in karmic
https://bugs.launchpad.net/bugs/463684
You received this bug notification because you are a member of Ubuntu
Also see bug #355400 - OpenLDAP doc page is horrible.
I found this forum post
http://ubuntuforums.org/showpost.php?p=8161118postcount=6 and this
thread http://ubuntuforums.org/showthread.php?t=1313472 to be useful in
getting a server up and running. It's a shame the Ubuntu documentation
is still
The only KVM hardware I have access to at the moment is a production
server. Upgrading it to lucid - which is still in beta - is not really
feasible at the moment.
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
Public bug reported:
Binary package hint: qemu-kvm
Booting Centos 4 with the default 2.6.9 kernel I get a sporadic error
maybe ~5% of the time:
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through
** Changed in: dovecot (Ubuntu)
Importance: Undecided = Wishlist
--
new upstream version available
https://bugs.launchpad.net/bugs/560047
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
--
Ubuntu-server-bugs
** Changed in: apache2 (Ubuntu)
Status: New = Confirmed
--
Upgrade from 2.2.14-5ubuntu6 to 2.2.14-5ubuntu7 results in syntax error,
missing module
https://bugs.launchpad.net/bugs/562370
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: eucalyptus
Importance: Undecided = Wishlist
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
eucalyptus should hold on to console logs as after instance terminated
https://bugs.launchpad.net/bugs/563175
You received this bug
If the diagnosis I posted above is correct, then the frequency with
which this error appears will depend on both the virtualisation platform
(in this case the KVM host) and the guest kernel. We virtualise CentOS
4.4 systems (2.6.9 kernel) and my colleague reports that, in two years
of using
Public bug reported:
Binary package hint: qemu-kvm
Trying to boot this iso:
7d88cd87df509a740d9f47b9bbf1375e *ubuntu-7.10-server-i386.iso
( from http://mirror.linux.org.au/ubuntu-releases/7.10/ )
Domain XML definition is:
domain type='kvm' id='13'
nameubuntu710/name
Confirmed under Karmic.
--
qemu-kvm: ubuntu-7.10-server-i386.iso fails to boot
https://bugs.launchpad.net/bugs/564727
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Apparently this is listed already on the upstream page http://www.linux-
kvm.org/page/Guest_Support_Status#Linux_Family:_Ubuntu.2FDebian_Derivatives
--
qemu-kvm: ubuntu-7.10-server-i386.iso fails to boot
https://bugs.launchpad.net/bugs/564727
You received this bug notification because you are a
Here's the output requested.
$ logwatch --service ftpd-xferlog --range all --detail high --print --archives
Unknown option: print
$ logwatch --service pam_pwdb --range yesterday --detail high --print
Unknown option: print
In each case, logwatch also prints a Usage message (same as logwatch
@Scott: The command is supposed to return the last 64K of console
output. Your results are expected in that case. See the first note
from:
http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?instance-console.html
As for the time, it should be timing out after 20 seconds
I'm having a problem where running opieinfo doesn't work, and I think it's
because it isn't root (and /etc/opiekeys is only readable by root). When I run
opieinfo, I get:
Error opening database! (errno = 13)
--
opieinfo isn't setuid, whilst opiepasswd is
https://bugs.launchpad.net/bugs/61335
continued
And when I run sudo opieinfo username, it correctly gives me my sequence
number and seed.
--
opieinfo isn't setuid, whilst opiepasswd is
https://bugs.launchpad.net/bugs/61335
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to opie
Public bug reported:
After installing the opie-client, opie-server, and libopie-pam packages,
and making the apparently needed edits to /etc/ssh/sshd_config and
/etc/pam.d/ssh, I go on to set it up for my user.
ch...@cowan-laptop:~$ opiepasswd
Adding chris:
You need the response from an OTP
I'm on Ubuntu 9.10 64-bit, and I had the 2.40~dfsg-0ubuntu1 version of
opie-server.
--
opiepasswd does not always generate valid seeds
https://bugs.launchpad.net/bugs/569292
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to opie in ubuntu.
routes as I
don't have a suitable lab environment handy but if you suspect that the
errors generated in the previous version are unlikely to affect that
element directly then we can put this to put as a 'fixed in future
release'.
Thanks again for your help,
Chris
--
Loading capability module
No problem, Chuck. We'll test it on a new Lucid build next week.
It would be great to get this into the LTS.
Chris
--
Quagga reports crash on Karmic
https://bugs.launchpad.net/bugs/523812
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The Debian bug appears to have been marked Fix Released because the
actual qemu package was removed from Debian and replaced with qemu-kvm.
Maybe another bug needs to be opened for that package.
--
qemu no tun/tap networking
https://bugs.launchpad.net/bugs/103010
You received this bug
Public bug reported:
Binary package hint: samba
This doesn't affect me directly but I maintain OpenOffice.org for
Ubuntu.
It appears after getting numerous reports that OOo does not save
properly to cifs mounted filesystems that the cause is due to the fact
the 'nobrl' option is not being used.
** Attachment added: CifsVersion.txt
http://launchpadlibrarian.net/48733924/CifsVersion.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48733925/Dependencies.txt
** Attachment added: SambaInstalledVersions.txt
I found that we do have a way to disable locking entirely for cifs in
OOo that we can use if this bug isn't considered good or safe to fix by
enabling nobrl.
--
OOo needs mount.cifs to default to nobrl if possible
https://bugs.launchpad.net/bugs/582925
You received this bug notification because
The workaround for OOo required updating coreutils to detect cifs which
I have added a patch for in bug 582980.
--
OOo needs mount.cifs to default to nobrl if possible
https://bugs.launchpad.net/bugs/582925
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
The vmbuilder manpage mentions a --tmp option to allow using other than
/tmp but it does not actually work when you try to use it with vmbuilder
kvm ubuntu, this is probably for similar reasons to bug 536940.
** Affects: vm-builder (Ubuntu)
Importance: Undecided
I didn't use ctrl-c vm-builder just bombed out probably due to other
bugs and didn't clean up the resulting mess, and I couldn't figure out
how to clean it up later without rebooting.
--
vm-builder 0.12.3-0ubuntu1 crashes and causes loop devices to be stuck
https://bugs.launchpad.net/bugs/583530
On 07/03/14 10:03, James Page wrote:
I've seen this happen when the server can't resolve its own hostname,
resulting in extra output in the sudo commands that nova uses to create
nbd devices; is that potentially happening in your case as well?
Unless there was a temporary DNS glitch, this
Public bug reported:
The One Convergence NVSD plugin was recently merged but no packaging
exists for the agent
Small patch attached to pkg
** Affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Patch added: patch to create agent package for the NVSD controller plugin
Patch is for the current trusty pkging code
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1293632
Title:
One Convergence NVSD plugin agent missing
To manage notifications about
Public bug reported:
Seen in today's icehouse+trusty packaging (neutron -
1:2014.1+git201404010632~trusty-0ubuntu1)
debian/neutron-plugin-onecovergence-agent.upstart should instead be
named debian/neutron-plugin-oneconvergence-agent.upstart
** Affects: neutron (Ubuntu)
Importance:
Public bug reported:
/var/lib/glance/images and /var/lib/glance/image-cache need to be owned
glance:glance
The current packaging leaves them as this after the postinst:
ls -l /var/lib/glance/
total 52
-rw-r--r-- 1 glance glance 37888 Apr 3 14:30 glance.sqlite
drwxr-xr-x 5 root root4096
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1303617
Title:
Latest curtin version prevents Juju from
** Description changed:
Curtin version: 0.1.0~bzr124-0ubuntu1
Curtin-common: 0.1.0~bzr124-0ubuntu1
Bootstrapping a juju environment on an up-to-date trusty MAAS server
fails. The bootstrap node becomes pingable but never allows connections
to the juju agent.
Cloud init output
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1303903
Title:
sgdisk zap/clear doesn't wipe all GPT tables
To manage notifications about this bug go to:
Public bug reported:
This is with trusty / fence-agents 3.1.5-2ubuntu4
fence-agents supplies /usr/share/fence/fencing.py
The corresponding generated fencing.pyc keeps it from uninstalling
cleanly:
# dpkg --purge fence-agents
(Reading database ... 54169 files and directories currently
Thank you so much for posting this bug and solution Andrew! I just
wasted several hours trying to hunt this down. The number of hacky
solutions being used by people to get around this is really quite
disturbing. I wonder why this 3 character fix didn't make it into
14.04... woulda saved me a
Public bug reported:
chris@chris-661M04-GX-6LH:~$ sudo apt-get install samba4
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libdcerpc-server0 libdcerpc0 libgensec0 libregistry0 libsamba-policy0
I'm running 1.18.3 and I'm still seeing this..
Installed: 1.18.3-0ubuntu1~14.04.1~juju1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1306537
Title:
LXC local provider
Public bug reported:
Package version tested: 2.4.7-1ubuntu4
Expected behavior: site names should be whitespace-tolerant.
[Side note: site names should probably also not require the .conf
extension, as there should be no other normal files in sites-enabled/ --
just filtering out directories (for
** Also affects: dhcp3 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
The linked branch should help with the problem, at the cost of an extra
round-trip to the upstream archive.
** Branch linked: lp:~tribaal/squid-deb-proxy/refresh-ims
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in
Running juju status seems to make my env happy too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1368403
Title:
juju-deployer traceback AttributeError: 'NoneType' object has no
Kapil, I believe lxc and ctsstack have both had this issue..
juju-core:
Installed: 1.20.7-0ubuntu1~14.04.1~juju1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1368403
Title:
As an interim solution:
juju deploy cs:~chris-gondolin/trusty/logrotate
juju set logrotate='logfiles={juju:{path:/var/log/juju/*.log}}'
On 02/10/14 08:38, Haw Loeung wrote:
ubuntu@juju-prod-XX-YYY-machine-0:/var/log/juju$ ls -la
total 19790064
drwxr-xr-x 2 syslog adm 4096 Oct 2
** Changed in: horizon (Ubuntu)
Assignee: (unassigned) = Chris Johnston (cjohnston)
** Changed in: horizon (Ubuntu Trusty)
Assignee: (unassigned) = Chris Johnston (cjohnston)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Public bug reported:
I've recently been setting up a new server using Ubuntu 14.04 to replace
a 12.04 server, and found if not a bug, then at least a breaking change
that doesn't seem to match up intuitively with the documentation.
Both servers have postfix installed. (12.04 has 2.9.6, and 14.04
I guess it's mail that sets the From value, not postfix, so this isn't
a postfix issue then.
** Also affects: mailutils
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
Public bug reported:
If you upload a large file into swift using swift -S (or presumably
the upload() method) then add extra metadata using swift post -m (or
post_object()), the large file manifest metadata is deleted. It
shouldn't do that.
$ swift upload -S 1000 chrisstest
Public bug reported:
The presence of /var/lock/lxc-net causes service lxc-net start to
claim success but actually just do nothing useful.
When the system goes down hard, /var/lock/lxc-net is not removed, fair
enough. This means that systems require manual intervention after
booting.
You can
Good spot, thanks: /var/lock is on /, not a symlink to /var/run.
These machines are provisioned from OVH.com templates. I have raised a
support request with them to see if they are aware of this or are doing
anything strange on purpose.
--
$ cat /proc/self/mountinfo | fgrep lock
27 20 0:19 /
** Changed in: horizon (Ubuntu)
Assignee: (unassigned) = Chris Johnston (cjohnston)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1396318
Title:
Cannot read text in region
** Changed in: horizon (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1396318
Title:
Cannot read text in region selection box
To
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1399016
Title:
MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty
To manage notifications about this
I have tried 1.7.0+bzr3299-0ubuntu2~trusty1 which works fine from a
fresh install of maas but fails to fix the issue when upgrading maas.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
This is fixed since the python code (instead of bash) behaves properly
now. Closing this bug (it's old, bug triage has taken a lot of dust).
Feel free to reopen should this sting you again.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug
This should be fixed in the next version of squid-deb-proxy when it's
released.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in
Public bug reported:
When running
qemu-system-x86_64 -object memory-backend-file,prealloc=yes,mem-
path=/dev/hugepages/libvirt/qemu,size=4096M,id=ram-node0,host-
nodes=0,policy=bind
I got the following error: NUMA node binding are not supported by
this QEMU
Looking at the qemu code, it
Same problem here. I have several machines that run screen -d -m from
an @reboot crontab entry and they all get the error at every boot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to screen in Ubuntu.
Is it possible to conditionally enable it based on architecture? Or
does Ubuntu try to keep the packages configured the same across all
architectures?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
One could argue that the NUMA functionality wasn't intentionally turned
off (it was inherited from debian) and thus re-enabling it would be
fixing a bug.
Just as some background...the kilo release of OpenStack (currently under
way) introduced support for NUMA guests (per-NUMA node hugepage
I don't want to give you more work than necessary.
If we can get it for utopic that'd be great...at least then we'd have
one formally released version of Ubuntu that supported it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu
Public bug reported:
lxc is configured for limited user usage, i.e. the backing store is
always dir. Let's create a container, and snapshot it in its pristine
state:
% lxc-create -n restorebug -t download -- -d ubuntu -r utopic -a amd64
lxc-snapshot -n restorebug
[...]
lxc_container:
Public bug reported:
The nested LXC functionality seems to be broken on Vivid, at least with
the following setup:
Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC)
What happens:
The Inner LXC start command fails when trying to start with:
http://pastebin.ubuntu.com/10682639/
( 631 cgroup
** Tags added: landscape
--
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/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications about this bug go to:
Public bug reported:
autofs prevents my laptop from suspending while mounts are active:
[ 1095.355009] Freezing user space processes ...
[ 1115.369769] Freezing of tasks failed after 20.005 seconds (1 tasks refusing
to freeze, wq_busy=0):
[ 1115.369833] df D 88011f2d34c0 0
So, the new lxcfs in vivid-proposed does *not* solve this particular
problem.
Again, running the daily PPA code solved this, but that means using the
ppa for both vivid and trusty, not just vivid.
Don't hesitate to let me know how I can test more/further versions of
LXC, including git branches,
Okay, so apparently I'm blind. Yeah, code looks fine.
The original thing that had me thinking this was buggy is that I'm
seeing libvirtd crash if I run 'virsh emulatorpin'. Will try and
isolate further and open a different bug report if appropriate.
** Changed in: libvirt (Ubuntu)
Public bug reported:
When starting a Vivid container, it fails to get an IP address. It
believes networking.service was successful, but actually it dies with
SIGPIPE. Restarting networking.service gets an IP, as expected.
Starting networking used to work with pre-vivid containers. I'm
This also occurs for limited user containers, without asking for a btrfs
backing store. This is more of a problem as the limited user can't
delete (or even detect) the subvolume themselves.
On a standard whole-partition-as-btrfs system, as setup by the installer, this
looks like:
ID 257 gen
Ok, so it seems this isn't fixed after all.
Following the exact steps reported in my original message result in a
non-starting container (same error message)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Fix Released = 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/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage
Confirming that latest trusty-updates including python-
compressor_1.4-2ubuntu3~cloud0_all.deb fixed this for me
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1443787
Title:
401 - 500 of 1779 matches
Mail list logo
