date:20160114

Public bug reported:

Please merge nginx 1.9.9-1 from Debian into Ubuntu.  There are multiple
packaging changes, which fix bugs or update third-party plugins which
need updated.

--

NGINX 1.9.9-0ubuntu1 was uploaded directly to Ubuntu due to Debian
dragging their heels with updating the package in Debian.  When it
became fairly clear that Debian was extremely slow to update, and was
almost three months behind Nginx upstream, 1.9.9-0ubuntu1 was uploaded
directly to the repositories.

The Debian changelog will be included after the Debian tracker updates -
1.9.9-1 was uploaded to Debian only today.

--

Build tests will be underway in
https://launchpad.net/~teward/+archive/ubuntu/xenial-buildtests
eventually, but build tests outside of my sbuild are still useful.
Build tests won't go here until i've made sure it doesn't die in my
pristine sbuild chroots.

** Affects: nginx (Ubuntu)
 Importance: Wishlist
 Assignee: Thomas Ward (teward)
 Status: In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1534208

Title:
  Please merge 1.9.9-1 (main) from Debian Unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534208/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1484696] Re: Unable to connect to: ws://:/MAAS/ws

2016-01-14 Thread Brian Murray

Hello Larry, or anyone else affected,

Accepted apache2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apache2/2.4.7-1ubuntu4.9 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apache2 (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696

Title:
  Unable to connect to: ws://:/MAAS/ws

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1484696/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1484268] Re: MAAS not auto-detecting/auto-entering credentials for HP Proliant ML310E G8 V2 server

2016-01-14 Thread Jeff Lane

Removing the blocker tag since this is no longer reproducible.

** Tags removed: blocks-hwcert-server

-- 
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/1484268

Title:
  MAAS not auto-detecting/auto-entering credentials for HP Proliant
  ML310E G8 V2 server

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1484268/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1516989] Re: juju status broken

2016-01-14 Thread Curtis Hovey

** Changed in: juju-core/1.25
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1516989

Title:
  juju status  broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1508565] Re: maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM power

2016-01-14 Thread Jeff Lane

Will this be fixed in the 1.9 release?

-- 
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/1508565

Title:
  maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM
  power

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1508565/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533992] Re: package libnss3 2:3.19.2.1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libnss3.so' to '/usr/lib/x86_64-linux-gnu/libnss3.so

2016-01-14 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: nss (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1533992

Title:
  package libnss3 2:3.19.2.1-0ubuntu0.14.04.1 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libnss3.so'
  to '/usr/lib/x86_64-linux-gnu/libnss3.so.dpkg-new': unexpected end of
  file or stream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1533992/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533833] Re: unprivileged lxc containers won't start

2016-01-14 Thread Bas Zoetekouw

Ah, right, that explains things: I'm running a xenial kernel, I think.

For completeness sake, these are the versions:

[bas@miranda]~> uname -a
Linux miranda 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
[bas@miranda]~> dpkg -l linux-image-\* systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
un  linux-image-3.   (no description available)
ii  linux-image-4. 4.2.0-23.28  amd64Linux kernel image for version 4.
ii  linux-image-4. 4.3.0-5.16   amd64Linux kernel image for version 4.
ii  linux-image-ex 4.2.0-23.28  amd64Linux kernel extra modules for ve
ii  linux-image-ex 4.3.0-5.16   amd64Linux kernel extra modules for ve
ii  linux-image-ge 4.2.0.23.25  amd64Generic Linux kernel image
ii  systemd225-1ubuntu9 amd64system and service manager

-- 
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/1533833

Title:
  unprivileged lxc containers won't start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533833/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1357424] Re: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)

2016-01-14 Thread Kick In

Hi,

Yes the work is being done currently. It is awaiting review.

Thanks!

2016-01-14 0:17 GMT+01:00 Artur Rona :

> Any news on that one?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1357424
>
> Title:
>   Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
>
> Status in amavisd-new package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+subscriptions
>


** Changed in: amavisd-new (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1357424

Title:
  Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533639] Re: [ubuntu-cpc] please make /tmp a tmpfs in RAM

** Description changed:

  In Ubuntu, we clear /tmp on every boot.
  
  As such, on servers, by default /tmp should actually be a tmpfs entirely
- in RAM.
+ in RAM, when there is enough memory in the system.  This threshold
+ should be configurable by the end user (in cloud-init?), and default
+ threshold of ~2GB.
  
  This has several advantages, mainly:
   * Performance - much faster read/write access to data in /tmp
   * Security - sensitive data would be cleared from memory on boot, rather 
than written (leaked) to disk -- important for encryption scenarios
   * Power consumption - storing information in memory is more energy efficient 
