[Bug 1554556] Re: dhclient crashes during startup

2016-03-21 Thread kukububu
Issues seems solved by isc-dhcp-client  4.3.3-5ubuntu11

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

Title:
  dhclient crashes during startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1554556/+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 1559912] [NEW] Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

2016-03-21 Thread ChristianEhrhardt
Public bug reported:

*as a start same text as my reach for the involved project mailing
lists*

I was trying to replicate a setup that I have working on physical devices
(ixgbe) under kvm since there is a virtio pmd driver.

TL;DR:
- under KVM with virtio-pci (working on baremetal with ixgbe cards)
- adding dpdk port to ovs fails with memzone  already exists
and causes a segfault
- I couldn't find a solution in similar mails that popped up here recently,
any help or pointer appreciated.

## Details ##
I thought I've read that others have it working I thought that would be a
great way to gain more debug control of the environment, but something
seems to be eluding me.

There were quite some similar mails on the List recently, but none seemed
to hit the same issue as I do. At least none of the tunings/workarounds
seemed to apply to me.
As versions I have Openvswitch 2.5, DPDK 2.2, Qemu 2.5, Kernel 4.4 - so a
fairly recent software stack.

The super-short repro summary is:
1. starting ovs-dpdk like
ovs-vswitchd --dpdk -c 0x1 -n 4 --pci-blacklist :00:03.0 -m 2048 --
unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info
--mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log
--pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor
2. add a bridge and a ovs dpdk port
ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk
ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk

The log of the initialization after #1 looks good to me - I can see two of
my three virtio devices recognized and one blacklisted.
Memory allocation looks good, ... I'll attach the log at the end of the mail

## ISSUE ##
But when I add a port and refer to one of the dpdk ports it fails with the
following:
ovs-vsctl[14023]: ovs|1|vsctl|INFO|Called as ovs-vsctl add-port
ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk
ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
 already exists
ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
 already exists
ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
 already exists
kernel: show_signal_msg: 18 callbacks suppressed
kernel: pmd12[14025]: segfault at 2 ip 7f3eb205eab2 sp 7f3e3dffa590
error 4 in libdpdk.so.0[7f3eb1fdf000+1e9000]
ovs-vswitchd[13902]: ovs|3|daemon_unix(monitor)|ERR|1 crashes: pid
13903 died, killed (Segmentation fault), core dumped, restarting
systemd-udevd[14040]: Could not generate persistent MAC address for
ovs-netdev: No such file or directory
kernel: device ovs-netdev entered promiscuous mode
ovs-vswitchd[14036]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
 already exists
ovs-vswitchd[14036]: RING: Cannot reserve memory
kernel: device ovsdpdkbr0 entered promiscuous mode
ovs-vswitchd[14036]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
 already exists
ovs-vswitchd[14036]: RING: Cannot reserve memory

## Experiments (failed) ##
I thought it could be related to all the multiqueue chances that recently
going in.
My usual setup has 4 vCPUs and 4 queues per virtio-net device.
I tried them with only 1 of 4 queues, also with only 1 queue defined and
only 1 CPU - but all fail the same way.
I have testpmd and l2fwd on the same devices working, so I hope they are
not totally set up badly.

I also tried hilarious things like reassigning to uio_pci_generic before,
but well its virtio_pmd eventually anyways - so it made no difference.

>From how it appears I felt that it could be related to the old discussions
around
[1] http://dpdk.org/ml/archives/dev/2015-May/017589.html
[2] http://openvswitch.org/pipermail/dev/2015-March/052344.html
But they are (partially) applied upstream already and the issue doesn't
100% match the old discussions.

## Logs ##
[3] log of openvswitch start (attached for more readability)


This needs to be debugged and fixed or openvswitch-dpdk it will be unusable 
within virtio environments.

Upstream discussion started:
http://dpdk.org/ml/archives/dev/2016-March/036021.html
http://openvswitch.org/pipermail/discuss/2016-March/020488.html

** Affects: dpdk (Ubuntu)
 Importance: Critical
 Assignee: ChristianEhrhardt (paelzer)
 Status: Triaged

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

Title:
  Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559912/+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 1559912] Re: Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

2016-03-21 Thread ChristianEhrhardt
It was also reported in 1559408 that this also affects BNX2X_PMD

** Description changed:

  *as a start same text as my reach for the involved project mailing
  lists*
  
  I was trying to replicate a setup that I have working on physical devices
  (ixgbe) under kvm since there is a virtio pmd driver.
  
  TL;DR:
  - under KVM with virtio-pci (working on baremetal with ixgbe cards)
  - adding dpdk port to ovs fails with memzone  already exists
  and causes a segfault
  - I couldn't find a solution in similar mails that popped up here recently,
  any help or pointer appreciated.
  
  ## Details ##
  I thought I've read that others have it working I thought that would be a
  great way to gain more debug control of the environment, but something
  seems to be eluding me.
  
  There were quite some similar mails on the List recently, but none seemed
  to hit the same issue as I do. At least none of the tunings/workarounds
  seemed to apply to me.
  As versions I have Openvswitch 2.5, DPDK 2.2, Qemu 2.5, Kernel 4.4 - so a
  fairly recent software stack.
  
  The super-short repro summary is:
  1. starting ovs-dpdk like
  ovs-vswitchd --dpdk -c 0x1 -n 4 --pci-blacklist :00:03.0 -m 2048 --
  unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info
  --mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log
  --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor
  2. add a bridge and a ovs dpdk port
  ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk
  ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk
  
  The log of the initialization after #1 looks good to me - I can see two of
  my three virtio devices recognized and one blacklisted.
  Memory allocation looks good, ... I'll attach the log at the end of the mail
  
- 
  ## ISSUE ##
  But when I add a port and refer to one of the dpdk ports it fails with the
  following:
  ovs-vsctl[14023]: ovs|1|vsctl|INFO|Called as ovs-vsctl add-port
  ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk
  ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
   already exists
  ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
   already exists
  ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
   already exists
  kernel: show_signal_msg: 18 callbacks suppressed
  kernel: pmd12[14025]: segfault at 2 ip 7f3eb205eab2 sp 7f3e3dffa590
  error 4 in libdpdk.so.0[7f3eb1fdf000+1e9000]
  ovs-vswitchd[13902]: ovs|3|daemon_unix(monitor)|ERR|1 crashes: pid
  13903 died, killed (Segmentation fault), core dumped, restarting
  systemd-udevd[14040]: Could not generate persistent MAC address for
  ovs-netdev: No such file or directory
  kernel: device ovs-netdev entered promiscuous mode
  ovs-vswitchd[14036]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
   already exists
  ovs-vswitchd[14036]: RING: Cannot reserve memory
  kernel: device ovsdpdkbr0 entered promiscuous mode
  ovs-vswitchd[14036]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone
   already exists
  ovs-vswitchd[14036]: RING: Cannot reserve memory
  
- 
  ## Experiments (failed) ##
  I thought it could be related to all the multiqueue chances that recently
  going in.
  My usual setup has 4 vCPUs and 4 queues per virtio-net device.
  I tried them with only 1 of 4 queues, also with only 1 queue defined and
  only 1 CPU - but all fail the same way.
  I have testpmd and l2fwd on the same devices working, so I hope they are
  not totally set up badly.
  
  I also tried hilarious things like reassigning to uio_pci_generic before,
  but well its virtio_pmd eventually anyways - so it made no difference.
  
  >From how it appears I felt that it could be related to the old discussions
  around
  [1] http://dpdk.org/ml/archives/dev/2015-May/017589.html
  [2] http://openvswitch.org/pipermail/dev/2015-March/052344.html
  But they are (partially) applied upstream already and the issue doesn't
  100% match the old discussions.
  
- 
  ## Logs ##
