Guys this fix really needs to be in trusty too.
--
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/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications
All right, just found a simple workaround for trusty. Just install the
net-tools package and lo will be brought up correctly.
--
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/1375821
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.
Hi Curtis,
To my understanding juju-1.22.1 is not in -updates yet not because we
don't want this but because it needs to be in -proposed for 7 days
before reaching -updates. This is a standard practice for SRUs. I expect
to see it landed into -updates until the end of this week. If juju team
** 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 openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1451134
Title:
Default connection parameters fails
** 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
wont-fixing the nova side will leave it broken for quite some time
until the backport has made its way into all relevant distro images. I'd
prefer to add your patch into nova code as workaround for older libvirt
versions.
--
You received this bug notification because you are a member of Ubuntu
i'm looking at http://bazaar.launchpad.net/~curtin-
dev/curtin/trunk/view/head:/helpers/common#L330 (which admittedly i just
committed to, but did not change this general behavior).
and i'm not really sure how it can get there...
partition_main() line 374 calls wipedev. wipedev wipes start and
Hi Oleg.
I am happy to continue with 1.22.1 going into updates first. I am a
little concerned about perception of churn in Trusty. Juju 1.22.4 will
arrive a few weeks later. What of 1.23.x? 1.23.3 is currently proposed,
but Core's desire to put 1.22.4 in means we delay the .1.23 going into
yeah. but net-tools is deprecated, so this really should be fixed in all
releases. :)
--
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/1375821
Title:
ifupdown doesn't bring loopback
Public bug reported:
1) the config in /etc/default/openvpn seems to not be respected, specifically
the value of the OPTARGS is not used.
-- it can be set in the vpn config file
2) the package uml-utilities is not installed and tunctl seems to be
required by the openvpn start procedure.
This was fixed in trusty-updates in
1.0.1~dfsg1-0ubuntu1~ubuntu0.14.04.1, and Utopic, Vivid and Wily all
also have Docker = 1.0.
** Changed in: docker.io (Ubuntu Trusty)
Status: Fix Committed = Fix Released
** Changed in: docker.io (Ubuntu)
Status: New = Fix Released
--
You
I see Recommends: apparmor and Depends: libapparmor1 in docker.io
1.5.0~dfsg1-1ubuntu2 that is in Wily, so I presume Fix Released?
For Trusty and Utopic, I expect this to be fixed by the planned backport
of Wily's docker.io package to Trusty, Utopic and Vivid.
** Changed in: docker.io (Ubuntu)
Public bug reported:
1.6.1 is available in Debian. This needs to be merged to Wily and
backported in SRUs to Trusty, Utopic and Vivid as approved by the
technical board[0].
[0]: https://lists.ubuntu.com/archives/technical-
board/2015-April/002090.html
** Affects: docker.io (Ubuntu)
The rootfs used Vivid and now Wily, but the issue remains with both.
--
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/1452451
Title:
failed to change apparmor profile to
Which distribution is in the rootfs?
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
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/1452451
Title:
failed to change
so 1 of 2 things seems like it must have happend:
a.) 'isblk' is not getting set (which would mean we dont run blockdev and
udevadm settle)
b.) my assumption that changing the partition table on a device, then running
'blockdev --rereadpt' and subsequently 'udevadm settle' would result in the
** Changed in: lxc (Ubuntu)
Status: Incomplete = Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided = Critical
** Changed in: lxc (Ubuntu)
Status: Triaged = New
** Changed in: lxc (Ubuntu)
Importance: Critical = High
--
You received this bug notification because you
This bug was fixed in the package simplestreams - 0.1.0~bzr378-0ubuntu1
---
simplestreams (0.1.0~bzr378-0ubuntu1) wily; urgency=medium
* New upstream snapshot.
- GlanceMirror: identify images as i686 not i386 (LP: #1454775)
- sstream-mirror: debug statement about filtered
Public bug reported:
sudo apt-get install lamp-server^
sudo apt-get autoremove *
then removed folders (php5, mysql, apache)
sudo apt-get install lamp-server^
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.9
ProcVersionSignature: Ubuntu
As per https://bugzilla.gnome.org/show_bug.cgi?id=747718#c13 this is a
samba library bug.
** Package changed: nautilus (Ubuntu) = samba (Ubuntu)
** Changed in: nautilus
Importance: Medium = Undecided
** Changed in: nautilus
Status: Unknown = New
** Changed in: nautilus
Remote watch:
** Changed in: openvswitch (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1336555
Title:
[SRU] ovs-vswitchd crashed with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
This bug was fixed in the package openstack-trove - 2015.1.0-0ubuntu1.2
---
openstack-trove (2015.1.0-0ubuntu1.2) vivid; urgency=medium
* d/p/patch-default-config-file.patch: Fix to ensure that path to
sqlite database is fully specified (LP: #1451134).
-- James Page
This bug was fixed in the package neutron-vpnaas - 1:2015.1.0-0ubuntu1
---
neutron-vpnaas (1:2015.1.0-0ubuntu1) vivid; urgency=medium
* New upstream release for OpenStack kilo. (LP: #1449744)
-- Chuck Short zul...@ubuntu.com Thu, 30 Apr 2015 18:32:31 +0200
--
You received this
This bug was fixed in the package openstack-trove - 2015.1.0-0ubuntu1.2
---
openstack-trove (2015.1.0-0ubuntu1.2) vivid; urgency=medium
* d/p/patch-default-config-file.patch: Fix to ensure that path to
sqlite database is fully specified (LP: #1451134).
-- James Page
This bug was fixed in the package manila - 2015.1.0-0ubuntu1
---
manila (2015.1.0-0ubuntu1) vivid; urgency=medium
* New upstream release for OpenStack kilo. (LP: #1449744)
-- Chuck Short zul...@ubuntu.com Fri, 01 May 2015 08:38:15 +0200
--
You received this bug notification
This bug was fixed in the package designate - 2015.1.0-0ubuntu1.1
---
designate (2015.1.0-0ubuntu1.1) vivid; urgency=medium
* d/p/fix-SO_REUSEPORT-usage.patch: Cherry pick workaround for use of
SO_REUSEPORT socket option with older kernel versions, resolving
FTBFS on distro
Can you re-upload:
The source usbredir - 0.6-2ubuntu2 is already accepted in ubuntu/utopic and you
cannot upload the same version within the same distribution. You have to modify
the source version and re-upload.
So perhaps use 0.6-2ubuntu1.1 ?
** Description changed:
Hello Emilien, or anyone else affected,
Accepted openstack-trove into vivid-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/openstack-
trove/2015.1.0-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello James, or anyone else affected,
Accepted designate into vivid-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/designate/2015.1.0-0ubuntu1.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matt, or anyone else affected,
Accepted libvirt into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.2.12-0ubuntu13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** 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 openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1451134
Title:
Default connection parameters fails when
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1454805
Title:
package libapache2-mod-php5 5.5.9+dfsg-1ubuntu4.9 failed to
install/upgrade:
doh. I hadn't seen that in the publication history.
Pushed 0.6-2ubuntu1.1, thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to usbredir in Ubuntu.
https://bugs.launchpad.net/bugs/1451540
Title:
usbredir fails to build in trusty
Hello gadLinux, or anyone else affected,
Accepted openvswitch into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/openvswitch/2.0.2-0ubuntu0.14.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Mathieu, or anyone else affected,
Accepted libvirt into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.11 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
Please sync mailman 1:2.1.18-2 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: path traversal vulnerability
- debian/patches/CVE-2015-2775.patch: validate list name in
Mailman/Utils.py, add comment
** Tags added: canonical-bootstack
--
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/1356392
Title:
lacks sw raid1 install support
To manage notifications about this bug go to:
** Tags removed: need-duplicate-check
--
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/1454887
Title:
package clamav-milter 0.98.7+dfsg-0ubuntu0.14.04.1 failed to
install/upgrade:
** Changed in: libibverbs (Ubuntu)
Importance: Undecided = High
** Changed in: libibverbs (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libibverbs in Ubuntu.
** Also affects: libibverbs (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libibverbs (Ubuntu Trusty)
Assignee: (unassigned) = Adam Conrad (adconrad)
** Changed in: libibverbs (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: libibverbs (Ubuntu
This happens if the container config doe snot specify mounting /proc,
because there is no (or a wrong) /proc in the container until the
container's init mounts it.
So lxc-attach needs to mount a temporary /proc (after switching
namespaces) for the sake of setting the lsm label.
** Changed in:
Public bug reported:
The system was staying more and more slowly almost stopping
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: clamav-milter 0.98.7+dfsg-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
Uname: Linux 3.13.0-52-generic i686
ApportVersion:
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package libqb - 0.16.0.real-1ubuntu4
---
libqb (0.16.0.real-1ubuntu4) trusty; urgency=medium
[ Billy Olsen ]
* debian/patches/ringbuffer-reclaim-fix.patch: infinite loop when
attempting to reclaim space in the ringbuffer fails. (LP: #1341496)
--
Yup, that's the trouble. Good sleuthing. Knowing that (and, indeed,
`ssh-add -X` reports success regardless of password entered), I can
start a real ssh-agent anywhere I want agent locking instead of gui
integration.
Thanks!
--
You received this bug notification because you are a member of
Uploaded libibverbs/libmlx4 for wily.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libibverbs in Ubuntu.
https://bugs.launchpad.net/bugs/1409904
Title:
Needed patches for InfiniBand Support: Flow Steering and Offload
Support +
Was the package 2.0.10-1ubuntu3 (in vivid and wily) ever tested? It has
an additional upstream patch to fix a potential segv.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
https://bugs.launchpad.net/bugs/1358835
** Description changed:
+ =
+ SRU Justification
+ 1. Impact: VMs fail to launch with TCG (non-kvm-accelerated)
+ 2. Stable fix: cherrypick a patch from upstream.
+ 3. Regression potential: this only slightly relaxes the check for multiple
cpus, and is
** Description changed:
+ ===
+ SRU Justification
+ 1. Impact: crash when removing filterref from a network interface
+ 2. Test case: Create an interface with filterref (see below), then update it
and try to remove it.
+ 3. Regression potential:
** Description changed:
==
SRU Justification:
Note: This fix is not applicable to vivid, because we only support migration
from LTS-LTS, so from 12.04 to 14.04. Therefore a fix is only needed for 14.04
Impact: live migration
I cannot reproduce this.
Would it be possible to coordinate your handing off a broken system to
me? Unfortunately I am out tomorrow and Friday, but perhaps sometime
next week?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/182716
--
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/1426324
Title:
VFS blkid calls need to handle 0 or 2
Public bug reported:
New packages with version 1.0+noroms break dependencies on old packages
from cloud-archive with version 1.5.0+dfsg.
# cat /etc/issue
Ubuntu 12.04.4 LTS \n \l
# apt-get install --upgrade qemu-kvm=1.0+noroms-0ubuntu14.22
qemu-utils=1.0+noroms-0ubuntu14.22
Reading package
@j-rosenboom-j My fix for nova will never be accepted upstream. I
wont speak for the Ubuntu developers but I strongly suspect that they'll
be unwilling to diverge from upstream. Especially as they've already
shown the fix will land in vivid.
--
You received this bug notification because you
I can verify that installing 1.2.12-0ubuntu13 on vivid fixes the issue
for me.
Please forgive my ignorance but can that package be tagged into cloud-
archive once it's officially a vivid update?
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26
--- Comment (attachment only) From thierry.fa...@fr.ibm.com 2014-12-08
16:02 EDT---
** Attachment added: Patch for libnuma.c
https://bugs.launchpad.net/bugs/1358835/+attachment/4397175/+files/linuma_patch.diff
--
You received this bug notification because you are a member of
--- Comment (attachment only) From thierry.fa...@fr.ibm.com 2014-11-19
14:45 EDT---
** Attachment added: libnuma.so.1 sum 55709
https://bugs.launchpad.net/bugs/1358835/+attachment/4397174/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug notification
--- Comment on attachment From thierry.fa...@fr.ibm.com 2014-11-18 15:55
EDT---
Please have a test
** Attachment added: new libnuma.so with fix
https://bugs.launchpad.net/bugs/1358835/+attachment/4397173/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug
** Changed in: simplestreams (Ubuntu)
Status: New = Fix Released
** Changed in: simplestreams (Ubuntu)
Importance: Undecided = Medium
** Also affects: simplestreams (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu Trusty)
Status:
Public bug reported:
Trusty's python-simplestreams uploads i386 images as architecture: i386,
which nova filters out, since it is not 'i686'.
See also
http://bazaar.launchpad.net/~smoser/simplestreams/trunk/revision/366
Can we please get this into trusty-updates?
thanks,
lamont
** Affects:
Change abandoned by Joe Gordon (joe.gord...@gmail.com) on branch: master
Review: https://review.openstack.org/132263
Reason: This review is 4 weeks without comment, and failed Jenkins the last
time it was checked. We are abandoning this for now. Feel free to reactivate
the review by pressing
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26
--- Comment on attachment From thierry.fa...@fr.ibm.com 2014-11-18 15:55
EDT---
Please have a test
** Attachment added: new libnuma.so with fix
https://bugs.launchpad.net/bugs/1358835/+attachment/4396913/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug
--- Comment (attachment only) From thierry.fa...@fr.ibm.com 2014-12-08
16:02 EDT---
** Attachment added: Patch for libnuma.c
https://bugs.launchpad.net/bugs/1358835/+attachment/4396915/+files/linuma_patch.diff
--
You received this bug notification because you are a member of
--- Comment (attachment only) From thierry.fa...@fr.ibm.com 2014-11-19
14:45 EDT---
** Attachment added: libnuma.so.1 sum 55709
https://bugs.launchpad.net/bugs/1358835/+attachment/4396914/+files/libnuma1_2.0.9%7Erc5-1ubuntu2_ppc64el.deb
--
You received this bug notification
Dang, I was afraid you might not be able to reproduce, being a race and
all. I'm not sure it's possible to hand off the system as it's my
primary development machine.
I think I will take a stab in trying to debug this. A quick looks shows
that it is failing in this block in lsm/apparmor.c:
if
This bug was fixed in the package qemu - 2.1+dfsg-4ubuntu6.5
---
qemu (2.1+dfsg-4ubuntu6.5) utopic-proposed; urgency=medium
* debian/control-in: enable numa on architectures where numa is built
(LP: #1417937)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 17 Feb 2015 14:13:00
** Also affects: libvirt (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: libvirt (Ubuntu)
Importance: Undecided =
possible / likely explanation is that there is no guarantee that blockdev will
exit after kernel has put events into the udev queue.
so udevadm could have run and found an empty queue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
So, if I remove the lxc-wait out of the start/wait/attach sequence, then
I always get the failure. This really points to a race where RUNNING is
being reported before it is really fully started.
It looks like the RUNNING state is set in start.c, so perhaps it is
being set a bit too early where
You have been subscribed to a public bug:
When attempting to mount a Ubuntu samba share via Nautilus, it notes:
Unable to access location
Failed to mount Windows share: Invalid argument
However, mounting via smbclient works fine. Hence, this would be an
issue with Nautilus/backend.
ProblemType:
Public bug reported:
I have executed github openflow 1.3 scripts with Openvswitch and got the
below error as openvswitch not accepting the message (OFPBRC_EPERM)
==
FAIL: bsn_gentable.SetBucketsSizeError
75 matches
Mail list logo