than reading and writing to disk
  
  In scenarios where more space in /tmp is needed than available, one can
  compliment that tmpfs with 'sudo apt-get install swapspace' which will
  dynamically create/delete swapfile as necessary.

-- 
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/1533639

Title:
  [ubuntu-cpc] please make /tmp a tmpfs in RAM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1533639/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533639] Re: [ubuntu-cpc] please make /tmp a tmpfs in RAM

** Description changed:

  In Ubuntu, we clear /tmp on every boot.
  
  As such, on servers, by default /tmp should actually be a tmpfs entirely
  in RAM.
  
  This has several advantages, mainly:
-  * Performance - much faster read/write access to data in /tmp
-  * Security - sensitive data would be cleared from memory on boot, rather 
than written (leaked) to disk -- important for encryption scenarios
+  * Performance - much faster read/write access to data in /tmp
+  * Security - sensitive data would be cleared from memory on boot, rather 
than written (leaked) to disk -- important for encryption scenarios
+  * Power consumption - storing information in memory is more energy efficient 
than reading and writing to disk

** Description changed:

  In Ubuntu, we clear /tmp on every boot.
  
  As such, on servers, by default /tmp should actually be a tmpfs entirely
  in RAM.
  
  This has several advantages, mainly:
   * Performance - much faster read/write access to data in /tmp
   * Security - sensitive data would be cleared from memory on boot, rather 
than written (leaked) to disk -- important for encryption scenarios
-  * Power consumption - storing information in memory is more energy efficient 
than reading and writing to disk
+  * Power consumption - storing information in memory is more energy efficient 
than reading and writing to disk
+ 
+ In scenarios where more space in /tmp is needed than available, one can
+ compliment that tmpfs with 'sudo apt-get install swapspace' which will
+ dynamically create/delete swapfile as necessary.

-- 
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/1533639

Title:
  [ubuntu-cpc] please make /tmp a tmpfs in RAM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1533639/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533833] Re: unprivileged lxc containers won't start

2016-01-14 Thread Martin Pitt

** Changed in: systemd (Ubuntu Wily)
   Status: New => Triaged

** Summary changed:

- unprivileged lxc containers won't start
+ unprivileged lxc containers won't start, need to put sessions into "pids"  
cgroup controlelr

** Summary changed:

- unprivileged lxc containers won't start, need to put sessions into "pids"  
cgroup controlelr
+ unprivileged lxc containers won't start, need to put sessions into "pids"  
cgroup controller

-- 
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/1533833

Title:
  unprivileged lxc containers won't start, need to put sessions into
  "pids"  cgroup controller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533833/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1512980] Re: Please enable PPS in the Ubuntu build of ntpd

2016-01-14 Thread Kick In

** Changed in: ntp (Ubuntu)
   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.
https://bugs.launchpad.net/bugs/1512980

Title:
  Please enable PPS in the Ubuntu build of ntpd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533639] Re: [ubuntu-cpc] please make /tmp a tmpfs in RAM

** Description changed:

- In Ubuntu, we clear /tmp on every boot.
+ In Ubuntu, we have always cleared /tmp on every boot.
  
  As such, on servers, by default /tmp should actually be a tmpfs entirely
  in RAM, when there is enough memory in the system.  This threshold
  should be configurable by the end user (in cloud-init?), and default
  threshold of ~2GB.
+ 
+ Read about tmpfs here:
+ https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
  
  This has several advantages, mainly:
   * Performance - much faster read/write access to data in /tmp
   * Security - sensitive data would be cleared from memory on boot, rather 
than written (leaked) to disk -- important for encryption scenarios
   * Power consumption - storing information in memory is more energy efficient 
than reading and writing to disk
  
  In scenarios where more space in /tmp is needed than available, one can
  compliment that tmpfs with 'sudo apt-get install swapspace' which will
  dynamically create/delete swapfile as necessary.

-- 
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/1533639

Title:
  [ubuntu-cpc] please make /tmp a tmpfs in RAM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1533639/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534106] Re: rsyslogd crashed with SIGSEGV with juju-local configuration

2016-01-14 Thread Martin Pitt

Really shabby workaround for xenial: Change
/lib/systemd/system/rsyslog.service like this:


[Service]
Type=oneshot
ExecStart=/bin/true
RemainAfterExit=yes