- [3] log of openvswitch start:
- systemd[1]: Starting Open vSwitch Internal Unit...
- ovs-ctl[13868]:  * Starting ovsdb-server
- ovs-vsctl[13893]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait --
- init -- set Open_vSwitch . db-version=7.12.1
- ovs-vsctl[13898]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait set
- Open_vSwitch . ovs-version=2.5.0
- "external-ids:system-id=\"8ddb892c-53a5-410d-a765-0031ad6eb1be\""
- "system-type=\"Ubuntu\"" "system-version=\"16.04-xenial\""
- ovs-ctl[13868]:  * Configuring Open vSwitch system IDs
- ovs-ctl[13868]: 2016-03-18T14:28:28Z|1|dpdk|INFO|No -vhost_sock_dir
- provided - defaulting to /var/run/openvswitch
- ovs-vswitchd[13900]: ovs|1|dpdk|INFO|No -vhost_sock_dir provided -
- defaulting to /var/run/openvswitch
- ovs-ctl[13868]: EAL: Detected lcore 0 as core 0 on socket 0
- ovs-ctl[13868]: EAL: Detected lcore 1 as core 0 on socket 0
- ovs-ctl[13868]: EAL: Detected 

[Bug 1559912] Re: Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

2016-03-21 Thread ChristianEhrhardt
systemd[1]: Starting Open vSwitch Internal Unit...
ovs-ctl[13868]:  * Starting ovsdb-server
ovs-vsctl[13893]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait --
init -- set Open_vSwitch . db-version=7.12.1
ovs-vsctl[13898]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait set
Open_vSwitch . ovs-version=2.5.0
"external-ids:system-id=\"8ddb892c-53a5-410d-a765-0031ad6eb1be\""
"system-type=\"Ubuntu\"" "system-version=\"16.04-xenial\""
ovs-ctl[13868]:  * Configuring Open vSwitch system IDs
ovs-ctl[13868]: 2016-03-18T14:28:28Z|1|dpdk|INFO|No -vhost_sock_dir
provided - defaulting to /var/run/openvswitch
ovs-vswitchd[13900]: ovs|1|dpdk|INFO|No -vhost_sock_dir provided -
defaulting to /var/run/openvswitch
ovs-ctl[13868]: EAL: Detected lcore 0 as core 0 on socket 0
ovs-ctl[13868]: EAL: Detected lcore 1 as core 0 on socket 0
ovs-ctl[13868]: EAL: Detected lcore 2 as core 0 on socket 0
ovs-ctl[13868]: EAL: Detected lcore 3 as core 0 on socket 0
ovs-ctl[13868]: EAL: Support maximum 128 logical core(s) by configuration.
ovs-ctl[13868]: EAL: Detected 4 lcore(s)
ovs-ctl[13868]: EAL: No free hugepages reported in hugepages-1048576kB
ovs-ctl[13868]: EAL: VFIO modules not all loaded, skip VFIO support...
ovs-ctl[13868]: EAL: Setting up physically contiguous memory...
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3eaf80 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x5ac0 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e54a0 (size =
0x5ac0)
ovs-ctl[13868]: EAL: Ask a virtual area of 0xc0 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e53c0 (size = 0xc0)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x120 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e5280 (size = 0x120)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x40 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e5220 (size = 0x40)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e51e0 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x40 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e5180 (size = 0x40)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e5140 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0xc0 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e5060 (size = 0xc0)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x100 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e4f40 (size = 0x100)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e4f00 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e4ec0 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e4e80 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e4e40 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x40 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e4de0 (size = 0x40)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3e4da0 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x5ac0 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3df2c0 (size =
0x5ac0)
ovs-ctl[13868]: EAL: Ask a virtual area of 0xc0 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3df1e0 (size = 0xc0)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x40 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3df180 (size = 0x40)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x100 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3df060 (size = 0x100)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3df020 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x40 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3defc0 (size = 0x40)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3def80 (size = 0x20)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x40 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3def20 (size = 0x40)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x60 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3deea0 (size = 0x60)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x180 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3ded00 (size = 0x180)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x60 bytes
ovs-ctl[13868]: EAL: Virtual area found at 0x7f3dec80 (size = 0x60)
ovs-ctl[13868]: EAL: Ask a virtual area of 0x20 bytes
ovs-ctl[13868]: EAL: 

[Bug 1559408] Re: Many PMD driver options are disabled, including "BNX2X"!

2016-03-21 Thread ChristianEhrhardt
Since I consider the extra PMDs kind of "unsupported" upstream I have to
rate it low for now.

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

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

Title:
  Many PMD driver options are disabled, including "BNX2X"!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559408/+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 1559408] Re: Many PMD driver options are disabled, including "BNX2X"!

2016-03-21 Thread ChristianEhrhardt
Hi Thiago,
you were busy weren't you :-)

Thanks your further experiments and reports - I'll try to refer all the open 
points.
Trying to summarize:

1. The vfio grouping issue is not a bug, just the vfio setup being more complex 
in general. But you already handled that for your setup - great.
But as you found - eventually a working vfio and a uio_pci_generic gets you to 
the same - the PMD driver (trying to) work on the card.


2. Firmware issue - that is very specific to the BNX2X_PMD PMD and Cards you 
use.
I'd consider adding something to the Readme if we end up enabling that driver, 
but not really considering pushing oco FW packages with dpdk. Yet that should 
help the next getting to it.


3. Enabling this or other PMDs.
You already did for for your experiments which is great, but so far we only 
enabled those that were enabled by default and only a few that different 
parties have asked for. There are some reasons not "just" to enable all others.
- One is testability - I don't have all the HW and also time is short while 
still more issue being open against dpdk.
- the other one is that a lessons learned is that everything that is not 
actively used/tested is broken or at least can not be considered very stable.
As dpdk by history came from a "build the solution with the dpdk source" 
approach where he specific solution setup can apply a multitude of tweaks/fixes 
without caring about "others" too much that is not a good option for a 
generically provided package.
On the good side though, until the specific cards PMD driver is used the code 
is not really active.
Unfortunately I don't see a good option of saying something like "and these 5 
more PMD are experimental" - I need to discuss that with more experienced 
packagers.
Maybe an extra package that brings "more" pmd drivers named dpdk-experimental, 
but that would due to its dependencies still have to be in main which I don't 
like. Also this is not working well with the combined library approach being 
used and linker script based solution is post dpdk 2.2

4.  segfault/mem alloc issue
That is an interesting one which I was working on last week as well.
In fact this is not specific to your PMD driver - I was hitting that with 
virtio-pci based setup which should be "more" supported (default enabled by 
upstream dpdk). It is an issue that as far as I can tell only occurs in 
combination with OVS-DPDK (testpmd and such are running fine).
I was just about filing a bug to track that effort - please see 1559912


Final summary:
- I'll discuss if it is doable/reasonable to enable so more low-tested extra 
drivers with some co-devs here for this bug.
- We will track the issues regarding ovs-dpdk+dpdk+some-PMDs in bug 1559912

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

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

Title:
  Many PMD driver options are disabled, including "BNX2X"!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559408/+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 1553023] Re: [FFe] libvirt v1.3.2 -- zfs support

2016-03-21 Thread Serge Hallyn
** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [FFe] libvirt v1.3.2 -- zfs support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1553023/+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 1559935] [NEW] [SRU] nova 12.0.2, keystone 8.1.0

2016-03-21 Thread James Page
Public bug reported:

Point release available for Liberty for nova and keystone.

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

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

Title:
  [SRU] nova 12.0.2, keystone 8.1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1559935/+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 1559408] Re: Many PMD driver options are disabled, including "BNX2X"!

2016-03-21 Thread ChristianEhrhardt
As an example what I meant to imply here the reason why it is disabled
by default as of now.

commit ce9b8bb8b99877026fcca00fdb253fa3ec3a7e06
Author: Thomas Monjalon 
Date:   Tue Jul 28 18:22:39 2015 +0200

config: disable bnx2x driver

This driver has too many issues:
- too big
- bad coding style
- no git history (dropped in 2 patches)
- no documentation
- no BSD support
- no maintainer
And the biggest one, constraining this disabling:
- many build issues

