It never happened again (and may have been a misuse involving immortal
sudo subprocesses but I'm blurry on the details), marking invalid but
fixed released may be correct as well.
** Changed in: lxc (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are
@Chris: Thanks !
I had to implement a different scheme not using nested containers but
still requiring lxc-1.1.2.
I'll give nested containers another shot asap.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I run into the same issue on a vivid host while trying to start a trusty
nested container from inside a trusty container.
--
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:
@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on
the outer container ?
--
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
Building on top of the added test (test_cloud_config_archive), using the
following breaks (the yaml can't be parsed):
message = '''#cloud-config-archive
- content: #cloud-config\napt_update: true\napt_upgrade: true\nchpasswd:\n
expire:\
\ false\nmanage_etc_hosts:
** Package changed: snappy (Ubuntu) = snappy-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to snappy in Ubuntu.
https://bugs.launchpad.net/bugs/1443557
Title:
snappy update error message 'already locked' is confusing
To
Public bug reported:
Running 'snappy update' may issue an 'already locked' error message.
mvo explained that this is caued by 'autopilot' running in the
background and 'tail /var/log/syslog' contains more details (indeed it
does).
The message is confusing for a newcomer.
** Affects: snappy
Sorry for not providing timely feedback there (nor a reproducing env).
Truth is this hasn't recur so marking invalid seems fair.
Thanks for the help nevertheless, if it happens again, I'll make sure to
have such a reproducing env before re-opening this bug.
--
You received this bug
Public bug reported:
and even 'lxc-stop -k -t timeout' can hang :-/
The context is an automated test run with otto using a lxc-container
trigerring a kernel crash on the host.
The host is still alive and so is the container but trying to implement
a catch-all to stop a container left running is
@Serge: I encounter the issue in
http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-
intel/2465/console
which runs on intel. I will try to reproduce locally (this happened in
the ci lab).
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Testing done, the bug is present in 3.8.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1157589
Title:
kvm hangs for freebsd guests since raring upgrade
To manage notifications about
Fixed upstream, great. Rough estimate about when this will land for
raring ?
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1157589
Title:
kvm hangs for freebsd guests since raring upgrade
To
** Attachment added: Freebsd9 xml description
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+attachment/3588233/+files/freebsd9.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
** Attachment added: vrish capabilities output
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+attachment/3588234/+files/virsh.capabilities
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
As discussed on IRC, doing:
sudo kvm -hda freebsd-8.0-64bits.qcow2 -serial stdio
doesn't trigger the bug, I'll investigate on which part of the xml is causing
the issue and report here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
apport information
** Tags added: apport-collected third-party-packages
** Description changed:
Until I upgraded to raring, freebsd guest has been one of my most stable
guest under kvm (and previously under vbox for that matter).
Since the upgrade to raring, my existing guest hangs
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1157589/+attachment/3588504/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
Public bug reported:
Until I upgraded to raring, freebsd guest has been one of my most stable
guest under kvm (and previously under vbox for that matter).
Since the upgrade to raring, my existing guest hangs very early in the
boot process ending with the following in
I encounter the same issue while trying to use the same image for juju.
If I use a precise image, cloud-init-output.log ends with:
Installed /usr/lib/juju/juju
Processing dependencies for juju==0.5
Finished processing dependencies for juju==0.5
% Total% Received % Xferd Average Speed
@Adam: Confirmed, using DEBUG produces output \o/
But DEBUG may not be appropriate in the long run ?
Anyway, I'm out of trouble.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
For the record, trying to apply the moral equivalent of the proposed
patch to my config files I still don't get anything written to the log
file :-/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
Public bug reported:
While trying to uninstall keystone (to start from a clean slate),
synaptic complains:
(Reading database ... 304179 files and directories currently installed.)
Removing keystone ...
dpkg: error processing keystone (--remove):
subprocess installed pre-removal script returned
Forget the re-install part, I renamed /etc/keystone while hammering,
restoring its proper name allow the re-installation to complete.
Removing the package is still not possible
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone
@Soren: Sorry for the confusing bug report, keystone-manage is called
while re-installing, not while removing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/961277
Title:
Cannot
** Changed in: keystone (Ubuntu)
Assignee: (unassigned) = Vincent Ladeuil (vila)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/922954
Title:
keystone has a missing dep
Please re-open this bug as the dependency was added to the wrong
section, see
https://code.launchpad.net/~vila/ubuntu/precise/keystone/fix-922954/+merge/91457
for an hopefully proper fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
27 matches
Mail list logo