On that note, it would really be nice if juju-local would not require
rsyslog. We have the systemd journal, so having rsyslog installed is
just redundant (I normally don't have it).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

Blueprint changed by Robie Basak:

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
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [raharper] strongswan merge and cleanup (=4days): INPROGRESS
  [nacc] logwatch merge and cleanup: INPROGRESS
  [smoser] openiscsi merge: TODO
  [kick-d] amavisd-new merge: INPROGRESS
  [kick-d] freeipmi merge and cleanup (=3days): INPROGRESS
- [kick-d] freeipmi12 to 16 transition: INPROGRESS
+ [vorlon] freeipmi12 to 16 transition: DONE
  [wesley-wiedenmeier] dovecot merge (doko: done in wily, update to 2.2.2x 
would be good): TODO
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  puppet merge and cleanup: TODO
  [paelzer] DPDK MIR: INPROGRESS
  [paelzer] DPDK upstream work: TODO
  [racb] MySQL cleanup and move to 5.7 (=14days): TODO
  NTP merge, cleanup and PPS support: TODO
  Tomcat updates and cleanup (=14days): TODO
  Java-related work (=10days): TODO
  mail-stack-delivery deprecation plan: TODO
  [tdaitx] squid3 merge (=4days): INPROGRESS
  [louis-bouchard] nut merge: INPROGRESS
  [arges] libvirt merge (bug 1519433) : INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

Blueprint changed by Robie Basak:

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
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [raharper] strongswan merge and cleanup (=4days): INPROGRESS
  [nacc] logwatch merge and cleanup: INPROGRESS
  [smoser] openiscsi merge: TODO
  [kick-d] amavisd-new merge: INPROGRESS
- [kick-d] freeipmi merge and cleanup (=3days): INPROGRESS
+ [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [wesley-wiedenmeier] dovecot merge (doko: done in wily, update to 2.2.2x 
would be good): TODO
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  puppet merge and cleanup: TODO
  [paelzer] DPDK MIR: INPROGRESS
  [paelzer] DPDK upstream work: TODO
  [racb] MySQL cleanup and move to 5.7 (=14days): TODO
  NTP merge, cleanup and PPS support: TODO
  Tomcat updates and cleanup (=14days): TODO
  Java-related work (=10days): TODO
  mail-stack-delivery deprecation plan: TODO
  [tdaitx] squid3 merge (=4days): INPROGRESS
  [louis-bouchard] nut merge: INPROGRESS
  [arges] libvirt merge (bug 1519433) : INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

2016-01-14 Thread Kick In

Blueprint changed by Kick In:

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
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [raharper] strongswan merge and cleanup (=4days): INPROGRESS
  [nacc] logwatch merge and cleanup: INPROGRESS
  [smoser] openiscsi merge: TODO
  [kick-d] amavisd-new merge: INPROGRESS
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [wesley-wiedenmeier] dovecot merge (doko: done in wily, update to 2.2.2x 
would be good): TODO
  [nacc] Consider php7.0 for Xenial: INPROGRESS
+ [kick-d] NTP merge, cleanup and PPS support: TODO
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  puppet merge and cleanup: TODO
  [paelzer] DPDK MIR: INPROGRESS
  [paelzer] DPDK upstream work: TODO
  [racb] MySQL cleanup and move to 5.7 (=14days): TODO
- NTP merge, cleanup and PPS support: TODO
  Tomcat updates and cleanup (=14days): TODO
  Java-related work (=10days): TODO
  mail-stack-delivery deprecation plan: TODO
  [tdaitx] squid3 merge (=4days): INPROGRESS
  [louis-bouchard] nut merge: INPROGRESS
  [arges] libvirt merge (bug 1519433) : INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-01-14 Thread Andrea Lazzarotto (Lazza)

Tristan, how is that a leak? Connections to 8.8.8.8 will go through the
VPN, not outside of it. By the way, the problem remaining is that
sometimes NM seems to still use the DNS of the router as well. It's as
if without VPN you have say 192.168.0.1 as primary DNS, but with VPN you
get these DNS servers:

8.8.8.8
8.8.4.4
192.168.0.1 (for example)

Then sometimes the third DNS receives the query. I will experiment with
setting the static DNS to the Wi-Fi connection as well. Of course it
would be easier if this bug actually gets fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1524590] Re: package libaio1:i386 0.3.110-1 failed to install/upgrade: package libaio1:i386 is already installed and configured

2016-01-14 Thread dino99

*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

** This bug has been marked a duplicate of bug 1407757
   multi-arch packages cannot be installed due to dpkg wrongly detecting them 
as already installed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libaio in Ubuntu.
https://bugs.launchpad.net/bugs/1524590

Title:
  package libaio1:i386 0.3.110-1 failed to install/upgrade: package
  libaio1:i386 is already installed and configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libaio/+bug/1524590/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534106] [NEW] rsyslogd crashed with SIGSEGV with juju-local configuration

2016-01-14 Thread Martin Pitt

Public bug reported:

installing juju-local pulls in rsyslog (at least on current xenial).
When doing

- juju init
- edit ~/.juju/environments.yaml to set "local" as default
- juju boostrap