If the last 4 issues are not fixed in the next release 2.2,
the driver must be removed.

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

Title:
  Many PMD driver options are disabled, including "BNX2X"!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559408/+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 1559935] Re: [SRU] nova 12.0.2, keystone 8.1.0

2016-03-21 Thread James Page
** Also affects: keystone (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: keystone (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/liberty
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/liberty
   Status: New => Triaged

** Changed in: cloud-archive
   Status: New => Invalid

** Changed in: cloud-archive/liberty
   Importance: Undecided => Medium

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

Title:
  [SRU] nova 12.0.2, keystone 8.1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1559935/+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 1559847] Re: smbd crashed with SIGABRT in strlen()

2016-03-21 Thread Apport retracing service
*** This bug is a duplicate of bug 1514766 ***
https://bugs.launchpad.net/bugs/1514766

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1514766, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1559847/+attachment/4606145/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1559847/+attachment/4606148/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1559847/+attachment/4606149/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1559847/+attachment/4606150/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1559847/+attachment/4606152/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1559847/+attachment/4606153/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1514766
   smbd crashed with SIGABRT in strlen() while accessing a share from a W7 
client

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  smbd crashed with SIGABRT in strlen()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1559847/+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 1559912] Re: Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

2016-03-21 Thread ChristianEhrhardt
** Also affects: openvswitch-dpdk (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559912/+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 1557156] Re: [MIR] voluptuous

2016-03-21 Thread Steve Langasek
Override component to main
voluptuous 0.8.8-1ubuntu1 in xenial: universe/misc -> main
python-voluptuous 0.8.8-1ubuntu1 in xenial amd64: universe/python/optional/100% 
-> main
python-voluptuous 0.8.8-1ubuntu1 in xenial arm64: universe/python/optional/100% 
-> main
python-voluptuous 0.8.8-1ubuntu1 in xenial armhf: universe/python/optional/100% 
-> main
python-voluptuous 0.8.8-1ubuntu1 in xenial i386: universe/python/optional/100% 
-> main
python-voluptuous 0.8.8-1ubuntu1 in xenial powerpc: 
universe/python/optional/100% -> main
python-voluptuous 0.8.8-1ubuntu1 in xenial ppc64el: 
universe/python/optional/100% -> main
python-voluptuous 0.8.8-1ubuntu1 in xenial s390x: universe/python/optional/100% 
-> main
python3-voluptuous 0.8.8-1ubuntu1 in xenial amd64: 
universe/python/optional/100% -> main
python3-voluptuous 0.8.8-1ubuntu1 in xenial arm64: 
universe/python/optional/100% -> main
python3-voluptuous 0.8.8-1ubuntu1 in xenial armhf: 
universe/python/optional/100% -> main
python3-voluptuous 0.8.8-1ubuntu1 in xenial i386: universe/python/optional/100% 
-> main
python3-voluptuous 0.8.8-1ubuntu1 in xenial powerpc: 
universe/python/optional/100% -> main
python3-voluptuous 0.8.8-1ubuntu1 in xenial ppc64el: 
universe/python/optional/100% -> main
python3-voluptuous 0.8.8-1ubuntu1 in xenial s390x: 
universe/python/optional/100% -> main
15 publications overridden.


** Changed in: voluptuous (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] voluptuous

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/voluptuous/+bug/1557156/+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 1558576] Re: OpenSSH Error "Disconnecting: Hash's MIC didn't verify" after upgrading to Ubuntu 16.04

2016-03-21 Thread Bug Watch Updater
** Changed in: openssh (Debian)
   Status: New => Fix Released

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

Title:
  OpenSSH Error "Disconnecting: Hash's MIC didn't verify" after
  upgrading to Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1558576/+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 1560148] Re: [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Serge Hallyn
Thanks, the debdiff looks fine to me.  Will sponsor this when the FFE is
approved.

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+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 1560148] Re: [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Serge Hallyn
@Nish,

is there a particular bug in the package which this fixes, or is this
purely to have a closer package to debian's in 16.04?

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+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 1559307] Re: [SRU] update walinuxagent to 2.1.3 in Wily

2016-03-21 Thread Chris J Arges
Hello Robert, or anyone else affected,

Accepted walinuxagent into wily-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/walinuxagent/2.1.3-0ubuntu4~15.10.0
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: walinuxagent (Ubuntu Wily)
   Status: New => Fix Committed

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

Title:
  [SRU] update walinuxagent to 2.1.3 in Wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1559307/+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 1539543] Re: [Ubuntu 16.04] librtas package update

2016-03-21 Thread Diane Brent
Per quick discussion with Hohnbaum 3/17, this is on track for 16.04. No
issues on Canonical side, just working the queue of requests.

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

Title:
  [Ubuntu 16.04] librtas package update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librtas/+bug/1539543/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

2016-03-21 Thread Corey Bryant
** Changed in: designate (Ubuntu)
   Status: New => Fix Released

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

Title:
  Replace assertEqual(None, *) with assertIsNone in tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/anchor/+bug/1280522/+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 1555700] Re: [FFE] Please merge tgt 1.0.63 from Debian (unstable)

2016-03-21 Thread Ryan Harper
Linking against libaio allows tgt to use libaio as a backend for submitting IO 
to the backing device.
The default backend uses pread64/pwrite64.  Adding an additional backed does 
not change this default

For users to consume the aio backend, they must specify the backend type
via command line switch (from tgtadm manpage):

-E, --bstype 
   When creating a LUN, this parameter specifies the type of backend
   storage to to use.

I believe that aio is out of the way for default users.  I'd like to get
some testing done on the aio backend before we say we'll support it.

-- 
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:
  [FFE] Please merge tgt 1.0.63 from Debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+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 1486335] Re: Create nova.conf with tox -egenconfig : ValueError: ("Expected ',' or end-of-list in", "Routes!=2.0,!=2.1,>=1.12.3; python_version=='2.7'", 'at', "; python_version=='2.7'")

2016-03-21 Thread Corey Bryant
I'm going to re-target this at the upstream Designate project since it
doesn't appear to have anything to do with the Ubuntu Designate package.
Ubuntu packages don't use pip or tox.

** Also affects: designate
   Importance: Undecided
   Status: New

** No longer affects: designate (Ubuntu)

** Also affects: designate (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: designate

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

Title:
  Create nova.conf with tox -egenconfig :ValueError: ("Expected ','
  or end-of-list in",
  "Routes!=2.0,!=2.1,>=1.12.3;python_version=='2.7'", 'at',
  ";python_version=='2.7'")

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1486335/+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 1559307] Re: [SRU] update walinuxagent to 2.1.3 in Wily

2016-03-21 Thread Robert C Jennings
** Changed in: walinuxagent (Ubuntu)
Milestone: wily-updates => ubuntu-16.04

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

Title:
  [SRU] update walinuxagent to 2.1.3 in Wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1559307/+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 1500006] Re: irqbalance crashes when CPUs are taken offline manually

2016-03-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: irqbalance (Ubuntu)
   Status: New => Confirmed

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

Title:
  irqbalance crashes when CPUs are taken offline manually

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/156/+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 1552983] Re: Please merge logwatch 7.4.2-1 from Debian

2016-03-21 Thread Ubuntu Foundations Team Bug Bot
The attachment "logwatch_7.4.2-1.7.4.2-1ubuntu1.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Please merge logwatch 7.4.2-1 from Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1552983/+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 1560120] Re: Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Serge Hallyn
Confirmed, i can reproduce.  Now why.

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

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1555060] Re: the "pecl" command that is installed, does not work for PHP 7

2016-03-21 Thread Nish Aravamudan
Please update your installation to the latest 16.04, which has php-pear
1.10.1+submodules+notgz-4, and fixes this particular issue.

** Package changed: php5 (Ubuntu) => php-pear (Ubuntu)

