I can confirm that `sed -i "s|-Lsd|-LS6d|" /etc/default/snmpd` fixes the
problem for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1246347
Title:
Lots of "error on
Public bug reported:
The only thing that seems to fail is the start:
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.conf in
/var/backups/slapd-2.4.31-1+nmu2ubuntu8.1... done.
* Starting OpenLDAP slapd
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1496713
Title:
package slapd 2.4.31-1+nmu2ubuntu8.2 failed to install/upgrade:
subprocess
** Changed in: cloud-archive
Status: New => Triaged
** Changed in: python-heatclient (Ubuntu)
Status: New => Triaged
** Changed in: python-heatclient (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-archive
Importance: Undecided => Medium
** Also affects:
Related to bug #1267564 (duplicate)
Proposed solution as found on
http://triple-networks.com/2014/07/20/etckeeper-git-issue-on-trusty/
To prevent this, make sure “/etc/hosts” contains a FQDN for the current
hostname of your machine.
[...]
127.0.1.1 ursula.example.com ursula
--
You received
** Also affects: python-ceilometerclient (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-ceilometerclient (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: python-ceilometerclient (Ubuntu Vivid)
Importance: Undecided
Status: New
**
Actually this does exist in 0.15.0 as well; but you only hit this
problem if the image-list call gets paginated due to a large number of
images.
I think it was fixed in https://github.com/openstack/python-
glanceclient/commit/f98ab688eff8fff4bdb5f650da3516715d62f232 (included
in 0.17.0) when the
As there was no response in 6 months, marking Fix Released on the
assumption this is no longer a problem
** Changed in: cloud-archive
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
Marking task Trusty as invalid, since haproxy 1.4 uses --pidfile and is
unaffected.
Marking task Wily as fix released as the --pid option is available in
Wily so haproxy 1.5 is unaffected
** Also affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
** Also affects: haproxy
Salut Louis,
Thanks for taking care of this bug. Have I understood correctly that the
haproxy package in trusty-backports is already updated? Or do I have to
wait until the package is released to all mirrors?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Patch for the fix to the backport package
** Patch added: "lp1494141_fix_stop_failure.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1494141/+attachment/4466700/+files/lp1494141_fix_stop_failure.debdiff
--
You received this bug notification because you are a member of
Bonjour Claudio,
No, I have just submitted the fix for inclusion in the backported
package. Once the backport team has taken care of it, it will be
indicated as such in the bug.
Kind regards,
..Louis
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
I see this already got promoted - thankyou doko.
** Changed in: python-castellan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-castellan in Ubuntu.
Already promoted - thanks doko.
** Changed in: python-magnumclient (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-magnumclient in Ubuntu.
https://bugs.launchpad.net/bugs/1496791
Thank you Mathieu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1469143
Title:
kpartx -d fails with image paths longer than 63 characters
To manage notifications about
Public bug reported:
[Availability]
Universe
[Rationale]
New dependency for glance
[Security]
No security history
[Quality assurance]
Package builds ok, unit tests executed
[Dependencies]
All in main
[Standards compliance]
OK
[Maintenance]
ubuntu-server/ubuntu-openstack
** Affects:
Most recent upload has upstream submitted fixes for python >= 3.4.
** Changed in: python-magnumclient (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-magnumclient in Ubuntu.
This bug was fixed in the package iscsitarget - 1.4.20.3+svn502-2ubuntu2
---
iscsitarget (1.4.20.3+svn502-2ubuntu2) wily; urgency=low
* Fix the compat-3.13.patch to not touch the top-level makefile. Will
allow to backport this version into older (kernel 3.13 and older)
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-15.05:
Raise MIR for python-openstackclient: DONE
Work items for ubuntu-15.06:
Liberty B1 update: DONE
Icehouse stable update: DONE
Transition oslo packages back to oslo.XXX naming: DONE
Convergence of
Public bug reported:
[Availability]
Universe
[Rationale]
New dependency for heat
[Security]
No security history
[Quality assurance]
Package builds ok, unit tests executed
[Dependencies]
All in main
[Standards compliance]
OK
[Maintenance]
ubuntu-server/ubuntu-openstack
** Affects:
Fixing py3 test failures.
** Changed in: python-magnumclient (Ubuntu)
Importance: Undecided => High
** Changed in: python-magnumclient (Ubuntu)
Milestone: None => ubuntu-15.09
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This bug was fixed in the package iscsitarget - 1.4.20.3+svn502-2ubuntu2
---
iscsitarget (1.4.20.3+svn502-2ubuntu2) wily; urgency=low
* Fix the compat-3.13.patch to not touch the top-level makefile. Will
allow to backport this version into older (kernel 3.13 and older)
Yes. I was running Vagrant and I had to increase the memory to 1024MB of
the VM. Increasing the memory worked for me.
Thanks a lot. Hope this helps someone.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
** Changed in: corosync (Ubuntu Trusty)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
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/1434684
Title:
Pacemaker is not
Hello,
Well, elbandi have found the answer to your question : pacemaker now
needs to be started as a separate service. To quote the document :
"Pacemaker used to obtain membership and quorum from a custom Corosync plugin.
This plugin also had the capability to start Pacemaker automatically when
Deployed Trusty Icehouse with this nova version, ran the test described
above and lgtm +1.
** 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 nova in Ubuntu.
** Package changed: haproxy (Ubuntu) => trusty-backports
--
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/1494141
Title:
HAProxy 1.5 init script does not terminate processes
To manage
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu, since you appear to have extensively deleted MySQL configuration
files and so it cannot be expected to work.
You can find pointers to get help for this sort of problem here:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
> When attempting to rebuild the php5 package with --enable-maintainer-
zts --with-tsrm-pthreads enabled...
Sorry, if you want to modify Ubuntu by rebuilding after changing build-
time configuration, then you're
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete. I've
tested slapd from trusty-updates and it does appear to install
Bug catchup - Marking fix released as all cloud-archive pockets are up-
to-date with libvirt and qemu fixes.
** Changed in: cloud-archive
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
** Changed in: horizon (Ubuntu)
Status: Confirmed => Triaged
** Changed in: horizon (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-archive
Status: New => Triaged
** Changed in: cloud-archive
Importance: Undecided => Low
--
You received this bug notification
This is fixed in 1.21-1 in Debian. Ubuntu will get it when we autosync
next cycle.
** Summary changed:
- package nagios3-cgi 3.2.3-1ubuntu1.2 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
+ mini-httpd breaks nagios by diverting to an
Thanks Artur!
** Changed in: exim4 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/1485369
Title:
Merge exim4 4.86-2 (main) from
** Branch linked: lp:ubuntu/wily-proposed/exim4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/1485369
Title:
Merge exim4 4.86-2 (main) from Debian unstable (main)
To manage
Louis,
I can't sponsor your debdiff into backports, but be careful of ordering
issues in your patch. clean() should be defined before the trap is set,
and tmp should be defined before any point that clean() could be called.
In general you should quote "$tmp" as well in case it ends up with
spaces
This bug was fixed in the package lightdm - 1.16.2-0ubuntu1
---
lightdm (1.16.2-0ubuntu1) wily; urgency=medium
* New upstream release:
- Fix compile failing without libinput
-- Robert Ancell Wed, 16 Sep 2015
14:20:11 -0400
** Changed in:
Micah, got the bug number ? Maybe we should make this one a duplicate
then ?
..Louis
--
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/1494141
Title:
HAProxy 1.5 init script does not
debdiff includes an updated apparmor profile for libvirt-qemu for
libraries provided by qemu-block-extra
** Patch added: "libvirt_qemu_block_extra_apparmor_update.debdiff"
** Patch removed: "lp1494141_fix_stop_failure.debdiff"
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+attachment/4466700/+files/lp1494141_fix_stop_failure.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
Thanks for reporting this bug.
Why do you feel this is a bug in lxc? Did you run the sample
program inside a container? Since apparmor profiles cannot be nested
and containers by default run confined, you would indeed not be able
to switch profiles inside a container.
Please show us precisely
** Changed in: landscape/release-29
Status: New => In Progress
** Changed in: landscape/release-29
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: landscape
Status: New => In Progress
** Changed in: landscape
Assignee: (unassigned) => Andreas
There's another haproxy backport request that should fix this (from
utopic version). It was missing the testing of one of the reverse
dependencies.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Hi Robie,
Thanks for your reply. I did see the messages about configuration files
but can honestly say, 'it wasn't me guv'. I didn't actually know that
mySQL had been installed until I got the update error about
inconsistencies in the package. I agree though that on the surface this
looks
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1488815
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
Public bug reported:
With the latest Ubuntu 15.04 Vivid( Kernel 3.19), I tried to ran the
sample program for aa_change_profile from the man page. Whenever I tried
to execute the program, it says No such file or directory. I ran strace
for this program, whenever aa_change_profile is called, looks
** 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 qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1488815
Title:
Kernel traces with skb_warn_bad_offload
I've tested[1] the proposed package and it passes[2] the testcase in
the SRU justification.
1. uvt-simplestreams-libvirt sync release=trusty arch=amd64
uvt-kvm create --cpu 2--disk 10 t1 release=trusty arch=amd64
uvt-kvm wait --insecure t1
uvt-kvm ssh --insecure t1
# inside
This bug was fixed in the package maas - 1.8.2+bzr4041-0ubuntu1
---
maas (1.8.2+bzr4041-0ubuntu1) wily; urgency=medium
* New upstream bugfix release, 1.8.2 bzr 4041:
- Regenerate the connection URL on websocket client reconnect, to fix
CSRF after upgrade to 1.8.1. (LP:
** Attachment removed: "debdiff to fix libecap dependency and
logical-not-parentheses warning"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+attachment/4465698/+files/squid3_3.3.8-1ubuntu16-FTBFS.debdiff
** Description changed:
- Note: currently squid3 fails due to
Please note that squid will still FTBFS due to LP: #1496223 even after
applying this patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1496924
Title:
squid3 FTBFS due to bad
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1496924
Title:
squid3 FTBFS due to bad libecap3 dependency and logical-not-
parentheses warning
To manage notifications about this
** Patch added: "squid3_3.3.8-1ubuntu16.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+attachment/4466957/+files/squid3_3.3.8-1ubuntu16.debdiff
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Currently squid3 FTBFS due to:
1. libecap3-dev dependency, should be libecap2-dev [1]
2. error due to a "logical-not-parentheses" warning
= Build error #1
checking for EXT_LIBECAP... no
configure: error: Package requirements (libecap >= 0.2.0 libecap < 0.3) were
not
I think the two bugs are only related. In #1267564 every change with apt,
synaptic or update-manager leads to an error, as username and email are not
set. As changing packages require root privilege the username and email have to
be configured for the root login.
When this is done altering
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.
Public bug reported:
Ricardo was trying to tie reporting into maas and found
that it is posting things like:
timestamp=1442509672.620882=SUCCESS=cloudinit=running+modules+for+final_type=finish=modules-final
rather than posting json data representing that same stuff, as curtin is doing.
Need to
Hello Axel, or anyone else affected,
Accepted iscsitarget into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/iscsitarget/1.4.20.3+svn499-0ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Stefan, or anyone else affected,
Accepted iscsitarget into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/iscsitarget/1.4.20.3+svn499-0ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1496223
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
** Also affects: cloud-init
Importance: Undecided
Status: New
--
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/1496960
Title:
webhook reporter posts url encoded data not
** Branch linked: lp:cloud-init
--
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/1496960
Title:
webhook reporter posts url encoded data not json data
To manage notifications
Simon, you may want to add a few ethernet interfaces and static routes.
I was able to reproduce it with ~6 network interface.
--
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/1481388
This bug was fixed in the package cloud-init - 0.7.7~bzr1146-0ubuntu1
---
cloud-init (0.7.7~bzr1146-0ubuntu1) wily; urgency=medium
* New upstream snapshot.
* make the webhook reporter post json data rather than
urlencoded data (LP: #1496960)
-- Scott Moser
Err, I meant I couldn't reproduce the issue with and without the patch.
--
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/1481388
Title:
NTP : Use-after-free in routing socket code after
I tried to reproduce the problem by lowering {r,w}mem_max on Precise and
Trusty's *unpatched* version to no avail. On the up side, I couldn't
find any regression with the update version.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** 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 squid3 in Ubuntu.
Hi Vincent, I've submitted an upload for -proposed along with another
fix. Once the fix lands in -proposed, can you please complete the
verification steps?
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status:
Eric, I don't know if that's a good test case but on my patched Trusty
box:
root@xeon:~# uname -a
Linux xeon 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
root@xeon:~# sysctl net.core.wmem_max=4650
net.core.wmem_max = 4700
root@xeon:~#
I've just uploaded a fix that means the package now builds in a clean
environment.
--
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/1487010
Title:
please upload new package to
Yes, sure, I'll do it.
--
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/1382481
Title:
[SRU] Support for CloudStack's basic networking in Precise
To manage notifications about
Public bug reported:
i dont know whappend
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: dlm 4.0.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6
Uname: Linux 3.19.0-29-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
Date: Thu Sep 17
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dlm in Ubuntu.
https://bugs.launchpad.net/bugs/1497064
Title:
package dlm 4.0.1-0ubuntu2 failed to install/upgrade: subprocess
installed
In a meeting with Mellanox in Israel I was told that libibverbs and
libmlx4 have been verified and proved to work. Changing this to
verification done. Thank you.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member
** Changed in: samba (Ubuntu)
Status: New => Confirmed
** Changed in: logrotate (Ubuntu)
Importance: Undecided => Medium
** Changed in: samba (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
And another one fixed to avoid stripping the syso (which stops it
working!)
--
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/1487010
Title:
please upload new package to reenable go's
Rmoved from wily.
** Changed in: juju (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1426549
Title:
drop pyjuju from vivid and newer
To
Public bug reported:
juju 1.18.1 is in trusty-release
Juju 1.22.6 is in trusty-updates
Juju 1.22.1 is in vivid-release, meaning upgrades from updated trusty to vivid
fail
Juju 1.22.6 is in wily
As a result of these version numbers, a fully-updated trusty system
should fail to upgrade to vivid
juju 0.7 is still available in wily. Is it too late to remove it?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1426549
Title:
drop pyjuju from vivid and newer
To manage
This doesn't need apport-collect, this is a bug in the header files
which is straightforward to reproduce.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a
Uploading this seems blocked by bug 1496223, so let's keep this in the
queue for now.
** Changed in: squid3 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
Can you please clarify the status here for sponsoring?
qemu_system_common_depend_on_qemu_block_extra.debdiff seems a bit harsh
-- the whole point of splitting out a separate binary is that you
*don't* have to have it installed all the time, no? So maybe a
Recommends: or Suggests:? But AFAIUI this
I uploaded the trusty patch to the SRU review queue. Thank you!
** Changed in: apache2 (Ubuntu Trusty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
So this is fixed in wily which has 2.4.12.
** Changed in: apache2 (Ubuntu)
Status: Triaged => Fix Released
** Also affects: apache2 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This was already uploaded without closing this bug:
https://launchpad.net/ubuntu/+source/golang/2:1.5.1-0ubuntu1
** Changed in: golang (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang
86 matches
Mail list logo