Now with less libaio-dev in control file for no AIO. Thanks for
catching my mistake
** Patch added: "old_ubuntu-new_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616629/+files/old_ubuntu-new_ubuntu.debdiff
--
You received this bug notification
On Tue, Mar 29, 2016 at 9:05 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> Ryan, for ease of review and sponsorship please provide an incremental
> debdiff against the package that's already in xenial-proposed.
>
I actually did in comment 18, but I didn't know that was sufficient
As far as I can see, the entire versioned code block here is wrong, and
> you should *only* be restarting squid.
>
>
The block (without my addition) is from debian itself. The original block
that's
present in debian:
update-rc.d squid defaults 30 >/dev/null
if test -d /etc/squid3 && dpkg
Hi, are you sure you uploaded the right debdiff? It looks to me like the
one from comment #9 leaves aio enabled...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1555700
Title:
Please
** Changed in: net-snmp (Debian)
Status: Fix Committed => Fix Released
--
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/1245604
Title:
"killall -u snmp" in a pre-install step
if test -d /etc/squid3 && dpkg --compare-versions "$2" lt '3.5'; then
#
# handle the case where we have /etc/squid3 but the init script is
# named squid.
#
service=squid3
if ! test -e /etc/init.d/$service ; then
service=squid
fi
Nevermind, it seems someone already sponsored this upload. So, for
future reference... :)
--
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/1473691
Title:
[FFe] squid: Update to latest
Ryan, for ease of review and sponsorship please provide an incremental
debdiff against the package that's already in xenial-proposed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Branch linked: lp:~lamont/maas/create-maas-proxy.conf-packaging
--
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/1379567
Title:
maas-proxy is an open proxy with no ACLs; it should
I created patched openldap packages for xenial, available on the same
PPA as above. I tested amd64 packages on xenial beta 2.
--
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/1557248
I created a PPA with patched openldap packages for wily and xenial. If
you would like to test them, there is more information in bug 1557248.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
@Martin, these are all fair question and ones I don't have good answers
for currently. After discussions with other members of the Server Team,
we will defer on this merge for now and look to do it in 16.10. Thank
you for your input.
--
You received this bug notification because you are a member
** Changed in: squid3 (Ubuntu)
Importance: Wishlist => Critical
--
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/1473691
Title:
[FFe] squid: Update to latest upstream release (3.5)
Additional build tests available in my Xenial build testing PPA -
https://launchpad.net/~teward/+archive/ubuntu/xenial-
buildtests/+packages - this is to permit armhf, arm64, and ppc64el
builds in addition to i386 and amd64.
If there are no build errors, this PPA will be used for the install
amd64 sbuild logs (plus Lintian checks)
** Attachment added: "amd64 sbuild logs (+ Lintian)"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4616444/+files/nginx_1.9.13-0ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
i386 sbuild logs (plus Lintian checks)
** Attachment added: "i386 sbuild logs (+ Lintian)"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4616443/+files/nginx_1.9.13-0ubuntu1_i386.build
--
You received this bug notification because you are a member of Ubuntu
Server
** Description changed:
+ [SRU Justification]
+ Impact: qemu stops processing traffic
+ Test case: see below (stress test using udp traffic generator)
+ Fix: cherrypick of upstream patch to fix this problem.
+
Description of problem:
- qemu socket becomes full, causing qemu to send
I've attached new debdiff integrating the change to the squid.postinst
fix. We would like to get this build uploaded into proposed (and locked
as the current one is) to continue wider testing of the new squid.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Old Ubuntu to New Ubuntu debdiff
** Patch added: "old-ubuntu-to-new-ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4616441/+files/old-ubuntu-to-new-ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Old Ubuntu to New Debian debdiff
** Patch added: "old-ubuntu-to-new-debian.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4616440/+files/old-ubuntu-to-new-debian.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Actually even porting to trusty is complicated by a set of endianness
patches.
--
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/1556306
Title:
vhost-user: qemu stops processing
Updated the description with the example upgrade testing using the test
packages in the ppa.
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for
** No longer affects: qemu (Ubuntu Vivid)
--
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/1493049
Title:
memory corruption during live-migration in TCG mode
To manage notifications
This is marked as affecting precise, but has anyone reproduced this with
qemu-kvm 1.0+noroms-0ubuntu14.27 ?
The patch is completely inapplicable to that code base, so it would need
to be rewritten from scratch if so.
** Changed in: qemu-kvm (Ubuntu Precise)
Status: New => Invalid
--
(if someone says they have reproduced it on 1.0+noroms-0ubuntu14.27 I'll
unmark it invalid.)
--
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/1556306
Title:
vhost-user: qemu stops
I'm confused- this is marked as affecting qemu-kvm in precise, but the
preceding patch (c6ac36e) which introduced the bug is not there either.
So I'm going to mark this as not affecting precise unless someone speaks
up to say that we in fact need the whole dependent series.
** Changed in:
Hi,
just to be sure, if you run
kvm -vnc :1 -m 1.5G
kvm -vnc :1 -m 1.5G --no-hpet
do those also crash?
Can you please show the contents of
/var/log/libvirt/qemu/u1510-1.log
** Package changed: kvm (Ubuntu) => qemu (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New
Assuming this is running upstart (as it looks like), try adding the
debug and verbose flags as shown in the upstart cookbook?
--
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/1551150
But unfortunately we do not know which patch fixed it, making an SRU
much more problematic. Someone who is able to reproduce the bug would
need to try to either bisect, or make educated guesses and test patch
cherrypicks.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: qemu (Ubuntu Vivid)
Status: In Progress => Won't Fix
--
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/1457639
Title:
qemu-img qcow2 conversion hangs on large core
** Description changed:
- The Juju team is preparing for a 2.0-beta1 release in time for the
- xenial feature freeze date (18-Feb), but not all features required for
- 2.0 will be ready by that date. We believe we will have a complete and
- stable Juju 2.0 by the time of the xenial release, but
** Changed in: tgt (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1555700
Title:
Please merge tgt 1.0.63 from
Public bug reported:
Please sync ethtool 1:4.5-1 (main) from Debian testing (main)
--
http://git.kernel.org/cgit/network/ethtool/ethtool.git/tree/NEWS
Version 4.5 - March 14, 2016
* Tests: Fix missing function declarations when
I'm afraid I've not yet made any headway.
--
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/1536331
Title:
Precise to Trusty live migration failing
To manage notifications about this
Dropped AIO enablement; while the feature was isolated, we've had no
testing on the aio backend; we can always enable it later if we get
enough testing to ensure proper functionality. Therefore dropping the
FFE and just requesting a merge with Debian.
** Changed in: tgt (Ubuntu)
Status:
Old Ubuntu -> New Debian debdiff
** Patch added: "old_ubuntu-new_debian.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616323/+files/old_ubuntu-new_debian.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
@nacc, we are past the cutoff date and there has been no movement on the
Debian side. Nothing on the 2 bugs I reported ([1] and [2]) nor the git
trees of the corresponding packages.
So I think you shouldn't hold the release of your package for that. If
you feel like it, you could include the
Old Ubuntu to New Ubuntu
** Patch added: "old_ubuntu-new_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616324/+files/old_ubuntu-new_ubuntu.debdiff
** Summary changed:
- [FFE] Please merge tgt 1.0.63 from Debian (unstable)
+ Please merge tgt 1.0.63
Hi Robie. Juju2 will *not* support 32 bit archs. As this package is only
used to upgrade to 2.0, it will not be used on armhf and i386 archs.
Per point 2 to in comment 4, Ubuntu accepts FTBFS, where as the Juju team
prefers to be clear about what is not supported:
maybe we want
Architecture:
Public bug reported:
currently cloud-init is removing /etc/network/interfaces.d/eth0.cfg .
This is because cloud-init now has a 'fallback' mode for getting configuration
which should be superior to the statically written one by the image build
process in all cases.
That said, still best to
This bug was fixed in the package ubuntu-core-config - 0.6.39
---
ubuntu-core-config (0.6.39) xenial; urgency=medium
* add /etc/systemd/network to writable paths to allow cloud-init to store
device names (LP: #1562784).
-- Oliver Grawert Tue, 29 Mar 2016
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Public bug reported:
rabbitmq crashes producing this traceback:
Running command: '/usr/sbin/rabbitmq-server'
{error_logger,{{2016,3,29},{16,41,53}},"Too short cookie string",[]}
Public bug reported:
NGINX has recently uploaded 1.9.13. There are included in this upload
multiple bug fixes, but also changes to include support for other
features in the modules.
--
--
The upstream changelog is as follows:
(http://nginx.org/en/CHANGES)
Changes with nginx 1.9.13
Blueprint changed by Thomas Ward:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
I just ran a verification on this package.
root@juju-niedbalski-sec-machine-27:/home/ubuntu# for file in $(strace -e open
-i corosync -v 2>&1 | grep -E '.*shm.*' |grep -Po '".*?"'| sed -e s/\"//g); do
du -sh $file; done
12K /dev/shm/qb-corosync-blackbox-header
8.1M
The verification of the Stable Release Update for walinuxagent 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
This bug was fixed in the package walinuxagent - 2.1.3-0ubuntu4~15.10.0
---
walinuxagent (2.1.3-0ubuntu4~15.10.0) wily; urgency=medium
* No-change backport to wily (LP: #1559307)
-- Robert C Jennings Fri, 18 Mar 2016
15:33:09 -0500
** Changed in:
Blueprint changed by Jon Grimm:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
what a pity we won't have postfix 3.1 in Ubuntu 16.04 LTS ...
--
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/1561975
Title:
default configuration warnings - minor
To manage
How did you install ceph and which version exactly? Running as ceph
should only happen with >= 9.2, which is available on Xenial.
If I install ceph=10.0.3-0ubuntu1 on a new machine, /var/lib/ceph and
/var/run/ceph have ceph:ceph as owner, which looks fine to me. One could
discuss the ownership of
Public bug reported:
When I try to update the system just says that is error with this file
and it is nonspecific. It will not allow for an update to take place.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.12
ProcVersionSignature: Ubuntu
** Tags removed: need-duplicate-check
--
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/1563328
Title:
package python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.12 failed to
install/upgrade:
Public bug reported:
This may be useful for an unexperienced user trying to run ceph on a
small setup, but for an automated deployment of a ceph cluster, it is
pretty annoying that there may be daemons trying to create credentials
that will allow access to the whole cluster if only the new
FYI, following additional regression tests, today we promoted qemu 2.2
+dfsg-5expubuntu9.7~cloud2 from kilo-proposed to kilo-updates in the
Ubuntu Cloud Archive.
** Changed in: cloud-archive/kilo
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
FYI, following additional regression tests, today we promoted neutron
2014.1.5-0ubuntu4~cloud0 from proposed to icehouse-updates in the Ubuntu
Cloud Archive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1563089
Title:
Memory Leak when new cluster
** Summary changed:
- Memory Leak when new configuration is formed.
+ Memory Leak when new cluster configuration is formed.
** Tags added: sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
seeing also bug 1563296, could we perhaps disable that cloud-init tries
to tinker with the network settings at all (snappy simply does all
configuration itself. afaik we only used cloud-init for ssh key
generation and user setup up to now and there are also plans to
drop/disable it by default i
** Also affects: mysql-5.7 (Ubuntu)
Importance: Undecided
Status: New
--
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/1563274
Title:
dbconfig-mysql sets blank port
Yeah, the copying is an ugly hack, but it's already done to some degree,
and has the least risk of breaking anything, I think.
--
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/1528583
Public bug reported:
snappy configures /etc/network/interfaces.d/ by default on first boot
based on snappy config settings of the ubuntu-core snap
with version 0.7.7~bzr1189-0ubuntu1 cloud-init now starts to also
create a file called 50-cloud-init.cfg with differing options to teh
snappy
Another suggestion to solve the header mess is to patch anywhere that
header files are looking for global reference to patch to local
reference "mysql/..."
Not sure if that would cause more harm though.
On Tue, Mar 29, 2016, 03:16 Lars Tangvald
wrote:
> The test
** Also affects: ubuntu-core-config (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-core-config (Ubuntu)
Status: New => Confirmed
** Changed in: ubuntu-core-config (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-core-config (Ubuntu)
Public bug reported:
For non-remote setups, dbconfig will not set a port value, leaving it
blank in generated option files.
MySQL 5.7 will no longer accept a blank port option in the config file
(See https://github.com/mysql/mysql-
server/commit/3d8b4570d1a9d8d03d32e4cd6705b6a2d354e992 for more
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1424900
Title:
Bootstrapping Vivid: ERROR failed to
*** This bug is a duplicate of bug 1468611 ***
https://bugs.launchpad.net/bugs/1468611
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package dpdk - 2.2.0-0ubuntu6
---
dpdk (2.2.0-0ubuntu6) xenial; urgency=medium
* d/dpdk-init fix handling of multiple huge page sizes (LP: #1557532):
- dpdk-init now ensures non-default-hugepage-size mountpoints are
available as well.
-
This bug was fixed in the package dpdk - 2.2.0-0ubuntu6
---
dpdk (2.2.0-0ubuntu6) xenial; urgency=medium
* d/dpdk-init fix handling of multiple huge page sizes (LP: #1557532):
- dpdk-init now ensures non-default-hugepage-size mountpoints are
available as well.
-
This bug was fixed in the package dpdk - 2.2.0-0ubuntu6
---
dpdk (2.2.0-0ubuntu6) xenial; urgency=medium
* d/dpdk-init fix handling of multiple huge page sizes (LP: #1557532):
- dpdk-init now ensures non-default-hugepage-size mountpoints are
available as well.
-
This bug was fixed in the package dpdk - 2.2.0-0ubuntu6
---
dpdk (2.2.0-0ubuntu6) xenial; urgency=medium
* d/dpdk-init fix handling of multiple huge page sizes (LP: #1557532):
- dpdk-init now ensures non-default-hugepage-size mountpoints are
available as well.
-
This bug was fixed in the package dpdk - 2.2.0-0ubuntu6
---
dpdk (2.2.0-0ubuntu6) xenial; urgency=medium
* d/dpdk-init fix handling of multiple huge page sizes (LP: #1557532):
- dpdk-init now ensures non-default-hugepage-size mountpoints are
available as well.
-
Seems Ryan is still investigating whether or not to enable AIO in the
first place. If you decide to disable it, then there's no FFE, and if
you want to enable it and can make sure that it does not negatively
affect other modes, then Adam already gave the OK.
** Changed in: tgt (Ubuntu)
about running the OPENVPN via command-line
it is possible to have the option of using a file with the USERNAME & PASSWORD
for the OPENVPN stored in a safe location (if you believe that!)
you can add the following into the config:
auth-user-pass {fullpath to file with USERNAME & PASSWORD}
Really OpenVPN is not a high enough priority for Canonical to have it fixed in
over 2 years ?!
I thought Ubuntu was supposed to be a replacement OS for businesses ...
anyhow, it is possible to run the configurations using the command line.
It is a joke to explain to users of other 'OSes' that
This is conceptually part of Juju 2.0, so the FFE for that should apply
to charm tools too. +1
** Changed in: charm-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to charm-tools in Ubuntu.
120 kB changelog essentially means "many changes". What testing has been
done with the new version? Do any of the reverse dependencies (cluster-
glue, collectd, heartbeat, zabbix, etc.) need updating as well? How were
these tested with the new openipmi?
** Changed in: openipmi (Ubuntu)
The test failures for dbconfig-common and redmine are due to a) The
tests setting empty port options in config files and b) MySQL 5.7 no
longer allowing empty options in config file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the
Some of the headers that are in include/mysql/mysql are also copied (not
moved) to include/mysql, probably to patch this sort of problem. With
the way the headers are structured right now I don't really see a very
nice way to solve this, so one suggestion is to simply copy everything.
--
You
Not sure how the process here works, is this enough or do i need to
change some status somewhere?
--
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
80 matches
Mail list logo