** Changed in: php-pear (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: php-pear (Ubuntu)
   Status: New => Fix Released

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

Title:
  the "pecl" command that is installed, does not work for PHP 7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-pear/+bug/1555060/+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 1528251] Re: WARNING: no suitable primes in /etc/ssh/primes

2016-03-21 Thread Seth Arnold
OFERBA, I suspect you have a different issue than this bug report, which
is about a misleading pathname in an error message.

I'd suggest filing a new bug for your issue however I do not think it is
appropriate to be shipping a new release with 1024 bit DH primes as a
default supported configuration. See https://weakdh.org/ for more
information.

Thanks

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

Title:
  WARNING: no suitable primes in /etc/ssh/primes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1528251/+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 1560120] Re: Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Serge Hallyn
Hm,

 lxc-start 20160321163436.552 ERROR lxc_utils - utils.c:mkdir_p:253 -
Permission denied - failed to create directory '/sys/fs/cgroup/blkio/lxc
/libertine-smoke-test/lxc/'

This is odd, if that was not writeable then cgfsng should not have
stored it as a writeable hierarchy.

Just to make sure, can you show the container configuration for both
containers?

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1560120] Re: Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Serge Hallyn
** Changed in: lxc (Ubuntu)
   Importance: Undecided => High

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1560120] Re: Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Serge Hallyn
The proposed fix for this is https://github.com/lxc/lxcfs/pull/102

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1559912] Re: Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

2016-03-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: openvswitch-dpdk (Ubuntu)
   Status: New => Confirmed

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

Title:
  Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559912/+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 1522422] Re: Update to php 7.0

2016-03-21 Thread Nish Aravamudan
FYI, PHP 7.0 is in main now (7.0.4-5), and several extensions with
build-dependencies from universe are in universe. We are still working
on the removal of PHP5, but I think this bug can be marked fix release
as we are using other bugs to track specific actions.

** Changed in: php5 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Update to php 7.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1522422/+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 1555856] Re: move to per-Go-major version coinstallable packages

2016-03-21 Thread Michael Hudson-Doyle
As is always the way I found a few silly things in the package (wrong
bug syntax in changelog, overcomplication in a helper script,
override_dh_prep was calling dh_clean and not dh_prep) and uploaded a
+ppa1 package of golang-defaults. Can whoever sponsors the upload strip
off the +ppa1 before uploading? TIA

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

Title:
  move to per-Go-major version coinstallable packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1555856/+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 1560120] Re: Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Serge Hallyn
I believe this is due to lxcfs not implementing access(2).

** Also affects: lxcfs (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1555856] Re: move to per-Go-major version coinstallable packages

2016-03-21 Thread Michael Hudson-Doyle
The remaining packages are now in
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages

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

Title:
  move to per-Go-major version coinstallable packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1555856/+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 1557248] Re: OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code

2016-03-21 Thread Maciej Puzio
Patch created by OpenLDAP team applies cleanly to openldap 2.4.41+dfsg-
1ubuntu2 (wily).

** Patch added: "tls_g.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557248/+attachment/4607004/+files/tls_g.patch

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

Title:
  OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557248/+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 1557248] Re: OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code

2016-03-21 Thread Ubuntu Foundations Team Bug Bot
The attachment "tls_g.patch" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557248/+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 1560120] Re: Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Launchpad Bug Tracker
This bug was fixed in the package lxcfs - 2.0.0~rc8-0ubuntu1

---
lxcfs (2.0.0~rc8-0ubuntu1) xenial; urgency=medium

  * Merge 2.0.0.rc8, which implements access(2) needed by lxc.
(LP: #1560120)

 -- Serge Hallyn   Mon, 21 Mar 2016 21:08:18
-0700

** Changed in: lxcfs (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1560327] [NEW] package libsasl2-2:i386 2.1.25.dfsg1-17build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2016-03-21 Thread taurusgr
Public bug reported:

I tried to install a program which could install iTunes but it failed and after 
that I have this problem that the update package
could not install.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libsasl2-2:i386 2.1.25.dfsg1-17build1
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
Uname: Linux 3.19.0-56-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue Mar 22 06:20:30 2016
DuplicateSignature: package:libsasl2-2:i386:2.1.25.dfsg1-17build1:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-02-06 (45 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.11
SourcePackage: cyrus-sasl2
Title: package libsasl2-2:i386 2.1.25.dfsg1-17build1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: cyrus-sasl2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty

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

Title:
  package libsasl2-2:i386 2.1.25.dfsg1-17build1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1560327/+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 1560327] Re: package libsasl2-2:i386 2.1.25.dfsg1-17build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2016-03-21 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libsasl2-2:i386 2.1.25.dfsg1-17build1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1560327/+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 1560315] [NEW] [needs packaging] juju2 beta is not in xenial

2016-03-21 Thread Curtis Hovey
Public bug reported:

Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.

Juju 2.0 uses a new package name, juju2. This package is co-installable
with juju-core.

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


** Tags: needs-packaging

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

Title:
  [needs packaging] juju2 beta is not in xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+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 1560120] Re: Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Serge Hallyn
Christopher,  thanks for reporting this.  I've pushed the fix, but as
we're now in final freeze it may be delayed for approval.

** Changed in: lxcfs (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1560030] Re: neutron-vpn-agent does not restart due to neutron-ovs-cleanup issue

2016-03-21 Thread James Page
Hi Gema

Please can you provide log files for both of the agents from the gateway
unit.

Thanks!

** Also affects: neutron (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: neutron-gateway (Juju Charms Collection)
   Status: New => Invalid

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

Title:
  neutron-vpn-agent does not restart due to neutron-ovs-cleanup issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1560030/+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 1560030] Re: neutron-vpn-agent does not restart due to neutron-ovs-cleanup issue

2016-03-21 Thread Gema Gomez
cat vpn_agent.log
2016-03-21 11:27:39.015 41648 INFO oslo.messaging._drivers.impl_rabbit 
[req-cb34296e-1674-4ec6-83a9-ac57085cd2a8 - - - - -] Connecting to AMQP server 
on 10.230.19.137:5672
2016-03-21 11:27:39.027 41648 INFO oslo.messaging._drivers.impl_rabbit 
[req-cb34296e-1674-4ec6-83a9-ac57085cd2a8 - - - - -] Connected to AMQP server 
on 10.230.19.137:5672
2016-03-21 11:27:39.033 41648 INFO oslo.messaging._drivers.impl_rabbit 
[req-cb34296e-1674-4ec6-83a9-ac57085cd2a8 - - - - -] Connecting to AMQP server 
on 10.230.19.137:5672
2016-03-21 11:27:39.045 41648 INFO oslo.messaging._drivers.impl_rabbit 
[req-cb34296e-1674-4ec6-83a9-ac57085cd2a8 - - - - -] Connected to AMQP server 
on 10.230.19.137:5672
2016-03-21 11:27:39.267 41648 INFO oslo.messaging._drivers.impl_rabbit 
[req-9740db7e-1876-4fe4-8eaf-74ad9281e10c - - - - -] Connecting to AMQP server 
on 10.230.19.137:5672
2016-03-21 11:27:39.292 41648 WARNING oslo_log.versionutils [-] Deprecated: 
WritableLogger() is deprecated as of Liberty and may be removed in Mitaka. It 
will not be superseded.
2016-03-21 11:27:39.294 41648 INFO oslo.messaging._drivers.impl_rabbit 
[req-9740db7e-1876-4fe4-8eaf-74ad9281e10c - - - - -] Connected to AMQP server 
on 10.230.19.137:5672
2016-03-21 11:27:39.321 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:39.334 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:44.996 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.008 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.019 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.028 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.038 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.048 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.061 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.076 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.079 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.080 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.082 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.084 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.085 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672
2016-03-21 11:27:45.087 41648 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on 10.230.19.137:5672

