Public bug reported:
$ python3
Python 3.4.2 (default, Oct 8 2014, 13:18:07)
[GCC 4.9.1] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> __requires__ = "stevedore >= 1.0"
>>>
Thanks for reporting this bug.
It looks like virstinst is creating wrong xml, so marking this as
affecting the virstinst package.
** Package changed: libvirt (Ubuntu) => virtinst (Ubuntu)
** Changed in: virtinst (Ubuntu)
Importance: Undecided => High
--
You received this bug notification be
Could you please show screenshots as you walk through the 'add hardware'
wizard?
Also please tell us which release you are on.
** Package changed: libvirt (Ubuntu) => virt-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: qemu (Ubuntu)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed
Public bug reported:
minor typo in "man uvt-kvm". Says "--userdata" instead of the proper
"--user-data" also uploading branch with patch
** Affects: uvtool (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server T
Verified this with a horizon deployment through the juju bundle
deployment. Tested Chrome & Firefox, things look great.
** 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
Fix proposed to branch: master
Review: https://review.openstack.org/141259
** Changed in: cinder
Assignee: Tony Breeds (o-tony) => John Griffith (john-griffith)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https
I'd elevate this to high so it matches nova and ubuntu but I don't have
permissions to do so.
** Changed in: cinder
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpa
I'm happy to tackle to also fix cinder with a version of the nova fix
(for consistency). I propose waiting until the nova fix lands
** Changed in: cinder
Assignee: (unassigned) => Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
Change abandoned by Mike Perez (thin...@gmail.com) on branch: master
Review: https://review.openstack.org/95797
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinderclient in Ubuntu.
https://bugs.launchpad.net/bugs/1266127
Titl
It seems fixed now with 1.7.1.
u@ubuntu:~$ sudo apt-cache policy maas
maas:
Installed: 1.7.0+bzr3299-0ubuntu3~trusty1
Candidate: 1.7.1~rc1+bzr3322-0ubuntu1~trusty1
Version table:
1.7.1~rc1+bzr3322-0ubuntu1~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/testing/ubuntu/
I've given up on ubuntu having a good version and just wrote my own script
to get the newest go-lang installed.
Kind of unfortunate to require this effort.
On Thu, Dec 11, 2014 at 1:49 PM, Jack Twilley <1362...@bugs.launchpad.net>
wrote:
> https://blog.golang.org/go1.4
>
> Go version 1.4 has now
https://blog.golang.org/go1.4
Go version 1.4 has now been released. I'm afraid to change the bug
title. :-)
Jack.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1362741
Title:
upd
** Changed in: maas
Milestone: 1.7.1 => 1.7.2
--
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/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about
** Changed in: maas
Milestone: 1.7.1 => 1.7.2
--
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/1381058
Title:
Upgrading introduces a spurious cluster controller
To manage notificati
** Changed in: maas
Milestone: 1.7.1 => 1.7.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/1382774
Title:
Postgresql installation for MAAS fails on locales missing lan
Was not able to reproduce this on my utopic host or a trusty VM. James
will try to come up with a reproducer.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
By default, saslauthd caches credentials.
The cache and timeout are set by the -c and -t command line options.
You can disable caching by removing the -c from /etc/default/saslauthd,
or adjust the timeout from the default 28800 seconds by adding -t to it.
** Information type changed from Private
** Tags added: smoosh
--
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/1350947
Title:
apparmor: no working rule to allow making a mount private
To manage notifications about this bug go
** Tags added: landscape smoosh
--
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/1401658
Title:
Host veth mtu not preserved during container reboot
To manage notifications about this bug
Public bug reported:
LXC containers configured with lxc.network.mtu = 9000
On start/restart using lxc-* commands, the mtu on the host and in
container interface is correctly set to 9000.
However, if the container is rebooted internally, the mtu of the veth on
the host resets to 1500, whilst the
** Also affects: cinder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
I've successfully run our openstack regression test suite against
trusty-proposed. Billy or Chris, when you have a moment please test
this and update the bug appropriately.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ub
This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu1.9
---
qemu (2.0.0+dfsg-2ubuntu1.9) trusty-security; urgency=medium
* SECURITY UPDATE: code execution via savevm data
- debian/patches/CVE-2014-7840.patch: validate parameters in
arch_init.c.
- CVE-2014-7840
This bug was fixed in the package qemu-kvm - 1.0+noroms-0ubuntu14.21
---
qemu-kvm (1.0+noroms-0ubuntu14.21) precise-security; urgency=medium
* SECURITY UPDATE: code execution via savevm data
- debian/patches/CVE-2014-7840.patch: validate parameters in
arch_init.c.
- CV
This bug was fixed in the package qemu-kvm - 0.12.3+noroms-0ubuntu9.26
---
qemu-kvm (0.12.3+noroms-0ubuntu9.26) lucid-security; urgency=medium
* SECURITY UPDATE: code execution via cirrus vga blit regions
(LP: #1400775)
- debian/patches/CVE-2014-8106.patch: properly validate
This bug was fixed in the package qemu - 2.1+dfsg-4ubuntu6.3
---
qemu (2.1+dfsg-4ubuntu6.3) utopic-security; urgency=medium
* SECURITY UPDATE: code execution via savevm data
- debian/patches/CVE-2014-7840.patch: validate parameters in
arch_init.c.
- CVE-2014-7840
* S
Nick, no documentation of the behavior does not mean the behavior still
exists in the code, so it is not enough.
--
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/1022612
Title:
private i
** Changed in: nova
Status: Confirmed => Opinion
--
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/1167073
Title:
nova-network should increase nf_conntrack_max
To manage notificat
Is this still valid, hasn't been touched in years.
** Changed in: nova
Status: Confirmed => Incomplete
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
ht
Workaround resolution:
apt-get install -y puppet
# installs puppet dependency: facter-1.7.5-1ubuntu1
gem install facter
# installs latest facter gem, 2.3.0 where the ec2_* facts in VPC are restored
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
As a result of the "slave" versus "make-slave" revelation, I've created
two upstream AppArmor bugs. The first is for the AppArmor documentation
being wrong about the acceptable mount option strings (bug #1401619).
The second is for the AppArmor parser accepting unknown mount option
strings (bug #14
This bug was fixed in the package qemu - 2.1+dfsg-4ubuntu6.2
---
qemu (2.1+dfsg-4ubuntu6.2) utopic-proposed; urgency=medium
* Apply two patches to fix intermittent qemu-img corruption
(LP: #1368815)
- 501-block-raw-posix-fix-disk-corruption-in-try-fiemap
- 502-block-raw-
Apparmor is recognizing "make-slave', not "slave". While apparmor will
be updated to accept 'slave' we should update the lxc policies to use
'make-slave' in the meantime.
Assigning this to Stéphane as he hasn't yet had a chance to show me the new
git-dpm packaging process :)
** Changed in: lxc
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
It appears that as tyhicks pointed out this is a dup of bug 1350947.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
hah, as pointed out in comment #4 of that bug. Marking this as a dup
** This bug has been marked a duplicate of bug 1350947
apparmor: no working rule to allow making a mount private
--
You received th
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
James if you'd like to increase the priority of bug 1350947 please do
so.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:/
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
The only way I can get this to work is to add
"mount,"
to /etc/apparmor.d/abstractions/lxc/start-container
If I add something like
"mount options=slave"
"remount options=slave"
that does not suffice.
-
** Description changed:
- When running facter (1.6.5-1ubuntu1.2) from Ubuntu 12.04 LTS on an
- EC2-instance inside AWS VPC, no ec2-facts are shown. This bug is already
- reported upstream: http://projects.puppetlabs.com/issues/7559
+ When running Facter (1.6.x or 1.7.x) from Ubuntu 12.04 LTS or 14
This is still a problem on Ubuntu 14.04.1 with puppet 3.4.3 and facter 1.7.5.
Interestingly, on Amazon Linux 2014.09 with puppet 2.7.25 and facter 1.6.18,
the EC2_* facts are present.
The latest version of the gem appears to have completely refactored the
ec2.rb facts:
https://github.com/puppetla
Robie: I've verified that the Vivid version works fine. Can I ping you
re getting the SRU done for Trusty?
--
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/1366174
Title:
apache2 SEGV wi
Public bug reported:
We are working on an Ubuntu 14.04 tls server with qemu & libvirt.
We are running a virtual machine and we make snapshots through:
virsh snapshot-create-as $name $date --diskspec
$device,file=$path$name"/"$name"_"$date"."$extension --disk-only
--atomic
Everything good so far
I would have assumed systemd is on neither. Since it seems to be the
same all the way since Trusty (at least).
--
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/1401148
Title:
Re/starting
Public bug reported:
$ qemu-img convert -O raw trusty-server-cloudimg-arm64-uefi1.img ts.img
$ sudo parted ./ts.img -- print
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean
that another operating system believes the disk is smaller. Fix, by moving t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: spamassassin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.n
Is this only happening when systemd is in the container, or when systemd
is on the host?
--
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/1401148
Title:
Re/starting an lxc container corru
lxc-start.strace.3093:clone(child_stack=0x7fff7fbc0290,
flags=CLONE_NEWNS|CLONE_NEWUTS|CLONE_NEWIPC|CLONE_NEWPID|CLONE_NEWNET|SIGCHLD)
= 3131
lxc-start.strace.3093:open("/proc/3131/ns/net", O_RDONLY) = 16
lxc-start.strace.3093:waitid(P_PID, 3131, {}, WNOHANG|WEXITED|WNOWAIT, NULL) =
--
You
This is the output of "apparmor_parser -p /etc/apparmor.d/usr.bin.lxc-
start" on Vivid with 3.16 kernel.
** Attachment added: "aa-parser.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+attachment/4278746/+files/aa-parser.txt
--
You received this bug notification because yo
When stracing lxc-start one of the sub-processes is doing the access.
This is the strace of that sub-process.
** Attachment added: "lxc-start.strace.3131"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+attachment/4278745/+files/lxc-start.strace.3131
--
You received this bug no
so I think it's some systemd handling which does that. LXC unshares the
mnt namespace which gets it a copy of the host's, then it's doing some
magic (rprivate I believe) to get things working under systemd, then
mounts what it needs, unmounts everything else and pivot_root.
lxc itself has no code
** Summary changed:
- squid3 gets killed at startup with dnsmasq and no networkmanager
+ squid3 gets killed at startup with dnsmasq
--
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/9783
Stop the bot.
--
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/1401148
Title:
Re/starting an lxc container corrupts all network namespaces on the
same physical host
To manage notificat
Stop the bot.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148
Title:
Re/starting an lxc container corrupts a
So for now I added also a task for the kernel, though the truth (if such a
thing exists) could be somewhere between. Serge, Stephane, what we probably
need to figure out is what exactly lxc-start tries to get done when slave
mounting /run/netns. And somehow it might be possible that it needs imp
At least make it a medium priority question on installing the package.
--
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/1357326
Title:
Make default VCS git
To manage notifications
ipv6 to ipv6 rdesktop is possible.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/657270
Title:
Netstat not displaying all listening ports when using IPv4 and IPv6
To manage noti
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1401148
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1401148
Title:
Re/starting an lxc container corrupts all netwo
Can you please attach the output of
apparmor_parser -p /etc/apparmor.d/usr.bin.lxc-start
--
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/1401148
Title:
Re/starting an lxc container co
** Changed in: python-logutils (Ubuntu)
Assignee: Liam Young (gnuoy) => (unassigned)
** Changed in: python-logutils (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-logutils i
*** This bug is a duplicate of bug 1370247 ***
https://bugs.launchpad.net/bugs/1370247
** This bug has been marked a duplicate of bug 1370247
glance_store rbd driver accidentally changed chunk size units
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
Please merge python-logutils 0.3.3-2 (main) from Debian unstable (main)
** Affects: python-logutils (Ubuntu)
Importance: Undecided
Assignee: Liam Young (gnuoy)
Status: In Progress
** Changed in: python-logutils (Ubuntu)
Status: New => In Progress
*
Hi James,
thanks for the review. My fix to make unit test failures fatal to build
has landed in the authors src on bitbucket but hasn't made it into the debian
package yet. I've marked this bug as invalid and raise a merge bug
** Changed in: python-logutils (Ubuntu)
Status: New => In
** Also affects: apparmor (Ubuntu Vivid)
Importance: High
Status: Invalid
** Also affects: linux (Ubuntu Vivid)
Importance: High
Assignee: John Johansen (jjohansen)
Status: Fix Released
** Also affects: docker.io (Ubuntu Vivid)
Importance: High
Status: Invalid
Hi Marius,
you can download new deb Files from vivid and install it.
http://packages.ubuntu.com/vivid/all/python-urllib3-whl/download
http://packages.ubuntu.com/vivid/all/python-urllib3/download
http://packages.ubuntu.com/vivid/all/python3-urllib3/download
Befor you test it again "virtualenv --
You have been subscribed to a public bug:
I'm trying to create a virtualenv with PyPy, using pypy 2.3.1+dfsg-1
from utopic/universe. This fails:
$ virtualenv -p pypy /tmp/pypy
Running virtualenv with interpreter /usr/bin/pypy
New pypy executable in /tmp/pypy/bin/pypy
Installing s
SRU justification:
Impact: Without starting a QEMU instance for dom0 it is not possible to
use advanced disk image types for PV guests because pygrub then cannot
peek into them to pick kernel images to start. However this setup is the
default for nova-xen (openstack).
Fix: Picking up changes from
SRU justification:
Impact: As soon as dom0 starts qemu it will try to locally attach
QCOW(2) images in case a PV guest is using those. This results in the
described errors and sometimes the whole host is rendered unusable.
Fix: Cherry picking an upstream patch (which was done already for Vivid)
r
** Also affects: snappy-ubuntu
Importance: Undecided
Status: New
** Changed in: snappy (Ubuntu)
Status: New => Invalid
--
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/1
*** This bug is a duplicate of bug 1401417 ***
https://bugs.launchpad.net/bugs/1401417
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1401417, so is being marked as such.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nspr in Ubuntu.
https://bugs.launchpad.net/bugs/1401419
Title:
package libnspr4-0d:amd64 2:4.10.7-0ubuntu0.14.04.1 failed to
install/upgrade: pac
*** This bug is a duplicate of bug 1401417 ***
https://bugs.launchpad.net/bugs/1401417
Public bug reported:
/
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnss3-1d:amd64 2:3.17.1-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.1
Public bug reported:
I don't know.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnspr4-0d:amd64 2:4.10.7-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
AptdaemonVersion: 1.1.1-1ubu
73 matches
Mail list logo