this creates a file /etc/rsyslog.d/25-juju-USERNAME-local.conf and
restarts rsyslog. rsyslog then crashes like this with this
configuration.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.14.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Thu Jan 14 12:18:18 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/sbin/rsyslogd
ProcCmdline: /usr/sbin/rsyslogd -n
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7efcf17d196e:  mov0x58(%rax),%rax
 PC (0x7efcf17d196e) ok
 source "0x58(%rax)" (0x0058) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rsyslog
StacktraceTop:
 ?? () from /usr/lib/rsyslog/lmnsd_gtls.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
Title: rsyslogd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: rsyslog (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Summary changed:

- rsyslogd crashed with SIGSEGV
+ rsyslogd crashed with SIGSEGV with juju-local configuration

** Information type changed from Private to Public

** Also affects: juju-core (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534106] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1534106/+attachment/4549842/+files/StacktraceSource.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534106]

StacktraceTop:
 gtlsClientCertCallback (session=, req_ca_rdn=, 
nreqs=, sign_algos=, sign_algos_length=, st=0x7efceed3e720) at nsd_gtls.c:254
 call_get_cert_callback () from 
/tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 _gnutls_server_select_cert () from 
/tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 remove_unwanted_ciphersuites () from 
/tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 _gnutls_server_select_suite () from 
/tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534106] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1534106/+attachment/4549843/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1534106/+attachment/4549828/+files/CoreDump.gz

** Changed in: juju-core (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534106] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1534106/+attachment/4549841/+files/Stacktrace.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1524590] Re: package libaio1:i386 0.3.110-1 failed to install/upgrade: package libaio1:i386 is already installed and configured

2016-01-14 Thread Marc Deslauriers

*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libaio in Ubuntu.
https://bugs.launchpad.net/bugs/1524590

Title:
  package libaio1:i386 0.3.110-1 failed to install/upgrade: package
  libaio1:i386 is already installed and configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libaio/+bug/1524590/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1524590] Re: package libaio1:i386 0.3.110-1 failed to install/upgrade: package libaio1:i386 is already installed and configured

*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libaio in Ubuntu.
https://bugs.launchpad.net/bugs/1524590

Title:
  package libaio1:i386 0.3.110-1 failed to install/upgrade: package
  libaio1:i386 is already installed and configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libaio/+bug/1524590/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533639] Re: [ubuntu-cpc] please make /tmp a tmpfs in RAM

** Description changed:

  In Ubuntu, we have always cleared /tmp on every boot.
  
  As such, on servers, by default /tmp should actually be a tmpfs entirely
  in RAM, when there is enough memory in the system.  This threshold
  should be configurable by the end user (in cloud-init?), and default
  threshold of ~2GB.
  
  Read about tmpfs here:
  https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
  
  This has several advantages, mainly:
   * Performance - much faster read/write access to data in /tmp
+- especially if your disk is spinning media
+- and if you're on SSD, this feature extends the life of your flash by 
reducing your NAND flash writes
   * Security - sensitive data would be cleared from memory on boot, rather 
than written (leaked) to disk -- important for encryption scenarios
   * Power consumption - storing information in memory is more energy efficient 
than reading and writing to disk
  
  In scenarios where more space in /tmp is needed than available, one can
  compliment that tmpfs with 'sudo apt-get install swapspace' which will
- dynamically create/delete swapfile as necessary.
+ dynamically create/delete swapfile as necessary.  See:
+ http://manpg.es/swapspace

-- 
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/1533639

Title:
  [ubuntu-cpc] please make /tmp a tmpfs in RAM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1533639/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-01-14 Thread Tristan

Andrea, a DNS Leak is defined as any DNS traffic going outside your
VPN's assigned servers. Even if 8.8.8.8 goes through the VPN, it's still
leaking your traffic. https://www.dnsleaktest.com/what-is-a-dns-
leak.html

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1533639] Re: [ubuntu-cpc] please make /tmp a tmpfs in RAM

** Description changed:

  In Ubuntu, we have always cleared /tmp on every boot.
  
  As such, on servers, by default /tmp should actually be a tmpfs entirely
  in RAM, when there is enough memory in the system.  This threshold
  should be configurable by the end user (in cloud-init?), and default
- threshold of ~2GB.
+ threshold of ~3GB.
  
  Read about tmpfs here:
  https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt
  
  This has several advantages, mainly:
   * Performance - much faster read/write access to data in /tmp
-- especially if your disk is spinning media
-- and if you're on SSD, this feature extends the life of your flash by 
reducing your NAND flash writes
+    - especially if your disk is spinning media
+    - and if you're on SSD, this feature extends the life of your flash by 
reducing your NAND flash writes
   * Security - sensitive data would be cleared from memory on boot, rather 