cat ovs-cleanup.log
2016-03-21 08:56:08.186 1896 INFO neutron.common.config [-] Logging enabled!
2016-03-21 08:56:08.187 1896 INFO neutron.common.config [-] 
/usr/bin/neutron-ovs-cleanup version 7.0.1
2016-03-21 08:56:11.663 1896 INFO neutron.cmd.ovs_cleanup [-] Cleaning bridge: 
br-int
2016-03-21 08:56:37.182 1896 INFO neutron.cmd.ovs_cleanup [-] Cleaning bridge: 
br-ex
2016-03-21 08:56:42.852 1896 INFO neutron.cmd.ovs_cleanup [-] OVS cleanup 
completed successfully


** Changed in: neutron-gateway (Juju Charms Collection)
   Status: Invalid => New

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

Title:
  neutron-vpn-agent does not restart due to neutron-ovs-cleanup issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1560030/+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 1555345] Comment bridged from LTC Bugzilla

2016-03-21 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-03-21 09:43 EDT---
Hi @mathieu-tl,

Can you confirm the milestone for this is 16.04?

Thanks!

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

Title:
  ISST-LTE: pVM:multipath -ll cannot show mpath device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1555345/+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 1559699] Re: [1.9.1] Commissioning doesn't detect partitioning of secondary hard disk

2016-03-21 Thread Andres Rodriguez
Martin,

On commissioning, MAAS won't detect your partitions on the secondary
disk and for the moment, MAAS won't gain that ability to auto-detect
partitions.

On deployment, these partitions will be wiped out as a premise that MAAS
won't keep old data. This is a security mechanism/feature  to ensure
that MAAS doesn't allow data to be available on the disk to users who
re-use the machines for different purposes.

As such, I'm marking this bug as won't fix provided MAAS won't give the
ability to keep the data.

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

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

Title:
  [1.9.1] Commissioning doesn't detect partitioning of secondary hard
  disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1559699/+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 1559935] Re: [SRU] nova 12.0.2, keystone 8.1.0

2016-03-21 Thread James Page
** Description changed:

  Point release available for Liberty for nova and keystone.
+ 
+ >> nova <<
+ 
+ 12.0.2
+ --
+ 
+ * Propagate qemu-img errors to compute manager
+ * Fix evacuate support with Nova cells v1
+ * libvirt: set libvirt.sysinfo_serial='none' for virt driver tests
+ * XenAPI: Workaround for 6.5 iSCSI bug
+ * Change warn to debug logs when migration context is missing
+ * Imported Translations from Zanata
+ * libvirt: Fix/implement revert-resize for RBD-backed images
+ * Ensure Glance image 'size' attribute is 0, not 'None'
+ * Add retry logic for detaching device using LibVirt
+ * Spread allocations of fixed ips
+ * Apply scheduler limits to Exact* filters
+ * Replace eventlet-based raw socket client with requests
+ * VMware: Handle image size correctly for OVA and streamOptimized images
+ * XenAPI: Cope with more Cinder backends
+ * ports & networks gather should validate existance
+ * Disable IPv6 on bridge devices
+ * Imported Translations from Zanata
+ * Imported Translations from Zanata
+ * Validate translations
+ * Fix instance not destroyed after successful evacuation
+ * Imported Translations from Zanata
+ 
+ >> keystone <<
+ 
+ 8.1.0
+ -
+ 
+ * Make WebSSO trusted_dashboard hostname case-insensitive
+ * Imported Translations from Zanata
+ * Escape DN in enabled query
+ * Test enabled emulation with special user_tree_dn
+ * Revert "Validate domain ownership for v2 tokens"
+ * Fix schema validation to use JSONSchema for empty entity
+ * Refactors validation tests to better see the cases
+ * Fix trust redelegation and associated test
+ * use self.skipTest instead of self.skip
+ * Imported Translations from Zanata
+ * Fix users in group and groups for user exact filters
+ * Add audit IDs to revocation events
+ * Expose defect in users_in_group, groups_for_user exact filters
+ * Ensure endpoints returned is filtered correctly
+ * Fix 500 error when no fernet token is passed
+ * Updated from global requirements
+ * Updated from global requirements
+ * Updated from global requirements
+ * More useful message when using direct driver import
+ * force releasenotes warnings to be treated as errors

** Changed in: cloud-archive/liberty
 Assignee: (unassigned) => James Page (james-page)

** Changed in: keystone (Ubuntu Wily)
 Assignee: (unassigned) => James Page (james-page)

** Changed in: nova (Ubuntu Wily)
 Assignee: (unassigned) => James Page (james-page)

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

Title:
  [SRU] nova 12.0.2, keystone 8.1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1559935/+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 1546445] Please test proposed package

2016-03-21 Thread James Page
Hello Liang, or anyone else affected,

Accepted qemu into kilo-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:kilo-proposed
  sudo apt-get update

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-kilo-needed to verification-kilo-done. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-kilo-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!

** Tags added: verification-kilo-needed

** Changed in: cloud-archive
   Status: Fix Committed => Invalid

** Changed in: cloud-archive
   Status: Invalid => Fix Released

** Tags removed: verification-needed

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

Title:
  support vhost user without specifying vhostforce

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1546445/+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 1559801] Re: OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

2016-03-21 Thread Brian Knoll
I think it is important to realize that this bug causes Ubuntu 16.04 to
be unusable in many high security environments, since the stock SSH
installation does not function with GSSAPI and the installation of a
non-vendor-supported SSH will be unacceptable by policy in many of those
same environments.

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

Title:
  OpenSSH GSSAPI Authentication Broken In Ubuntu 16.04 Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+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 1559981] [NEW] dpdk stability improvements by cherry picking from 16.04-rc1

2016-03-21 Thread ChristianEhrhardt
Public bug reported:

DPDK is great, but also a very fast moving project.
Looking at quite some commits post dpdk 2.2 shows that there are various issues 
that we should not let our customers run into, but instead backport some 
non-functional but bug fixing patches from upstream dpdk into our 2.2 release.

Just as some fixes that we found in testing and provided them upstream
plus packaging them - there are many more that fall into the same
category.

Please analyze potential fixes and try to integrate in packaging.
It would be a tremendous improvement to the stability of DPDK to get at least 
some of them.

** Affects: dpdk (Ubuntu)
 Importance: High
 Assignee: ChristianEhrhardt (paelzer)
 Status: Triaged

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

** Changed in: dpdk (Ubuntu)
   Importance: Undecided => High

** Changed in: dpdk (Ubuntu)
 Assignee: (unassigned) => ChristianEhrhardt (paelzer)

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

Title:
  dpdk stability improvements by cherry picking from 16.04-rc1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559981/+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 1559912] Re: Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

2016-03-21 Thread ChristianEhrhardt
Info on progress.
No feedback from communities so far.
After various other DPDK fixes took 3/4 of my day I set up a more thorough 
debugging environment derived from my testing env, but the real debugging 
itself has to start tomorrow morning.

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

Title:
  Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559912/+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 1560120] [NEW] Unprivileged nested container will not start inside a privileged container

2016-03-21 Thread Christopher Townsend
Public bug reported:

This is a follow up to bug #1543697 where I have a Trusty host with ppa
:ubuntu-lxc/stable installed and have a privileged Xenial LXC and a
nested unprivileged LXC.

After some recent update(s), the unprivileged nested LXC will not start
again.  I've attached a debug log.

LXC version on host: 2.0.0~rc11-0ubuntu1~ubuntu14.04.1~ppa1
LXC version in privileged Xenial LXC: 2.0.0~rc11-0ubuntu1

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

** Attachment added: "test2_start.out"
   
https://bugs.launchpad.net/bugs/1560120/+attachment/4606580/+files/test2_start.out

** Description changed:

- This is a follow up to bug#1543697 where I have a Trusty host with ppa
+ This is a follow up to bug #1543697 where I have a Trusty host with ppa
  :ubuntu-lxc/stable installed and have a privileged Xenial LXC and a
  nested unprivileged LXC.
  
  After some recent update(s), the unprivileged nested LXC will not start
  again.  I've attached a debug log.

