Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Fwiw, I agree with enikanorov's assessment. It looks like the first
value (tenant_id) is mistakenly a python dict instead of the expected
simple string.
Having stared at the relevant piece of havana-eol code
(neutron.db.metering.metering_db.MeteringDbMixin.create_metering_label())
and traced the
This also appears for me in Ubuntu 12.04 LTS, with cloud-init
0.6.3-0ubuntu1.15.
Rebooting in recovery mode, I was able to install the python-serial
package, and the error message went away once I rebooted.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
The samba DHCP enter hook needs to be fixed too, so adding a task.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu)
Importance: Undecided = Medium
** Changed in: samba (Ubuntu)
Status: New = In Progress
** Changed in: samba
Public bug reported:
It seems a fairly recent update to LXC has caused this. This is a
privileged container. I will attach debug output when trying to start
the container.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.0~rc4-0ubuntu1
ProcVersionSignature: Ubuntu
This is the debug output when starting the container.
** Attachment added: debug.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1417909/+attachment/4311947/+files/debug.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Tags removed: need-duplicate-check
--
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/1417890
Title:
package lxc 1.0.7-0ubuntu0.1 failed to install/upgrade: subprocess
installed
Public bug reported:
Took a very long time to come of lxc instalation which I tried to do via
'apt-get install lxc'. Finally it failed.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.7-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: open-vm-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
This is the generated LXC config file.
** Attachment added: config
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1417909/+attachment/4311948/+files/config
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Ill prep an SRU and a debdiff for this fix, if only because one of my
servers is impacted.
** Changed in: php5 (Ubuntu Trusty)
Status: Triaged = In Progress
** Changed in: php5 (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: php5 (Ubuntu Trusty)
Assignee: (unassigned)
Blueprint changed by Liam Young:
Work items changed:
Work items for ubuntu-15.01:
+ Try Mojo for Openstack bundle and HA testing: DONE
+ Write Mojo spec and helpers for Openstack Deploys: DONE
+ Add Mojo support into OSCI: DONE
+ Add support for Ceph Rados gw HA: DONE
+ Add unicast support to
** Description changed:
+ === Begin SRU Information ===
+ [Impact]
+ CloudStack provides an EC2-style metadata server which cloud-init consumes.
Unfortunately, the CloudStack metadata server does not exactly match the
behaviour of the EC2 metadata server. When an instance using cloud-init is
** Description changed:
+ [Impact]
+
+ * After the switch to Upstart in Saucy, php5-fpm log rotation began to
+ break. It was reported that individuals were getting weekly cron
+ warning emails during logrotation.
+
+ [Test Case]
+
+ * This test case happens with automatic rotation of logs,
** Branch linked: lp:~daniel-thewatkins/ubuntu/trusty/cloud-
init/lp1356855
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1356855
Title:
Cloud-init 0.7.5 Failed to get
Debdiff for Trusty (based off of comment #5 from Ondrej)
Test build uploaded to https://launchpad.net/~teward/+archive/ubuntu
/sru-builds/+packages
** Patch added: Trusty Debdiff for this issue
Public bug reported:
Release: any
Version: 1.2.8
Expected: Assigning host device to pcie-root like this:
domain type='kvm'
...
os
type arch='x86_64' machine='pc-q35-2.0'hvm/type
/os
...
controller type='pci' index='0' model='pcie-root'/
controller type='pci' index='1'
** Changed in: nut (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1405822
Title:
Default ups.conf should have maxretry setting above examples
*** This bug is a duplicate of bug 1416854 ***
https://bugs.launchpad.net/bugs/1416854
** This bug has been marked a duplicate of bug 1416854
Fail to install rabbitmq-server
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thanks. Assuming the patch is correct this looks good, but needs to be
done in Vivid first, and the SRU paperwork done for SRUs to Trusty and
Utopic. See https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for
the steps needed.
A couple of potential minor improvements:
Try to say _why_ in the
*** This bug is a duplicate of bug 1214379 ***
https://bugs.launchpad.net/bugs/1214379
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 #1214379, so is being marked as such.
We're not on a bridged network (nor are there VMs) so we may be seeing a
different bug, or perhaps both situations trigger the same symptom. I'll
try playing with the timeout.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Looked good, uploaded to vivid with a couple of minor changelog changes.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1405822
Title:
Default ups.conf should have maxretry
In addition, Debian has had an RFS open on php5 for two years now:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664595.
JFTR the team is quite healthy now, but I keep the bug open since we are
always keen on having more people on board.
--
You received this bug notification because you
** Bug watch added: Debian Bug tracker #776947
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776947
** Also affects: nut (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776947
Importance: Unknown
Status: Unknown
** Changed in: nut (Ubuntu)
Status: New =
** Changed in: openvswitch (Ubuntu Utopic)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: openvswitch (Ubuntu Utopic)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in
** Patch added: fix-lp1417775-utopic.debdiff
https://bugs.launchpad.net/debian/+source/openvswitch/+bug/1417775/+attachment/4311660/+files/fix-lp1417775-utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in
James, if you can ACK the patch I can sponsor if necessary.
Thanks,
--
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/1417775
Title:
remove dkms binary package from openvswitch
Could you please try the package in the following PPA, to make sure they
fix the regression without causing any further issues?
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
If it works for you, I will release it as a security regression update.
Thanks!
--
You received
Blueprint changed by Liam Young:
Work items changed:
Work items for ubuntu-15.01:
Try Mojo for Openstack bundle and HA testing: DONE
Write Mojo spec and helpers for Openstack Deploys: DONE
Add Mojo support into OSCI: DONE
Add support for Ceph Rados gw HA: DONE
Add unicast support to
Hello Luis, or anyone else affected,
Accepted open-vm-tools into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/open-vm-
tools/2011.12.20-562307-0ubuntu1.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
You have been subscribed to a public bug by Robie Basak (racb):
The freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubuntu 14.04 LTS (Trusty Tahr)
has a bug in the logrotate script (/etc/logrotate.d/freeradius):
The command /etc/init.d/freeradius reload is used for reloading
freeradius after its logfile(s)
You have been subscribed to a public bug by Robie Basak (racb):
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -
About Ubuntu
Description:Ubuntu 13.10
Release:13.10
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking
You have been subscribed to a public bug by Robie Basak (racb):
-- Problem Description --
irqbalance is not working properly in Ubuntu 14.04.1, all the interrupts are
going exclusively to one CPU instead of being spread.
# service irqbalance status
irqbalance start/running, process 832
# cat
** Also affects: python-django (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: python-django (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: python-django (Ubuntu Lucid)
Assignee: (unassigned) = Marc Deslauriers (mdeslaur)
** Changed
Patch to backport the fix into utopic.
** Description changed:
+ [Impact]
+
+ Without this patch containers that don't have a complete apparmor
+ configuration fail to start. Making lxc unusable to run Debian Sid and Jessie
+ (at least).
+
+ This bug is not present in Trusty, which ships 1.0.7
Packages are in the upload queues awaiting the SRU team, unsubscribing
ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/583216
Title:
inet_protocols can't be
Public bug reported:
could this be related to net outage?
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.2
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
This bug was fixed in the package nut - 2.7.1-1ubuntu4
---
nut (2.7.1-1ubuntu4) vivid; urgency=low
* debian/patches/0006-ups-conf-reorder.patch: Move maxretry setting
above Examples section, closer to the outside of a driver definition
comment. (LP: #1405822)
-- Tuomas
I can confirm that resolves the issue in my environment, with no other
issues I've noticed. Thanks for the prompt update!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1417274
the fix necessary seems to be:
$ diff -u templates/icehouse/keystone.conf templates/kilo/keystone.conf
--- templates/icehouse/keystone.conf2015-02-03 15:43:25.987725000 +
+++ templates/kilo/keystone.conf2015-02-03 15:40:46.756974000 +
@@ -42,7 +42,7 @@
[endpoint_filter]
@josep-m-perez
Yes, this is an upstream bug. So it affects anyone using the right filesystem
and CONFIGs. Once we fix this upstream, then it will be submitted as a stable
kernel update and make its way into all stable kernels as applicable.
--
You received this bug notification because you are
I installed a newer version of pxelinux to see if that is the culprit.
It doesn't work, but /some/ traffic between the nodes now happens when
transferring the kernel:
11:54:03.181388 IP 10.0.0.12.49164 10.0.0.1.tftp: 77 RRQ
ubuntu/amd64/generic/trusty/release/boot-kernel octet tsize 0 blksize
** Description changed:
[Impact]
Users of non-extent ext4 filesystems (ext4 ^extents, or ext3 w/
CONFIG_EXT4_USE_FOR_EXT23=y) can encounter data corruption when using fallocate
with FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE flags. This seems to be a
regression in ext4_ind_remove_space
Static ARP did not help.
Setting the MTU to 1200 caused pxelinux.0 to fail transferring with
similar, but different behaviour:
12:12:50.699971 IP 10.0.0.12.2071 10.0.0.1.tftp: 32 RRQ pxelinux.0 octet
blksize 1456
12:12:50.773393 IP 10.0.0.1.59263 10.0.0.12.2071: UDP, length 15
Oh, I'm mistaken -- it's exactly the same as before. I hadn't noticed
that the machine had replied once before going offline.
Gavin looked up the ARP issue and it turns out that pxelinux doesn't
respond to ARP when in the keyboard read loop and when in the tftp
send/recv loop, so that's why
Mine is related to bug 1385817
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1241298
Title:
package ntp 1:4.2.6.p5+dfsg-3ubuntu2 failed to install/upgrade:
ErrorMessage: subprocess
Mine is related to bug 1385817
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1414126
Title:
package samba 2:4.1.11+dfsg-1ubuntu2.1 failed to install/upgrade:
subprocess installed
Mine is related to bug 1385817
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1414126
Title:
package samba 2:4.1.11+dfsg-1ubuntu2.1 failed to install/upgrade:
subprocess installed
Mine is related to bug 1385817.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1400669
Title:
package spamassassin 3.4.0-3ubuntu1 failed to install/upgrade:
subprocess
I've verified that the open-vm-tools currently in -updates
(2011.12.20-562307-0ubuntu1) fails to build when installed with the
latest precise kernel (3.2.0-76.111):
Error! Build of vmhgfs.ko failed for: 3.2.0-76-generic (x86_64)
Consult the make.log in the build directory
** Branch linked: lp:~1chb1n/charms/trusty/keystone/kilo-support
** Branch linked: lp:~openstack-charmers/charms/trusty/keystone/next
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
Public bug reported:
I have a old program of mine, that I developed in earlier versions of
Ubuntu against ruby1.8
When I tried to run it today to be reminded of the good old times, it
ruby1.9 crashed in a way not understandable for me.
Does anyone know how to fix this?
Should not at least a
I merged 7.4.1-2ubuntu1 yesterday. Based on Debian's changelog, it looks
like this bug is fixed now in the latest development release. If not,
please reopen.
** Changed in: logwatch (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member
You have been subscribed to a public bug by Robie Basak (racb):
the postinst for apache2 2.4.7-1ubuntu4.1 copies an index.html into
/var/www/html if it cannot find one in */var/www*
I upgraded a server from lucid-precise-trusty today, and the top page was
broken at the end due to this (my site
Thanks. It would perhaps be reasonable to test /var/www/html/index.* as
well, perhaps, and skip the move if any of those exist, presuming that
the user is already using /var/www/html. I can see this might fail if
somebody is using a DocumentRoot of /var/www and simply has an html/
directory being
I wrote:
or 2) a convincing case is made for the relevance of php5-fpm in main.
The number of people marked as affected by bug 1230917 (67) does swing
me a little. I would like to see the fpm bugs cleared up first, though.
--
You received this bug notification because you are a member of
Presumed fixed in Vivid, so marking Fix Released, but from reading the
comments it sounds like this still affects 14.04 so I'll leave a bug
task for Trusty open.
php5-fpm is in universe in Ubuntu, so is community maintained and not
currently looked after by Canonical's server team (see also bug
Okay, we did a lot of debugging and tracing attempting to find the
problem. In the end, it was hardware.
I upgraded manually to a newer version of syslinux and pxelinux which
/did/ appear to be working, albeit VERY slowly. It seems that the 6.x
syslinux network stack is more tolerant of errors,
Public bug reported:
The vivid ppc64el builds are failing. The last success was on
2015-01.20. their first failure was on 2015-01-23.
We suspect that golang-go sets the wrong GOARCH in vivid.
We cannot see the build logs because Lp is a punk. The builds were in the
~juju-package stable and
Public bug reported:
openvswitch doesn't support kernels 3.14.
Utopic contains 3.16.
Let's remove the dkms binary packages as Vivid already has.
** Affects: openvswitch (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: openvswitch (Ubuntu Utopic)
Importance:
** Changed in: openvswitch (Debian)
Status: Unknown = 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/1417775
Title:
remove dkms binary package from
62 matches
Mail list logo