than written (leaked) to disk -- important for encryption scenarios
   * Power consumption - storing information in memory is more energy efficient 
than reading and writing to disk
  
  In scenarios where more space in /tmp is needed than available, one can
  compliment that tmpfs with 'sudo apt-get install swapspace' which will
  dynamically create/delete swapfile as necessary.  See:
  http://manpg.es/swapspace

-- 
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/1533639

Title:
  [ubuntu-cpc] please make /tmp a tmpfs in RAM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1533639/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534205] [NEW] cloud-initramfs-dyn-netconf should work without /etc/network/interfaces symlink

2016-01-14 Thread Scott Moser

Public bug reported:

See [1] for doc on cloud-initramfs-dyn-netconf.

cloud-initramfs-dyn-netconf takes klibc ipconfig output and writes 
/etc/network/interfaces (ENI) style file in /run/network/dynamic-interfaces.
The goal is to have the user's provided 'ip=' kernel parameters be "sticky" and 
not have the network interface get bounced by normal post-initramfs networking 
bringup.  Essentially kernel command line should override 
/etc/network/interfaces in a similar way to command line flags overriding 
environment or system configuration.

As it is right now, we have to have ln -sf /etc/network/interfaces 
/run/network/dynamic-interfaces in order for this to work.
That means:
 a.) if you've not done this, dyn-netconf isn't much use
 b.) if you *have* done this, but not provided ip= then you'll get you'll get 
no network configuration.

In xenial, the one necessary change from a cloud image to maas image is
this symlink, so that the image can work well with networking
information being provided on the kernel command line via network boot.

--
[1] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/dyn-netconf/doc/README.txt

** Affects: cloud-initramfs-tools (Ubuntu)
 Importance: High
 Status: Confirmed

** Changed in: cloud-initramfs-tools (Ubuntu)
   Status: New => Confirmed

** Changed in: cloud-initramfs-tools (Ubuntu)
   Importance: Undecided => High

** Description changed:

  See [1] for doc on cloud-initramfs-dyn-netconf.
  
  cloud-initramfs-dyn-netconf takes klibc ipconfig output and writes 
/etc/network/interfaces (ENI) style file in /run/network/dynamic-interfaces.
  The goal is to have the user's provided 'ip=' kernel parameters be "sticky" 
and not have the network interface get bounced by normal post-initramfs 
networking bringup.  Essentially kernel command line should override 
/etc/network/interfaces in a similar way to command line flags overriding 
environment or system configuration.
  
  As it is right now, we have to have ln -sf /etc/network/interfaces 
/run/network/dynamic-interfaces in order for this to work.
  That means:
-  a.) if you've not done this, dyn-netconf isn't much use
-  b.) if you *have* done this, but not provided ip= then you'll get you'll get 
no network configuration.
+  a.) if you've not done this, dyn-netconf isn't much use
+  b.) if you *have* done this, but not provided ip= then you'll get you'll get 
no network configuration.
+ 
+ In xenial, the one necessary change from a cloud image to maas image is
+ this symlink, so that the image can work well with networking
+ information being provided on the kernel command line via network boot.
  
  --
  [1] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/dyn-netconf/doc/README.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1534205

Title:
  cloud-initramfs-dyn-netconf should work without
  /etc/network/interfaces symlink

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1534205/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

I'll take this review (in progress).

-- 
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/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1524165] Re: merge with debian

2016-01-14 Thread Steve Langasek

Hi Michael,

The debdiff for 1.5.2-1ubuntu1 largely looks correct to me.  I have a
few small corrections:

- the changes to debian/copyright should be retained, these fix a real bug and 
should be upstreamed to Debian.
- the changes to debian/source/lintian-overrides should be retained, for the 
same reason.
- the debian/control contents have diverged from Debian quite a bit in matters 
of field ordering, whitespace, etc.  we can lose much of this delta with no 
change in semantics, so I think it's best to do this now when merging.
- Debian has added versioned Conflicts against golang-golang-x-tools, and 
golang-go.tools.  This is incorrect, these should be versioned Breaks/Replaces 
to ensure smooth upgrades with apt.  Since the Ubuntu package already had 
Breaks/Replaces, I restored this usage with updated version numbers.
- The golang-src package in Ubuntu Breaks/Replaces ancient versions of 
golang-go, but this has been dropped in Debian.  Unfortunately, these versions 
are not so ancient that they aren't newer than the version present in the 
trusty release pocket, so we should hang on to this until xenial is released.
- the changelog should document those changes that have been dropped and why 
(e.g., patches that are upstream and no longer needed here).
- Debian has added ppc64 to their list of archs where they build golang; so we 
should extend our list of "go archs" to include this one for better 
upstreamability to Debian.