** Description changed:

  This is a follow up to bug #1543697 where I have a Trusty host with ppa
  :ubuntu-lxc/stable installed and have a privileged Xenial LXC and a
  nested unprivileged LXC.
  
  After some recent update(s), the unprivileged nested LXC will not start
  again.  I've attached a debug log.
+ 
+ LXC version on host: 2.0.0~rc11-0ubuntu1~ubuntu14.04.1~ppa1
+ LXC version in privileged Xenial LXC: 2.0.0~rc11-0ubuntu1

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

Title:
  Unprivileged nested container will not start inside a privileged
  container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1560120/+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 1560117] [NEW] gevent 1.1 (non beta) released, please merge from Debian testing

2016-03-21 Thread Teg
Public bug reported:

The current version of gevent for Xenial is a beta version, so please
update from https://packages.debian.org/stretch/python-gevent to bring
python-gevent to the final and stable 1.1 version.

Also update the python3-gevent package from
https://packages.debian.org/stretch/python3-gevent

** Affects: python-gevent (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gevent python

** Description changed:

- The current version of gevent is a beta version, so please update from
- https://packages.debian.org/stretch/python-gevent to bring python-gevent
- to the final and stable 1.1 version.
+ The current version of gevent for Xenial is a beta version, so please
+ update from https://packages.debian.org/stretch/python-gevent to bring
+ python-gevent to the final and stable 1.1 version.

** Description changed:

  The current version of gevent for Xenial is a beta version, so please
  update from https://packages.debian.org/stretch/python-gevent to bring
  python-gevent to the final and stable 1.1 version.
+ 
+ Also update the python3-gevent package from
+ https://packages.debian.org/stretch/python3-gevent

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

Title:
  gevent 1.1 (non beta) released, please merge from Debian testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-gevent/+bug/1560117/+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 1559408] Re: Many PMD driver options are disabled, including "BNX2X"!

2016-03-21 Thread ChristianEhrhardt
Martin since I'm happy you work with that code base I'd recommend you create a 
test setup based on virtio.
You will still be blocked on bug 1559912 for now, but I'm working on that this 
week and stil hope to get some upstream support.

I'll reject this bug for the given reasons now, but please catch me on
IRC for a more interactive discussion if you like.

** Changed in: dpdk (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Many PMD driver options are disabled, including "BNX2X"!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559408/+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 1559408] Re: Many PMD driver options are disabled, including "BNX2X"!

2016-03-21 Thread ChristianEhrhardt
I checked the other default disabled drivers.
To all some kind of incompleteness, non-support or being only stubs applies.

It could be said, that the same is true for the virtual ones we enable like 
PCAP and XEN.
But there is a major difference in:
- nobody is "buying" the HW for pcap or XEN to then realize it is not supported
- those virtual environments are good for experiments and proof of concepts but 
not suitable for most production cases anyway

So (keep) enabling those virtual ones is kind of ok, while I'd consider
enabling the PMDs for more of the HW cards is not.

To get those enabled in my opinion one has to work with the upstream
project to get it properly supported and default enabled.

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

Title:
  Many PMD driver options are disabled, including "BNX2X"!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559408/+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 1559981] Re: dpdk stability improvements by cherry picking from 16.04-rc1

2016-03-21 Thread ChristianEhrhardt
I had a focus on identifying:
- only patches to components that are enabled in our packaging
- issues that have a real chance to occur on the usage we expect for 16.04 
timeframe
- patches that are small, so review is not overly complex
- apply without manual adaption (offset ok to some extend, no fuzz, no manual 
fix)

commit d3a274ce9dee28118b8647e0db72ef0f4b6a6323
app/testpmd: handle SIGINT and SIGTERM
commit 308df2bfba3d238fc1d2d16cc10c84681803b408 
   
Handle SIGINT and SIGTERM in l3fwd.
commit da82ee17e6ea99bf2931383ac33b0caccaaaefce
tools: fix unbinding failure handling
commit 16c1814c802c205f6d3c32e3d3d10de9f87e7f22
tools: support Python 3 in bind script
commit bb9f408550d13af6c1da104b0d9d9b9837f69bde
tools: support binding to built-in kernel modules

commit 6e7caa1ad9d597fed0a49468af25ae6e68b8c443
eal/linux: support built-in kernel modules

commit 86f36ff9578b5f3d697c8fcf6072dcb70e2b246f
mempool: fix leak when creation fails

commit ca67ed289a76f38d6c4a4021985a36eaf1d77e28
vhost: fix leak of fds and mmaps
commit fa11a8a7251e14eca0a4190128732386f13551bd
   port: fix crash for ring writer nodrop
commit 04f366906ab395c8047bebfc1ddea244dfcb40f5
   port: fix crash for ethdev writer nodrop

commit c7a4ff80722e9237a4c504106d21ba5ca27d8df2 
   i40e: fix overflow
commit 097e920c32bf19cf918cc071525f33b0abdeebaf
   i40e: fix inverted check for no refcount
commit 330aa319382aec9ea595f9ebcb9a3c44647ad66c
i40e: fix VLAN filtering
commit 9f44dd3d8ad447c7f797a9564d30a15e5ab7f72b
i40e/base: fix missing check for stopped admin queue
commit 8a8807369ffafef90c410279b4b2645d2d7a7483
i40e/base: fix driver load failure

commit 7656a546c0609f3205558a5d48352c82607d38d3
fm10k: fix VLAN flag in scattered Rx

commit c6fb0e55585206a89f6db396de860e6e844cad06
pcap: fix captured frame length

commit 6e02723754fb2b341701ac438486b2dfea98b523
bonding: fix detach of bonded device
commit df3e8ad73f4c92b4eb8f49ff33271d4a09e6a04a
bonding: fix detach of slave devices
commit 786c990a11e6e6592dfdee02840877070aa3a79a
bonding: copy entire config structure in mode 4
commit 6698820b5f6d955b6af2b916e1074db236d4f5a2
bonding: do not ignore multicast in mode 4
commit 8997a10bfcad789d000debaac4cd85cd3db57997
bonding: fix active slaves with no primary
commit 7a7122edf1c8d63e516d1b2c2eff6fa9b54e0f82
bonding: do not activate slave twice
commit 2186fff3675d4e774cecc8f918c05063e0367d28
bonding: fix crash when no slave device


The following patches were considered but too complex / non applying without 
adaption
For those we need a way "harder" reasoning to cherry pick them:
commit 1939d724f2d0bd2f81d7fbc9d0b17f0cf1815154
i40e/base: fix uncertain event descriptor issue
commit 360c4545e01e97676681dece153d884cd72f681a
fm10k/base: fix max queues on VF initialization failure

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

Title:
  dpdk stability improvements by cherry picking from 16.04-rc1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559981/+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 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist

2016-03-21 Thread Mathieu Trudel-Lapierre
Just uploaded it to the trusty queue again, I'll get someone to review
it and accept the upload.

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

Title:
  kpartx causes kernel oops when NVMe devices is not in blacklist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+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 1559571] Re: package nginx-extras (not installed) failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2016-03-21 Thread Thomas Ward
Due to some issue in apt and apport hooks, can you provide the output of
the following command please?

systemctl -l status nginx.service


** Changed in: nginx (Ubuntu)
   Status: New => Incomplete

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

Title:
  package nginx-extras (not installed) failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1559571/+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 1560030] Re: neutron-vpn-agent does not restart due to neutron-ovs-cleanup issue

2016-03-21 Thread Gema Gomez
Forgot to mention that we are running Liberty, the version of the charm
in use is cs:trusty/neutron-gateway-9

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

Title:
  neutron-vpn-agent does not restart due to neutron-ovs-cleanup issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1560030/+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 1555345] Re: ISST-LTE: pVM:multipath -ll cannot show mpath device