Please let me know whether you agree with these changes (in the attached
debdiff) or whether you think further revision is needed before upload.

** Patch added: "golang-1524164-mergier-slangasek.diff"
   
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+attachment/4550305/+files/golang-1524164-mergier-slangasek.diff

-- 
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/1524165

Title:
  merge with debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

2016-01-14 Thread Steve Langasek

Louis, I second Robie's comments. Here is an interdiff between your
merge, and what I think the merge should be. This addresses Robie's
comments about the changelog having incomplete documentation of the
remaining delta; it also includes the following changes relative to your
merge diff:

- nut-{cgi,server}.postinst: the existing delta with Debian is bad form,
adduser is designed to be called unconditionally. Not strictly speaking part
of the merge, but something I spotted along the way that I think it's important
to fix. Along the way, I fixed up the changelog explanation for why this is
still needed (since we no longer do upgrades from hardy, if that were the only
reason we could drop the delta).
- debian/patches/backport-fix-lp753661.patch has been a pointless diff for
several upstream releases. The patch still applies, but upstream fixed the
issue differently (using rtrim() ).
- as Robie noted, you say the udev delta is dropped, but the delta to
debian/rules still exists. I've dropped the delta, with more explanation in
the changelog to why it can be dropped.
- the changes from 2.7.7-1ubuntu5 are restored, as still required.

Please have a look at my delta, and let me know if you agree with these
changes. If you see anything you disagree with, let's discuss. If you
do agree with these changes, please make sure you understand the source
of these differences on your side. Then I can sponsor the upload if
we're in agreement.

BTW, one thing I notice in the Ubuntu delta that I didn't yet address in
the merge is that the apport hooks are installed in wrong paths. There
is no source package named nut-client or nut-server, installing those
files is a no-op. Also not a question of the merge, but I would gladly
take a patch fixing this as part of sponsoring the upload.

** Patch added: "nut-1522346-mergier-slangasek.diff"

https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+attachment/4550146/+files/nut-1522346-mergier-slangasek.diff

--
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/1522346

Title:
Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534368] Re: HTTP/2 is not enabled for nginx-extras

Also, I'm pretty certain we *did* remove HTTP/2 from the module list in
the description.  I remember doing that myself.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1534368

Title:
  HTTP/2 is not enabled for nginx-extras

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534368/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534429] [NEW] Invalid doc-base file php-structures-graph

2016-01-14 Thread Logan Rosen

Public bug reported:

Imported from Debian bug http://bugs.debian.org/809325:

Package: php-pear
Version: 5.6.16+dfsg-2
Severity: normal
File: /usr/share/doc-base/php-structures-graph

When installing php-pear, I get a warning the the above file is invalid.

# install-docs --verbose --check /usr/share/doc-base/php-structures-graph
Warning in `/usr/share/doc-base/php-structures-graph', line 8: file 
`/usr/share/doc/php-pear/PEAR/Structures_Graph/docs/html/index.html' does not 
exist.
Error in `/usr/share/doc-base/php-structures-graph', line 8: all `Format' 
sections are invalid.
/usr/share/doc-base/php-structures-graph: Fatal error found, the file won't be 
registered.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php-pear depends on:
ii  php5-cli 5.6.16+dfsg-2
ii  php5-common  5.6.16+dfsg-2

Versions of packages php-pear recommends:
ii  gnupg  1.4.20-1

Versions of packages php-pear suggests:
pn  php5-dev  

-- no debconf information

** Affects: php5 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: php5 (Debian)
 Importance: Undecided
 Status: New

** Bug watch added: Debian Bug tracker #809325
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809325

** Changed in: php5 (Debian)
 Remote watch: None => Debian Bug tracker #809325

** Description changed:

  Imported from Debian bug http://bugs.debian.org/809325:
  
- < attachments at 140117114577168>: []
+ Package: php-pear
+ Version: 5.6.16+dfsg-2
+ Severity: normal
+ File: /usr/share/doc-base/php-structures-graph
+ 
+ When installing php-pear, I get a warning the the above file is invalid.
+ 
+ # install-docs --verbose --check /usr/share/doc-base/php-structures-graph
+ Warning in `/usr/share/doc-base/php-structures-graph', line 8: file 
`/usr/share/doc/php-pear/PEAR/Structures_Graph/docs/html/index.html' does not 
exist.
+ Error in `/usr/share/doc-base/php-structures-graph', line 8: all `Format' 
sections are invalid.
+ /usr/share/doc-base/php-structures-graph: Fatal error found, the file won't 
be registered.
+ 
+ 
+ 
+ -- System Information:
+ Debian Release: stretch/sid
+   APT prefers unstable
+   APT policy: (500, 'unstable'), (200, 'experimental')
+ Architecture: amd64 (x86_64)
+ Foreign Architectures: i386
+ 
+ Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
+ Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
+ Shell: /bin/sh linked to /bin/dash
+ Init: systemd (via /run/systemd/system)
+ 
+ Versions of packages php-pear depends on:
+ ii  php5-cli 5.6.16+dfsg-2
+ ii  php5-common  5.6.16+dfsg-2
+ 
+ Versions of packages php-pear recommends:
+ ii  gnupg  1.4.20-1
+ 
+ Versions of packages php-pear suggests:
+ pn  php5-dev  
+ 
+ -- no debconf information