2016-03-21 Thread Mathieu Trudel-Lapierre
The milestone for this is indeed still 16.04; but we might use a
different way to get the fix than applying the patch. We have Ryan here
working on merging multipath-tools (a git snapshot that should contain
the fix and many others) from Debian; once that is completed and lands
in the release we'll revisit this bug, make sure whether it is fixed or
if it still needs to have the patch applied on top.

Or, if we end up in the case that we can't land the larger update, we'll
land just this patch. In any case, this means we'll delay fixing this
here bug for now until the situation with the merge is completed -- that
is tracked in bug 1551952.

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

Title:
  ISST-LTE: pVM:multipath -ll cannot show mpath device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1555345/+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 1551952] Re: FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable

2016-03-21 Thread Mauricio Faria de Oliveira
About more testing..

If that helps, at least one test team here at IBM will perform multipath 
testing on 16.04 from Final Beta Freeze (March 24, currently) throughout 
release/GA on April 21.
They drove lots of the multipath bugs that I've worked on and bugged 
@mathieu-tl with since 15.04 :) so, they find stuff.

This, of course, is not to say more testing shouldn't be done (and I
have no reason to think that would happen; but have to mention) - the
more coverage, the better, specially w/ multipath, which relates to
multiple areas in its workings.

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

Title:
  FFE: Please merge multipath-tools 0.5.0+git1.656f8865  from Debian
  unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+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 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

2016-03-21 Thread John Sopko
Doing this forces rpcbind to start on boot and then nis starts
correctly:

# /bin/systemctl add-wants multi-user.target rpcbind.service
Created symlink from 
/etc/systemd/system/multi-user.target.wants/rpcbind.service to 
/lib/systemd/system/rpcbind.service

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

Title:
  ypbind not able to socket activate rpcbind under systemd, fails at
  boot unless something else starts rpcbind

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+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 1555700] Re: [FFE] Please merge tgt 1.0.63 from Debian (unstable)

2016-03-21 Thread Ryan Harper
Discussion from #ubuntu-release

 rharper: As for the AIO thing, as you understand the code, what are 
the odds this could have a negative impact on users of other backends if the 
AIO stuff is broken?
 rharper: If you're 99% confident that the change is meaningless for 
people who don't use the feature, then I'm fine with adding it.
 infinity: ok;  re aio;  let me look a bit to be certain, libaio is 
standard stuff;  the question is has tgt had aio for quite some time and just 
not enabled it (and why);  debian recently added it 
 rharper: Right, it's obviously been there longer upstream than in 
Debian, the question is how long and, more importantly, is it isolated enough 
to not blow up the world for non-AIO users if it sucks.
 rharper: The latter question being the interesting one.  I don't 
care if the feature it experimental and added last week if it has zero impact 
on people who don't use it.
 s/feature it/feature is/
 understood
 rharper: Feel free to copy and paste any of the above to the bug, 
FWIW, and if your conclusion is "yeah, it looks safe enough", no need to 
round-trip to me again, FFe approved if your best judgement says it's safe.
 infinity: will do; I need to confirm aio is only enabled via user 
choice (ie not default); if so then I'd say it's out of the way for anyone 
except those whom request it;  
 rharper: And if you're less sure, a commitment of "we'll actively 
watch for explosions and either fix the issues or revert the aio addition", 
then also approved. :P
 rharper: With a caveat that "revert the aio addition" can only be a 
solution pre-release.  Once xenial is out the door, you're stuck supporting 
whatever features we released with.
 rharper: If you're okay with the above, go nuts.

-- 
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:
  [FFE] Please merge tgt 1.0.63 from Debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+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 1560148] Re: [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Nish Aravamudan
** Patch added: "openipmi_2.0.21-1.2.0.21-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+attachment/4606633/+files/openipmi_2.0.21-1.2.0.21-1ubuntu1.debdiff

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+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 1560148] Re: [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Nish Aravamudan
For reference, git tree used to merge is at:
https://git.launchpad.net/~nacc/ubuntu/+source/openipmi

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+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 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

2016-03-21 Thread Robie Basak
Thanks, this looks good.

AFAICS, the quilt patches in Ubuntu mongodb 1:2.6.10-0ubuntu1 apply with
only offset, not fuzz. This is allowed, so refreshing wasn't necessary.
I can see that your refresh (and one line of series being moved) is
effectively a no-op but it would be easier for me if we didn't refresh
things unnecessarily to reduce review diff. Similarly the change to
COMMON_OPTIONS in debian/rules just adds diff and is a no-op, so I'd
prefer not to have it.

I'm not sure what approach to take against mongodb 3.2 here though, as
there's nothing really to diff against except 2.6.

I've also been grappling a little with coming up with a good review
strategy for these packages in general. I ended up using meld to examine
a 3-way diff between your tree, Ubuntu mongodb 1:2.6.10-0ubuntu1 and
Ubuntu juju-mongodb 2.4.10-0ubuntu6. I'm much happier now that I can see
better what you changed, though I will have to do something different
for 3.2. With this though, I found a couple of other things that I
missed before. Sorry to go back to you again on this.

Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you
haven't carried this forward. Is this expected (not described in
changelog)? Perhaps it is because of --disable-scripting but I'm not
sure.

You also introduced a nocheck wrapper around override_dh_auto_build
which isn't in any of the base versions. This looks unintentional to me,
or was it intended?

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

Title:
  [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+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 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

2016-03-21 Thread Robie Basak
No need to give me any changes. Just let me know what you think we
should do on these two points, and I'll upload.

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

Title:
  [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+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 1552983] Re: Please merge logwatch 7.4.2-1 from Debian

2016-03-21 Thread Nish Aravamudan
No FFe should be necessary, as the upstream changes are all bugfixes for
the version of logwatch we now have in Ubuntu. We did the earlier merge
this cycle with the intention of doing this merge once upstream released
a full 7.4.2.

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

Title:
  Please merge logwatch 7.4.2-1 from Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1552983/+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 1552983] Re: Please merge logwatch 7.4.2-1 from Debian

2016-03-21 Thread Nish Aravamudan
** Summary changed:

- Please merge logwatch 7.4.2 from Debian
+ Please merge logwatch 7.4.2-1 from Debian

** Patch added: "logwatch_7.4.2-1.7.4.2-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1552983/+attachment/4606634/+files/logwatch_7.4.2-1.7.4.2-1ubuntu1.debdiff

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

Title:
  Please merge logwatch 7.4.2-1 from Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1552983/+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 1560148] [NEW] Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Nish Aravamudan
Public bug reported:

openipmi (2.0.21-1ubuntu1) xenial; urgency=medium

  * Merge with Debian unstable (LP: #1560148). Remaining changes:
- debian/openipmi.init: Change lockfile path. '/var/lock/subsys' does
  not exist in Debian. (LP #722770)
  [ typo in changelog entry previously ]
- Fix up packaging to install and use /etc/default/openipmi. (LP
  #473332) Thanks to Serge Hallyn.
- Patch libtool macro support in for ppc64el shared libraries.
- Detect that a module is built into the kernel.
  + LP #1309860
- debian/openipmi.init: Do not unload all modules if some configured
  HW modules are not successfully loaded (LP #1318317).
  * Drop:
- Do not explicitly depend on pthread.
  [ previously undocumented]
- Only use SIGPWR if defined.
  [ merged in Debian ]
- Delete copyright.
  [ previously undocumented ]
- Add usr/sbin to debian/dirs
  [ previously undocumented ]
- d/watch: update for new location
  [ previously undocumented ]
- Revert local changes to config.guess/config.sub; instead, use
  autotools-dev's debhelper integration to update these files for each
  build.
  [ fixed in Debian ]
- swig/python/openipmigui/Makefile generated file
  [ previously undocumented ]
- Enabling openssl support as it is causing
  problems running third party applications. (closes: #775847)
  (LP #1546735)
  [ merged in Debian ]
  * Use dh_autoreconf{,_clean} to update the build tooling to the
current levels on Ubuntu.

 -- Nishanth Aravamudan   Fri, 18 Mar
2016 15:50:09 -0700

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

** Description changed:

  openipmi (2.0.21-1ubuntu1) xenial; urgency=medium
  
-   * Merge with Debian unstable (LP: #). Remaining changes:
- - debian/openipmi.init: Change lockfile path. '/var/lock/subsys' does
-   not exist in Debian. (LP #722770)
-   [ typo in changelog entry previously ]
- - Fix up packaging to install and use /etc/default/openipmi. (LP
-   #473332) Thanks to Serge Hallyn.
- - Patch libtool macro support in for ppc64el shared libraries.
- - Detect that a module is built into the kernel.
-   + LP #1309860
- - debian/openipmi.init: Do not unload all modules if some configured
-   HW modules are not successfully loaded (LP #1318317).
-   * Drop:
- - Do not explicitly depend on pthread.
-   [ previously undocumented]
- - Only use SIGPWR if defined.
-   [ merged in Debian ]
- - Delete copyright.
-   [ previously undocumented ]
- - Add usr/sbin to debian/dirs
-   [ previously undocumented ]
- - d/watch: update for new location
-   [ previously undocumented ]
- - Revert local changes to config.guess/config.sub; instead, use
-   autotools-dev's debhelper integration to update these files for each
-   build.
-   [ fixed in Debian ]
- - swig/python/openipmigui/Makefile generated file
-   [ previously undocumented ]
- - Enabling openssl support as it is causing
-   problems running third party applications. (closes: #775847)
-   (LP #1546735)
-   [ merged in Debian ]
-   * Use dh_autoreconf{,_clean} to update the build tooling to the
- current levels on Ubuntu.
+   * Merge with Debian unstable (LP: #1560148). Remaining changes:
+ - debian/openipmi.init: Change lockfile path. '/var/lock/subsys' does
+   not exist in Debian. (LP #722770)
+   [ typo in changelog entry previously ]
+ - Fix up packaging to install and use /etc/default/openipmi. (LP
+   #473332) Thanks to Serge Hallyn.
+ - Patch libtool macro support in for ppc64el shared libraries.
+ - Detect that a module is built into the kernel.
+   + LP #1309860
+ - debian/openipmi.init: Do not unload all modules if some configured
+   HW modules are not successfully loaded (LP #1318317).
+   * Drop:
+ - Do not explicitly depend on pthread.
+   [ previously undocumented]
+ - Only use SIGPWR if defined.
+   [ merged in Debian ]
+ - Delete copyright.
+   [ previously undocumented ]
+ - Add usr/sbin to debian/dirs
+   [ previously undocumented ]
+ - d/watch: update for new location
+   [ previously undocumented ]
+ - Revert local changes to config.guess/config.sub; instead, use
+   autotools-dev's debhelper integration to update these files for each
+   build.
+   [ fixed in Debian ]
+ - swig/python/openipmigui/Makefile generated file
+   [ previously undocumented ]
+ - Enabling openssl support as it is causing
+   problems running third party applications. (closes: #775847)
+   (LP #1546735)
+   [ merged in Debian ]
+   * Use dh_autoreconf{,_clean} to update the build tooling to the
+ current levels on Ubuntu.
  
-  -- Nishanth Aravamudan   Fri, 18 Mar
+  -- Nishanth Aravamudan 

[Bug 1560148] Re: Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Nish Aravamudan
** Attachment added: "openipmi_2.0.21-1ubuntu1_amd64-20160321-0921.build"
   
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+attachment/4606629/+files/openipmi_2.0.21-1ubuntu1_amd64-20160321-0921.build

** Summary changed:

- Please merge with openipmi 2.0.21-1 from Debian unstable
+ [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+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 1560148] Re: Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Nish Aravamudan
** Patch added: "ChangeLog.diff"
   
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+attachment/4606628/+files/ChangeLog.diff

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+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 1349857] Re: maas-common fails to set up symbolic link to etc/rsyslog/99-maas.conf

2016-03-21 Thread nathan
** Changed in: maas (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  maas-common fails to set up symbolic link to etc/rsyslog/99-maas.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1349857/+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 1560149] [NEW] missing seccomp whitelist for qemu-kvm

2016-03-21 Thread Simon Déziel
Public bug reported:

Steps to reproduce:

1) set "seccomp_sandbox = 1" in /etc/libvirt/qemu.conf
2) restart libvirt-bin
3) create a guest using the attached .xml file
4) start the guest

Current behavior: the guest will remain in the "paused" state and fail
to start because of this:

audit: type=1326 audit(1458582324.294:87): auid=4294967295 uid=114
gid=123 ses=4294967295 pid=17695 comm="qemu-system-x86" exe="/usr/bin
/qemu-system-x86_64" sig=31 arch=c03e syscall=99 compat=0
ip=0x7fc47c3557d7 code=0x0

Expected behavior: the guest would start normally

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 21 13:40:41 2016
KernLog:

SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/libvirt/qemu.conf']
modified.conffile..etc.libvirt.qemu.networks.default.xml: [deleted]

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


** Tags: amd64 apport-bug xenial

** Attachment added: "guest definition"
   
https://bugs.launchpad.net/bugs/1560149/+attachment/4606623/+files/ubuntu16.04.xml

** Description changed:

  Steps to reproduce:
  
  1) set "seccomp_sandbox = 1" in /etc/libvirt/qemu.conf
  2) restart libvirt-bin
- 3) create a guest using the spice display type
+ 3) create a guest using the attached .xml file
+ 4) start the guest
  
  Current behavior: the guest will remain in the "paused" state and fail
  to start because of this:
  
  audit: type=1326 audit(1458582324.294:87): auid=4294967295 uid=114
  gid=123 ses=4294967295 pid=17695 comm="qemu-system-x86" exe="/usr/bin
  /qemu-system-x86_64" sig=31 arch=c03e syscall=99 compat=0
  ip=0x7fc47c3557d7 code=0x0
  
  Expected behavior: the guest would start normally
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libvirt-bin 1.3.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 13:40:41 2016
  KernLog:
-  
+ 
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] 
Permission denied: '/etc/libvirt/qemu.conf']
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [deleted]

** Attachment removed: "guest definition"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1560149/+attachment/4606623/+files/ubuntu16.04.xml

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

Title:
  missing seccomp whitelist for qemu-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1560149/+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 1560148] Re: Please merge with openipmi 2.0.21-1 from Debian unstable

2016-03-21 Thread Nish Aravamudan
FFe justification: The version of OpenIPMI in Ubuntu was released in
2010. Since that time, a number of bugfixes and features have been
added, which improve the code quality and broaden the functionality
available.

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

Title:
  [FFe] Please merge with openipmi 2.0.21-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1560148/+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 1559307] Re: [SRU] update walinuxagent to 2.1.3 in Wily

2016-03-21 Thread Robert C Jennings
** Changed in: walinuxagent (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [SRU] update walinuxagent to 2.1.3 in Wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1559307/+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 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

2016-03-21 Thread Martin Packman
> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't
> carried this forward. Is this expected (not described in changelog)? Perhaps 
> it
> is because of --disable-scripting but I'm not sure.

Indeed. We have always built juju-mongodb without the javascript engine
because the security team had concerns and we didn't need it anyway.
Note in 3.2 V8 has gone, and they're back to spidermonkey:



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

Title:
  [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+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 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

2016-03-21 Thread Michael
I'd like to confirm that on Ubuntu 16.04 the following allowed rpcbind to start 
on fresh bootup:
/bin/systemctl add-wants multi-user.target rpcbind.service

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

Title:
  ypbind not able to socket activate rpcbind under systemd, fails at
  boot unless something else starts rpcbind

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+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 1528586] Re: upgrade to php PHP 7.0.1

2016-03-21 Thread Nish Aravamudan
PHP 7.0 is at 7.0.4-5, please clarify what is being requested.

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

Title:
  upgrade to php PHP 7.0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1528586/+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