-- 
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/1534429

Title:
  Invalid doc-base file php-structures-graph

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1534429/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534368] Re: HTTP/2 is not enabled for nginx-extras

Ooops, my bad, I did miss the removal from the description of nginx-
extras... reopening because i'm working on it in the next merge.

** Changed in: nginx (Ubuntu)
   Importance: Undecided => Low

** Changed in: nginx (Ubuntu)
   Status: Won't Fix => In Progress

** Changed in: nginx (Ubuntu)
 Assignee: (unassigned) => Thomas Ward (teward)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1534368

Title:
  HTTP/2 is not enabled for nginx-extras

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534368/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

2016-01-14 Thread Mathew Hodson

** Changed in: corosync (Ubuntu)
   Importance: Undecided => Medium

** Changed in: corosync (Ubuntu Trusty)
   Importance: Undecided => Medium

-- 
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/1530837

Title:
  Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running
  corosync -v

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534346] Re: FTBFS with golang-go 1.6 beta2

2016-01-14 Thread Launchpad Bug Tracker

This bug was fixed in the package golang-x-text -
0+git20151217.cf49866-0ubuntu1

---
golang-x-text (0+git20151217.cf49866-0ubuntu1) xenial; urgency=high

  * New upstream snapshot, resolving FTBFS with golang 1.6. (LP: #1534346)
  * Fix gen-orig-tgz to work on wily.

 -- Dimitri John Ledkov   Thu, 14 Jan 2016 22:33:25
+

** Changed in: golang-x-text (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-x-text in Ubuntu.
https://bugs.launchpad.net/bugs/1534346

Title:
  FTBFS with golang-go 1.6 beta2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/consul-migrate/+bug/1534346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534368] Re: HTTP/2 is not enabled for nginx-extras

Working As Intended, and we're not enabling it at this time due to a
request/mandate from the Security Team at this time.  Read the answer I
wrote to this question, and the links included in there, to explain why
it is currently disabled:
https://answers.launchpad.net/ubuntu/+source/nginx/+question/280708

** Changed in: nginx (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1534368

Title:
  HTTP/2 is not enabled for nginx-extras

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534368/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534368] Re: HTTP/2 is not enabled for nginx-extras

** Description changed:

  The package description for nginx-extras in Ubuntu Xenial falsely claims
  that it has HTTP/2 support, even though when --enable-http_v2_module was
  removed from common_configure_flags, nginx-extras isn't compiled with
  HTTP/2.
  
  Two solutions:
- * Actually add HTTP/2 support (my preference)
+ * Actually add HTTP/2 support (will not happen at this time, per Security 
Team)
  * Remove HTTP/2 from module list in description

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1534368

Title:
  HTTP/2 is not enabled for nginx-extras

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534368/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534340] Re: openssh server 6.6 does not report max auth failures

2016-01-14 Thread Kees Cook

** Changed in: openssh (Ubuntu Trusty)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1534340

Title:
  openssh server 6.6 does not report max auth failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1534340/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2016-01-14 Thread DaveHenson

I'm glad to see that I am not the only one fighting this issue on Ubuntu
15.10.  This is a real show stopper to this being brought into a
production environment. I found the same as post from Tristan on
2015-12-11.  I CAN run command line but it is a pain to enter my
username/pwd every time I need to launch VPN.  There is definitely a bug
in how the network manager runs openvpn.

Surprised to see this has been open over 2 years.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/120

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534208] Re: Please merge 1.9.9-1 (main) from Debian Unstable (main)

Additional bugs being squished with the merge, because they're
extraordinarily minor:

* Bug #1534368 - HTTP/2 was still described in the nginx-extras package,
even though it's disabled. Oversight caused this to get missed, will be
rectified here.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1534208

Title:
  Please merge 1.9.9-1 (main) from Debian Unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534208/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start"

2016-01-14 Thread Mathew Hodson

** Changed in: ntp (Ubuntu Precise)
   Status: New => Triaged

** Changed in: ntp (Ubuntu Trusty)
   Status: New => Triaged

-- 
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/1125726

Title:
  boot-time race between /etc/network/if-up.d/ntpdate and
  "/etc/init.d/ntp start"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1524165] Re: merge with debian

2016-01-14 Thread Michael Hudson-Doyle

Hi Steve,

Thanks for the very thorough review!

On 15 January 2016 at 16:47, Steve Langasek
 wrote:
> Hi Michael,
>
> The debdiff for 1.5.2-1ubuntu1 largely looks correct to me.  I have a
> few small corrections:
>
> - the changes to debian/copyright should be retained, these fix a real bug 
> and should be upstreamed to Debian.

Already done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807304
(so I guess this bug number should be added to d/copyright?)

> - the changes to debian/source/lintian-overrides should be retained,
for the same reason.

OK.

> - the debian/control contents have diverged from Debian quite a bit in
matters of field ordering, whitespace, etc.  we can lose much of this
delta with no change in semantics, so I think it's best to do this now
when merging.

Thanks.

> - Debian has added versioned Conflicts against golang-golang-x-tools,
and golang-go.tools.  This is incorrect, these should be versioned
Breaks/Replaces to ensure smooth upgrades with apt.  Since the Ubuntu
package already had Breaks/Replaces, I restored this usage with updated
version numbers.

I did wonder about this and assumed Debian was more likely to be
correct than me. Apparently not!

> - The golang-src package in Ubuntu Breaks/Replaces ancient versions of
golang-go, but this has been dropped in Debian.  Unfortunately, these
versions are not so ancient that they aren't newer than the version
present in the trusty release pocket, so we should hang on to this until
xenial is released.

Er, yes they are? The versions being broke/replaced is 2:1-3~ and
trusty has 2:1.2.1-2ubuntu1 (which has the breaks/replaces of 2:1-3~
already). So I think this really can be dropped (it even seems
*precise* has a newer version than 1-3 :-)).

Of course it's pretty harmless to keep too.

> - the changelog should document those changes that have been dropped
and why (e.g., patches that are upstream and no longer needed here).

OK. Thanks.

> - Debian has added ppc64 to their list of archs where they build
golang; so we should extend our list of "go archs" to include this one
for better upstreamability to Debian.

Good spotting.

> Please let me know whether you agree with these changes (in the attached
> debdiff) or whether you think further revision is needed before upload.

I guess I'd ask you to:

1) re-delete the breaks of golang-src
2) remove mention of same from changelog
3) add the bug number for the copyright changes to changelog

and upload away! And then we can do the 1.5.3 merge, but m-o-m should
get that right.

Cheers,
mwh

> ** Patch added: "golang-1524164-mergier-slangasek.diff"
>
> https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+attachment/4550305/+files/golang-1524164-mergier-slangasek.diff
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1524165
>
> Title:
>   merge with debian
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+subscriptions

-- 
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/1524165

Title:
  merge with debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1524165] Re: merge with debian

2016-01-14 Thread Michael Hudson-Doyle

** Bug watch added: Debian Bug tracker #807304
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807304

-- 
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/1524165

Title:
  merge with debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534368] [NEW] HTTP/2 is not enabled for nginx-extras

2016-01-14 Thread Laine Gholson

Public bug reported:

The package description for nginx-extras in Ubuntu Xenial falsely claims
that it has HTTP/2 support, even though when --enable-http_v2_module was
removed from common_configure_flags, nginx-extras isn't compiled with
HTTP/2.

Two solutions:
* Actually add HTTP/2 support (my preference)
* Remove HTTP/2 from module list in description

** Affects: nginx (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: armhf xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1534368

Title:
  HTTP/2 is not enabled for nginx-extras

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1534368/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534487] [NEW] cgroup change failed (freezer) when using sudo

2016-01-14 Thread Dean Henrichsmeyer

Public bug reported:

When running 'sudo su -' I got the following error:

call to remove-on-empty (freezer:3) failed: invalid request

It was mentioned to me that this might be cgmanager racing with systemd
due to some recent changes in libpam-cgm. I don't know how relevant that
is though.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cgmanager 0.39-2ubuntu3
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 15 09:45:54 2016
InstallationDate: Installed on 2015-11-03 (72 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: cgmanager
UpgradeStatus: Upgraded to xenial on 2015-12-07 (38 days ago)

** Affects: cgmanager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1534487

Title:
  cgroup change failed (freezer) when using sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1534487/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

2016-01-14 Thread Steve Langasek

** Changed in: nut (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
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/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1349888] Re: [SRU] Attempting to attach the same volume multiple times can cause bdm record for existing attachment to be deleted.

2016-01-14 Thread Matt Riedemann

** Tags removed: icehouse-backport-potential

-- 
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/1349888

Title:
  [SRU] Attempting to attach the same volume multiple times can cause
  bdm record for existing attachment to be deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1349888/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)