date:20160229

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  bind9 9.10.3.dfsg.P2-4 crash on exit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1549788/+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 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

2016-02-29 Thread Ben Howard

** Package changed: linux (Ubuntu) => cloud-init (Ubuntu)

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

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+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 1551419] [NEW] Fix UUID endianness patch breaks cloud-init on Azure

You have been subscribed to a public bug:

On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
unique ID for a cloud instance.  If this ID ever changes, then cloud-
init will attempt to reprovision the VM.

This recent kernel patch in the Ubuntu kernel corrects the endianness
for some SMBIOS fields, but also has the effect causing cloud-init to
think that the system-uuid has changed:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

The impact is that cloud-init attempts to reprovision the VM, often
causing the customer to lose access to their VM.

** Affects: cloud-init (Ubuntu)
 Importance: Critical
 Status: Confirmed

-- 
Fix UUID endianness patch breaks cloud-init on Azure
https://bugs.launchpad.net/bugs/1551419
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to cloud-init in Ubuntu.

-- 
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 1551421] [NEW] dpkg installation routine of dlm depends on corosync to be installed and started

2016-02-29 Thread Karl-Philipp Richter

Public bug reported:

`sudo apt-get install dlm` fails with

dlm (4.0.1-0ubuntu2) wird eingerichtet ...
insserv: warning: script 'K01irda-setup' missing LSB tags and overrides
insserv: Service corosync has to be enabled to start service dlm_controld
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: Fehler beim Bearbeiten des Paketes dlm (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 
zurück

and only succeeds if `corosync` is installed and the service enabled
with `sudo systemd enable corosync`.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: dlm 4.0.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
Uname: Linux 4.2.0-32-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 29 22:02:45 2016
InstallationDate: Installed on 2013-10-17 (865 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: dlm
UpgradeStatus: Upgraded to wily on 2015-11-19 (102 days ago)

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


** Tags: amd64 apport-bug wily

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

Title:
  dpkg installation routine of dlm depends on corosync to be installed
  and started

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1551421/+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 1500981] Re: juju-db segfault while syncing with replicas

2016-02-29 Thread Cheryl Jennings

** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4

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

Title:
  juju-db segfault while syncing with replicas

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1500981/+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 1349949] Re: Juju's mongodb does not need to log every command in syslog

2016-02-29 Thread Cheryl Jennings

** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4

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

Title:
  Juju's mongodb does not need to log every command in syslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1551150] Re: devel-proposed - android lxc container fails to start

So far that does seem to confirm the hypothesis that since the phone has
systemd installed (but unused), this meets lxc's dependency on systemd |
cgroup-lite but as upstart is used to boot and upstart itself doesn't
mount the cgroup controllers, this results in a system without cgroups
mounted.

Having whatever package sets up the android container depend directly on
cgroup-lite would fix that dependency issue, though from the logs
provided so far, it looks like cgroup-lite is either not starting or is
failing.


I'm keeping the LXC task open for now, but there's so far been no indication of 
an actual bug in LXC or in its packaging, instead the phone seed is doing 
something that's not seen anywhere else (depend on systemd but not use it) 
which we can't do anything about from a packaging point of view. The rest of 
the issue appears to be some bad interaction between cgroup-lite and the init 
configuration on the Ubuntu phone.

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

Some more information on cgroup-lite and where it may fail.

 - cgroup lite is triggered on "mounted MOUNTPOINT=/sys/fs/cgroup" => the path 
is shown as mountend above, so not it
 - The job then gets skipped if /bin/cgroups-mount doesn't exist => part of the 
cgroup-lite package, so not it
 - The job then gets skipped if /sys/fs/cgroup doesn't exist => was shown as 
mounted above, so not it
 - cgroup-lite exits if a cgroup entry is found in /etc/fstab
 - cgroup-lite exits if /proc/cgroups doesn't exist => all Ubuntu kernels have 
it, so not it

So the most likely reason I believe would be a "cgroup" entry of some
sort in /etc/fstab, the second most likely reason would be a failure for
the "mounted MOUNTPOINT=/sys/fs/cgroup" to be emitted by upstart
somehow.

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

That mountinfo shows no mounted cgroup controller, hinting that cgroup-
lite didn't start or otherwise failed to start.

Could you look for a /var/log/upstart/cgroup-lite.log file?

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

2016-02-29 Thread Serge Hallyn

Hi,

sorry, mountinfo does not show the hierarchies.  Can you show
/proc/cgroups  and /proc/self/cgroup output?

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

android container log with cgroup-lite installed and content of
mountinfo from the same boot.

** Attachment added: "mountinfo.out"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584668/+files/mountinfo.out

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

And syslog

** Attachment added: "syslog"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584669/+files/syslog

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

The phone uses upstart. I'll try to get the content of mountinfo

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551305] Re: backup service crashes in ceph job with "pure virtual method called"

Upstream original bug reference:

http://tracker.ceph.com/issues/13636

firefly backport was rejected:

http://tracker.ceph.com/issues/13757

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

Title:
  backup service crashes in ceph job with "pure virtual method called"

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1551305/+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 1551305] Re: backup service crashes in ceph job with "pure virtual method called"

2016-02-29 Thread Michal Dulko

I was afraid that whole scalable backups stuff we've merged recently may
be causing this, but it seems very unlikely.

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

Title:
  backup service crashes in ceph job with "pure virtual method called"

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1551305/+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 1551150] Re: devel-proposed - android lxc container fails to start

Do you know if the phone actually uses systemd as its init system
nowadays?

LXC requires either systemd or cgroup-lite to mount all the cgroup bits
properly, if systemd is installed but not used, that could explain what
you are seeing. Installing cgroup-lite should have fixed it though,
unless the container is started before cgroup-lite is done. That's not
possible with the regular lxc init script, but if the phone has
something custom, it could be possible.

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

We're gonna need a /proc/self/mountinfo output if we want to figure out
what the controller #7 is on your system...

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551305] Re: backup service crashes in ceph job with "pure virtual method called"

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

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

Title:
  backup service crashes in ceph job with "pure virtual method called"

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1551305/+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 1318317] Re: openipmi startup script removes kernel modules

2016-02-29 Thread Nish Aravamudan

@Breno, yes, I think that's correct.

@Jeremy, were you able to test in both 16.04 and 14.04?

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

Title:
  openipmi startup script removes kernel modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1318317/+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 1551150] Re: devel-proposed - android lxc container fails to start

With cgroup-lite install the error message is different:
  lxc-start 20160229153538.890 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 - 
cgroupfs failed to detect cgroup metadata
  lxc-start 20160229153538.890 ERRORlxc_start - start.c:lxc_spawn:1026 
- failed initializing cgroup support
  lxc-start 20160229153538.891 ERRORlxc_start - 
start.c:__lxc_start:1276 - failed to spawn 'android'
  lxc-start 20160229153538.891 ERRORlxc_start_ui - lxc_start.c:main:344 
- The container failed to start.
  lxc-start 20160229153538.891 ERRORlxc_start_ui - lxc_start.c:main:348 
- Additional information can be obtained by setting the --logfile and 
--logpriority options.
  lxc-start 20160229160049.670 ERRORlxc_cgfs - 
cgfs.c:lxc_cgroupfs_create:874 - Could not find writable mount point for cgroup 
hierarchy 7 while trying to create cgroup.
  lxc-start 20160229160049.671 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 
- Device or resource busy - cgroup_rmdir: failed to delete 
/sys/fs/cgroup/freezer/
  lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 
- Device or resource busy - cgroup_rmdir: failed to delete 
/sys/fs/cgroup/cpuacct/
  lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 
- Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu/
  lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 
- Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/debug/
  lxc-start 20160229160049.672 ERRORlxc_start - start.c:lxc_spawn:1033 
- failed creating cgroups
  lxc-start 20160229160049.673 ERRORlxc_start - 
start.c:__lxc_start:1276 - failed to spawn 'android'
  lxc-start 20160229160049.673 ERRORlxc_start_ui - lxc_start.c:main:344 
- The container failed to start.
  lxc-start 20160229160049.673 ERRORlxc_start_ui - lxc_start.c:main:348 
- Additional information can be obtained by setting the --logfile and 
--logpriority options.

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

I installed cgroup-lite 1.10 but it still doesn't boot.

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551299] Re: Unable to run LXC commands on xenial guest in trusty host with --share-net 1

2016-02-29 Thread Tom Haddon

** Attachment added: "apport.lxc.qo3lud5p.apport"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551299/+attachment/4584512/+files/apport.lxc.qo3lud5p.apport

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

Title:
  Unable to run LXC commands on xenial guest in trusty host with
  --share-net 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551299/+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 1551304] [NEW] Unable to run LXC commands on xenial guest in trusty host with --share-net 1

2016-02-29 Thread Tom Haddon

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

Public bug reported:

This is a duplicate of 1551299

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.8-0ubuntu0.3
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux 3.13.0-79-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Mon Feb 29 15:51:10 2016
Ec2AMI: ami-0142
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: prodstack-zone-1
Ec2InstanceType: cpu1-ram2-disk50
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
KernLog:
 
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: amd64 apport-bug ec2-images trusty

** This bug has been marked a duplicate of bug 1551299
   Unable to run LXC commands on xenial guest in trusty host with --share-net 1

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

Title:
  Unable to run LXC commands on xenial guest in trusty host with
  --share-net 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551304/+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 1551299] [NEW] Unable to run LXC commands on xenial guest in trusty host with --share-net 1

2016-02-29 Thread Tom Haddon

Public bug reported:

I've created a xenial LXC on a trusty host as follows:

http://paste.ubuntu.com/15244552/

I'm able to run commands inside the LXC without "--share-net 1" but any
time I try with "--share-net 1" it fails, such as:

http://paste.ubuntu.com/15243604/ (strace output).

Will attach apport report.

** Affects: lxc (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/1551299

Title:
  Unable to run LXC commands on xenial guest in trusty host with
  --share-net 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551299/+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 1551150] Re: devel-proposed - android lxc container fails to start

cgroup-lite is not installed:
un  cgroup-lite   
ii  systemd:armhf 229-1ubuntu4

I cannot paste the content of /proc/mounts because I only have adb in
recovery (the devices fails before adb starts otherwise)

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start

Can you paste the content of /proc/mounts on such a system and confirm that 
either one of those is true:
 - systemd is installed and used as init system
 - cgroup-lite is installed

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1319320] Re: samba does not provide netlogon infos

2016-02-29 Thread Ben Vassie

Can 4.1.7 be backported to 14.04?

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

Title:
  samba does not provide netlogon infos

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1319320/+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 1551175] Re: "net join" to Active Directory may fail

2016-02-29 Thread Tim Gardner

** Package changed: linux (Ubuntu) => samba (Ubuntu)

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

Title:
  "net join" to Active Directory may fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1551175/+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 1551175] [NEW] "net join" to Active Directory may fail

You have been subscribed to a public bug:

in some AD environment the user used to join a machine may only have
right to create or delete objects but not modify. The net join code
though recently wants to set the supported encryption typed after
joining the account, which may fail then. The better approach is to
create the machine account with all the intended attributes with one
shot.

The required patch for this has been added to the Samba master and
stable 4.4 and 4.3 branches today, see

https://bugzilla.samba.org/show_bug.cgi?id=11755

https://attachments.samba.org/attachment.cgi?id=11872

As this affects many AD enterprise environments with Ubuntu clients, it
would be good if this patch would be added to the Ubuntu Samba package
before 16.04 becomes final.

** Affects: samba (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
"net join" to Active Directory may fail
https://bugs.launchpad.net/bugs/1551175
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to samba in Ubuntu.

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

Re: Fwd: Re: [Bug 1514794] Re: package:strongswan-plugin-farp may need apparmor config change

2016-02-29 Thread Simon Déziel

Hi Steven,

Thanks for the thorough analysis.

On 2016-02-29 05:58 AM, Steven Bishop wrote:
> Hi there,
> 
> 
> Sending again as message didn't show up in the thread.
> 
> 
>  Forwarded Message 
> 
> Subject: Re: [Bug 1514794] Re: package:strongswan-plugin-farp may need 
> apparmor config change
> Date: Thu, 28 Jan 2016 20:26:48 +
> From: Steven Bishop 
> To: Bug 1514794 <1514...@bugs.launchpad.net>
> 
> 
> Hi Simon,
> 
> 
> Thanks for your email.
> 
> Had a quick look back at the details.
> 
> I've attached the complete copy of "/etc/apparmor.d/usr.lib.ipsec.charon"
> that I've got installed and running (post-the-patch).
> 
> The excerpt I took from "/var/log/syslog" at the time of the bug-report
> showed that apparmor was blocking the dgram packets that the strongswan farp 
> plugin
> was trying to generate when I had a Road-Warrior client connected to the VPN
> and pinging a LAN-side client.
> 
> 
> Until I put in the patch to "/etc/apparmor.d/usr.lib.ipsec.charon" of :
> 
> network packet dgram,
> 
> the ping wasn't getting any reply as apparmor was preventing the farp plugin
> from generating the correct traffic for the ping to travel back from the 
> LAN-side client
> andacross the VPN boundary.
> 
> 
> Doing a quick :
> 
> $ dpkg -S /etc/apparmor.d/usr.lib.ipsec.charon
> 
> returns :
> 
> strongswan-ike: /etc/apparmor.d/usr.lib.ipsec.charon
> 
> 
> Looking in /var/log/auth.log, I can see that I installed :
> 
>  $ sudo apt-get install strongswan-ikev2
> 
> On Oct-17-2015 @ 17:30pm (BST = GMT + 1hr)
> 
> 
> Looking at the current Trusty repo, the date on their copy is from 15-Nov-2015
> so that working copy is actually newer than my bug-report.
> 
> I've pulled down a copy that particular .deb and looked at
> it's copy of /etc/apparmor.d/usr.lib.ipsec.charon.
> 
> Looking at the version I've got installed I can see some noteable style 
> differences
> in the layout of the file.
> The ordering of the '#include' statements are grouped all together.
> 
> I'm guessing that the package that I "apt-get install"ed on 17-Oct-2015
> has been updated on the Trusty repo since that time.
> 
> By the way, the version currently available in the current Trusty repo
> has the 2 lines:
> 
> line-24:
>  network,
> line-25:
>  network raw,
> 
> 
> If I'm reading this correctly, wouldn't line-24 mean that all network traffic 
> is allowed.
> and makes line-25 unnecessary.

That is also my understanding of those 2 rules. Even if the more
specific one is IMHO not necessary, it is causing no harm either.

> As long as the current version of the Strongswan package with farp-plugin 
> installed
> will permit a road-warrior client connected to the VPN to 'ping' a LAN-side 
> client
> then I would be 100% happy.

Now that you are using the up to date profile from Trusty's repo, do you
still get Apparmor denials? And is the plugin working as it should?


Regards,
Simon

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

Title:
  package:strongswan-plugin-farp may need apparmor config change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1514794/+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 1549363] Re: Unprivileged LXC will not start after today's updates

2016-02-29 Thread Christopher Townsend

The containers now start after today's updates (2.0.0~rc4-0ubuntu1).
Also a new kernel was installed which may have fixed something too.

At any rate, looks like it's fixed for now.

Thanks!

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1522319] Re: package samba-common 2:4.1.17+dfsg-4ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

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

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

Title:
  package samba-common 2:4.1.17+dfsg-4ubuntu3 failed to install/upgrade:
  le sous-processus script post-installation installé a retourné une
  erreur de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1522319/+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 1540214] Re: package mysql-server-5.6 5.6.28-0ubuntu0.15.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Changed in: mysql-5.6 (Ubuntu)
   Importance: Undecided => High

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

Title:
  package mysql-server-5.6 5.6.28-0ubuntu0.15.10.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1540214/+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 1538308] Re: package mysql-server-5.6 5.6.28-0ubuntu0.15.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Changed in: mysql-5.6 (Ubuntu)
   Importance: Undecided => High

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

Title:
  package mysql-server-5.6 5.6.28-0ubuntu0.15.10.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1538308/+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 1549363] Re: Unprivileged LXC will not start after today's updates

** 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/1549363

Title:
  Unprivileged LXC will not start after today's updates

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

2016-02-29 Thread bugproxy

--- Comment From thorsten.di...@de.ibm.com 2016-02-29 08:50 EDT---
Regarding the above strange behaviour in #5:
On a 4.4.0-8 system freshly installed (not updated from 4.4.0-7) with 
libzfcphbaapi0 installed the paths are recoverd and re-added as expected, as 
already described in case #2. And again, with case #1 the problem is 
reproducable.

What is this libzfcphbaapi0 package doing undercover? Normally it has no
interatice with multipath daemon. Does it change anything in the
multipath configuration?

Adding the libzfcphbaapi0 package to prevent symptoms of this bug can
not be the solution and it might be just by chance, that the symptom
vanished. I talked to zfcp development, and they confirmed that.

As already promised, I will continue some long term tests (cable pull
and other path loosing scenarios) on a 4.4.0-8 system with multipath-
tools_0.5.0+git1.656f8865-4 and kpartx_0.5.0+git1.656f8865-4. Results
should be available by tomorrow.

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

Title:
  multipathd drops paths of a temporarily lost device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+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 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..

2016-02-29 Thread Corey Bryant

Hui, I've uploaded your fix and it is now awaiting review by the sru
team for trusty-proposed:
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1_text=

** Changed in: neutron (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: neutron (Ubuntu Trusty)
   Status: Confirmed => Fix Committed

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

Title:
  neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-
  update_fanout..

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1393391/+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 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..

** Branch linked: lp:~ubuntu-server-dev/neutron/icehouse

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

Title:
  neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-
  update_fanout..

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1393391/+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 1551150] Re: devel-proposed doesn't boot

dmesg from a system that doesn't boot.

** Attachment added: "dmesg.out"

https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551150/+attachment/4584338/+files/dmesg.out

** Description changed:

Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446

ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent
images on other devices do not boot and hang on the boot logo.

From the list of changes, it could be lxc:
446: lxc 2.0.0~rc2-0ubuntu2
447: lxc 2.0.0~rc3-0ubuntu1

Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either.

lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium

* New upstream release (2.0.0~rc3)
- Make the cgfs backend and cgns work without cgmanager
- Manpage updates
- Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
* Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral

lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium

* Use versioned dependencies against the various binary packages.
* Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
* Move the lxcfs recommends from lxc-templates to liblxc1.
* Drop cgmanager, use the cgfs backend instead.
* Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.
+
+ Device tarballs between 446 and 447 are the same.

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

Title:
devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot

~ # cat /data/system-data/var/log/lxc/android.log 
  lxc-start 20160229125348.090 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 - 
cgroupfs failed to detect cgroup metadata
  lxc-start 20160229125348.091 ERRORlxc_start - start.c:lxc_spawn:1026 
- failed initializing cgroup support
  lxc-start 20160229125348.091 ERRORlxc_start - 
start.c:__lxc_start:1276 - failed to spawn 'android'
  lxc-start 20160229125348.091 ERRORlxc_start_ui - lxc_start.c:main:344 
- The container failed to start.
  lxc-start 20160229125348.092 ERRORlxc_start_ui - lxc_start.c:main:348 
- Additional information can be obtained by setting the --logfile and 
--logpriority options.


** Summary changed:

- devel-proposed doesn't boot
+ devel-proposed - android lxc container fails to start

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

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

Title:
  devel-proposed - android lxc container fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot

** Description changed:

  Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
  
- ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on
- other devices do not boot and hang on the boot logo.
+ ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent
+ images on other devices do not boot and hang on the boot logo.
  
  From the list of changes, it could be lxc:
  446: lxc 2.0.0~rc2-0ubuntu2
  447: lxc 2.0.0~rc3-0ubuntu1
  
  lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium
  
-   * New upstream release (2.0.0~rc3)
- - Make the cgfs backend and cgns work without cgmanager
- - Manpage updates
- - Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
-   * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral
+   * New upstream release (2.0.0~rc3)
+ - Make the cgfs backend and cgns work without cgmanager
+ - Manpage updates
+ - Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
+   * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral
  
  lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium
  
-   * Use versioned dependencies against the various binary packages.
-   * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
-   * Move the lxcfs recommends from lxc-templates to liblxc1.
-   * Drop cgmanager, use the cgfs backend instead.
-   * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.
+   * Use versioned dependencies against the various binary packages.
+   * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
+   * Move the lxcfs recommends from lxc-templates to liblxc1.
+   * Drop cgmanager, use the cgfs backend instead.
+   * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.

** Description changed:

  Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
  
  ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent
  images on other devices do not boot and hang on the boot logo.
  
  From the list of changes, it could be lxc:
  446: lxc 2.0.0~rc2-0ubuntu2
  447: lxc 2.0.0~rc3-0ubuntu1
+ 
+ Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either.
  
  lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium
  
    * New upstream release (2.0.0~rc3)
  - Make the cgfs backend and cgns work without cgmanager
  - Manpage updates
  - Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
    * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral
  
  lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium
  
    * Use versioned dependencies against the various binary packages.
    * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
    * Move the lxcfs recommends from lxc-templates to liblxc1.
    * Drop cgmanager, use the cgfs backend instead.
    * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.

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

Title:
  devel-proposed doesn't boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1274247] Re: [MIR] Glusterfs

2016-02-29 Thread ISIDOROS

is there any distribution that solves this bug? i'm using ubuntu 14.04,
updated cluster to 3.6 and is not working.

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

Title:
  [MIR] Glusterfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1274247/+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 1551150] Re: devel-proposed doesn't boot

changes list between 446 and 447.

** Attachment added: "446-447.changes"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584311/+files/446-447.changes

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

** Description changed:

- ubuntu-touch/devel-proposed/krillin.en/mako/ 338 and equivalent images
- on other devices do not boot and hang on the boot logo.
+ Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
+ 
+ ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on
+ other devices do not boot and hang on the boot logo.

** Description changed:

  Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
  
  ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on
  other devices do not boot and hang on the boot logo.
+ 
+ From the list of changes, it could be lxc:
+ 446: lxc 2.0.0~rc2-0ubuntu2
+ 447: lxc 2.0.0~rc3-0ubuntu1

** Description changed:

  Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
  
  ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on
  other devices do not boot and hang on the boot logo.
  
  From the list of changes, it could be lxc:
  446: lxc 2.0.0~rc2-0ubuntu2
  447: lxc 2.0.0~rc3-0ubuntu1
+ 
+ lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium
+ 
+   * New upstream release (2.0.0~rc3)
+ - Make the cgfs backend and cgns work without cgmanager
+ - Manpage updates
+ - Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
+   * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral
+ 
+ lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium
+ 
+   * Use versioned dependencies against the various binary packages.
+   * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
+   * Move the lxcfs recommends from lxc-templates to liblxc1.
+   * Drop cgmanager, use the cgfs backend instead.
+   * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.

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

Title:
  devel-proposed doesn't boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1318317] Re: openipmi startup script removes kernel modules

2016-02-29 Thread Breno Leitão

Nish,

I understand that this bug should be targeted for 16.04 as for 14.04. Is
it your understanding also?

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

Title:
  openipmi startup script removes kernel modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1318317/+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 1547517] Re: libdpdk should link against the library it uses

This bug was fixed in the package dpdk - 2.2.0-0ubuntu3

---
dpdk (2.2.0-0ubuntu3) xenial; urgency=medium

  * Guard dep8 tests against non supported platforms (LP: #1551158):
- d/t/control now avoids failing due to "dependencies are unsatisfiable"
  when fetching packages. The packages architecture restrictions got added
  to avoid that.
- d/t/check-dpdk-supported-arch.sh is called by all DPDK tests to ensure
  the platform is supported. If not it skips the test.

 -- Christian Ehrhardt   Mon, 29 Feb
2016 11:03:39 +

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

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

Title:
  libdpdk should link against the library it uses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1547517/+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 1551158] Re: DPDK dep8 tests failing on non supported platforms

This bug was fixed in the package dpdk - 2.2.0-0ubuntu3

---
dpdk (2.2.0-0ubuntu3) xenial; urgency=medium

  * Guard dep8 tests against non supported platforms (LP: #1551158):
- d/t/control now avoids failing due to "dependencies are unsatisfiable"
  when fetching packages. The packages architecture restrictions got added
  to avoid that.
- d/t/check-dpdk-supported-arch.sh is called by all DPDK tests to ensure
  the platform is supported. If not it skips the test.

 -- Christian Ehrhardt   Mon, 29 Feb
2016 11:03:39 +

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

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

Title:
  DPDK dep8 tests failing on non supported platforms

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

2016-02-29 Thread bugproxy

--- Comment From thorsten.di...@de.ibm.com 2016-02-29 06:27 EDT---
(In reply to comment #16)
> > Could you attempt to use the Debian package from Sid on top of the Ubuntu
> system?  This will help rule out kernel related issues vs. userspace package
> bugs.
>
> You can download from here
>
> http://ftp.us.debian.org/debian/pool/main/m/multipath-tools/multipath-
> tools_0.5.0+git1.656f8865-4_s390x.deb
>
> And then force install with
>
> sudo dpkg --force all --install
> multipath-tools_0.5.0+git1.656f8865-4_s390x.deb
>
> If this is successful, then I can prepare a package with some updated fixes
> from upstream; there are a number of changes to path related discovery in
> upstream multipath that aren't yet included in the Ubuntu version.

Hi Ryan,

I followed your proposal, installed 
multipath-tools_0.5.0+git1.656f8865-4_s390x.deb as described, and it worked 
fine and as expected, i.e. described problem does not occur.
On another system I installed both 
multipath-tools_0.5.0+git1.656f8865-4_s390x.deb and 
kpartx_0.5.0+git1.656f8865-4_s390x.deb - with the same result.
I did a detach/attach of the zfcp device and found, that it apperas for some 
seconds in status active faulty running, then it changed to failed faulty 
running and remained in that state until reattachment of the device. Then it 
changed back to active ready running.

Hi Christian,

in addition I did the following tests:

1. On a freshly installed xenial (installer version 427, kernel 4.4.0-8) with 
the already mentioned multipath.conf I found, that no zfcphbaapi stuff is 
installed per default.
kernel 4.4.0-8
multipath-tools 0.5.0-7ubuntu15 (was 7ubuntu14 before) and kpartx 
0.5.0-7ubuntu15
I did a detach/attach of the zfcp device and found, that it apperas for some 
seconds in status active faulty offline, then it changed to failed faulty 
offline and vanished and did not reappear upon reattachment of the device. I 
had the zfcp LUNs configure manually (via sysfs)

2. Then I installed zfcp-hbaapi-utils_2.1.1-0ubuntu1_s390x.deb and
libzfcphbaapi0_2.1.1-0ubuntu1_s390x.deb on top. With these two
additional packages I could not reproduce this problem.

3. I installed a system with kernel 4.4.0-7 and multipath-tools
0.5.0-7ubuntu14 + the above mentioned zfcphbaapi stuff. Problem was
reproducable.

4. I updated that system to multipath-tools 0.5.0-7ubuntu15. Problem was
still reproducable.

5. I updated that system to kernel 4.4.0-8. It should be now similar to
case #2. But problem was still reproducable. strange.

6. I switched several times back and forth between multipath-tools
0.5.0-7ubuntu15 and multipath-tools_0.5.0+git1.656f8865-4_s390x.deb.
With git1 it worked always, with 7ubuntu15 never. (although it did on a
freshly installed system, see #2)

So, for now we have two ways to solve/circumvent this problem:
a) use an updated multipath-tools package (from debian sid)
b) use an updated multipath-tools/kpartx packages from ubuntu (>= version 
0.5.0-7ubuntu15) AND zfcp-hbaapi-utils_2.1.1-0ubuntu1_s390x.deb and 
libzfcphbaapi0_2.1.1-0ubuntu1_s390x.deb on top. But that didn't help always 
(see case #5 above)

I found different values for path_selector in multipath-tools versions of 
ubuntu and debian:
ubuntu15: round-robin 0
debian-git: service-time 0
Then I set this in multipath.conf to the (usual) default "round-robin 0"
And with debian-git version the problem was still solved. So this setting 
should not matter.

Ryan,
although obviously only fixes from multipath-tools_0.5.0+git1.656f8865-4 are 
required to fix this problem, please consider and analyze, if it is better to 
get the complete set of patches in both multipath-tools AND kpartx from debian 
upstream (sid) instead of cherry picking some fixes.
The debian sid combination of multipath-tools AND kpartx does obviously not 
harm and is already 6 weeks old.

Anyway, I will do some other test with this combination.

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

Title:
  multipathd drops paths of a temporarily lost device

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

Fwd: Re: [Bug 1514794] Re: package:strongswan-plugin-farp may need apparmor config change

2016-02-29 Thread Steven Bishop

Hi there,

Sending again as message didn't show up in the thread.

 Forwarded Message 

Subject: Re: [Bug 1514794] Re: package:strongswan-plugin-farp may need apparmor 
config change
Date: Thu, 28 Jan 2016 20:26:48 +
From: Steven Bishop 
To: Bug 1514794 <1514...@bugs.launchpad.net>

Hi Simon,

Thanks for your email.

Had a quick look back at the details.

I've attached the complete copy of "/etc/apparmor.d/usr.lib.ipsec.charon"
that I've got installed and running (post-the-patch).

The excerpt I took from "/var/log/syslog" at the time of the bug-report
showed that apparmor was blocking the dgram packets that the strongswan farp 
plugin
was trying to generate when I had a Road-Warrior client connected to the VPN
and pinging a LAN-side client.

Until I put in the patch to "/etc/apparmor.d/usr.lib.ipsec.charon" of :

network packet dgram,

the ping wasn't getting any reply as apparmor was preventing the farp plugin
from generating the correct traffic for the ping to travel back from the 
LAN-side client
andacross the VPN boundary.

Doing a quick :

$ dpkg -S /etc/apparmor.d/usr.lib.ipsec.charon

returns :

strongswan-ike: /etc/apparmor.d/usr.lib.ipsec.charon

Looking in /var/log/auth.log, I can see that I installed :

 $ sudo apt-get install strongswan-ikev2

On Oct-17-2015 @ 17:30pm (BST = GMT + 1hr)

Looking at the current Trusty repo, the date on their copy is from 15-Nov-2015
so that working copy is actually newer than my bug-report.

I've pulled down a copy that particular .deb and looked at
it's copy of /etc/apparmor.d/usr.lib.ipsec.charon.

Looking at the version I've got installed I can see some noteable style 
differences
in the layout of the file.
The ordering of the '#include' statements are grouped all together.

I'm guessing that the package that I "apt-get install"ed on 17-Oct-2015
has been updated on the Trusty repo since that time.

By the way, the version currently available in the current Trusty repo
has the 2 lines:

line-24:
 network,
line-25:
 network raw,

If I'm reading this correctly, wouldn't line-24 mean that all network traffic 
is allowed.
and makes line-25 unnecessary.

[ ref :
http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Network_rules
]

As long as the current version of the Strongswan package with farp-plugin 
installed
will permit a road-warrior client connected to the VPN to 'ping' a LAN-side 
client
then I would be 100% happy.

Kind Regards,

Steven

On 24/01/2016 23:12, Simon Déziel wrote:
> @Steven, is this still an issue? The diff you showed includes "# network
> all," but this is not in the released version of charon's profile. Maybe
> you had a locally modified profile when you ran into the issue?
>
> Since the charon's profile in Trusty allows all networking, I don't
> think that adding "network packet dgram," makes sense. Would you mind
> confirm if the problem happened with the stock profile or not?
>
> ** Changed in: strongswan (Ubuntu)
> Status: New => Incomplete
>

** Attachment added: "usr.lib.ipsec.charon - my-patched-copy"

https://bugs.launchpad.net/bugs/1514794/+attachment/4584242/+files/usr.lib.ipsec.charon%20-%20my-patched-copy

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

Title:
  package:strongswan-plugin-farp may need apparmor config change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1514794/+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 1536827] Re: adt-build-lxc unmounted my home directory

2016-02-29 Thread Martin Pitt

adt-build-lxc only uses LXC commands, it does not do any mounting by
itself. I use ecyrptfs /home as well, so this isn't broken in general.
If you can reproduce this, please attach the full output of the program
you were running, and the output of "journalctl -b" and /var/log/lxc/*.

** Package changed: autopkgtest (Ubuntu) => lxc (Ubuntu)

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

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

Title:
  adt-build-lxc unmounted my home directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1536827/+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 1536827] [NEW] adt-build-lxc unmounted my home directory

You have been subscribed to a public bug:

I'm running wily (autopkgtest 3.17.4) with an encrypted home directory.
I ran adt-build-lxc ubuntu xenial and it unmounted my home directory,
which was a bit surprising!

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

-- 
adt-build-lxc unmounted my home directory
https://bugs.launchpad.net/bugs/1536827
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
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 1551158] Re: DPDK dep8 tests failing on non supported platforms

FYI - this started on Friday and while we were almost done right now it
is worth to document this for further reference e.g. from the
Changelogs.

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

Title:
  DPDK dep8 tests failing on non supported platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1551158/+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 1549778] Re: ceph 0.94.6

Package update for wily prepared - just waiting on some extra PPA
capacity so I can pre-upload test.

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

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

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

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

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

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

** Changed in: cloud-archive/kilo
   Importance: Undecided => High

** Summary changed:

- ceph 0.94.6
+ [SRU] ceph 0.94.6

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

Title:
  [SRU] ceph 0.94.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1549778/+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 1551158] [NEW] DPDK dep8 tests failing on non supported platforms

Public bug reported:

While adding further tests we realized that DPDK tests would fail on non
supported platforms.

While it makes perfect sense for them to fail, most involved people wondered 
why it even ran there.
Long story short: The dpdk package builds packages for all platforms like 
libdpdk-dev - therefore it's tests are tried to run on all platforms.

Now all the time the only thing avoiding this issue to be seen was that the 
tests had an "isolation-machine" restriction.
That accidentally limited the execution just to the supported i386 and amd64 
for now.

When adding another Test which did not have that restrictions the issues
started to show up.

** Affects: dpdk (Ubuntu)
 Importance: High
 Status: Triaged

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

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

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

Title:
  DPDK dep8 tests failing on non supported platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1551158/+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 1551158] Re: DPDK dep8 tests failing on non supported platforms

After discussing on #ubuntu-devel it was decided that the tests should guard 
themselves and skip the test if not appropriate.
Such specific HW need seems rare and there is no e.g. autopkgtest feature to 
limit Architectures.

Note: it was considered a "regression" because the fact that before we
couldn't run it was not a "fault" of the Test (but of our environment).
So when the new failing test landed it became a regression.

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

Title:
  DPDK dep8 tests failing on non supported platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1551158/+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 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..

2016-02-29 Thread Xiang Hui

Corey,

  Thanks for looking at it, I will keep watching it for the new updates
and please help to update it if there is any news, thanks.

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

Title:
  neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-
  update_fanout..

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1393391/+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 1540407] Re: multipathd drops paths of a temporarily lost device

Hi,
I couldn't reproduce today.

The device stays in:
0:0:0:1074675728 sdb 8:16 active faulty offline
And when re-adding it comes back online just nice.


The way I configured was via chzdev like:
I used the z/VM approach with detaching the FCP adapter.
I used the multipath.conf as reported initially.
chzdev zfcp --enable 7200
chzdev zfcp --enable 7300
chzdev zfcp-lun --enable --online   <- warning I enable ALL, you might want 
just some of them


We realized as difference to Thorstens systems I also had from this ppa: sudo 
add-apt-repository ppa:xnox/nonvir
>From here I installed packages:
libzfcphbaapi0
zfcp-hbaapi-utils

Versions:
libzfcphbaapi0  2.1.1-0ubuntu1
zfcp-hbaapi-utils  2.1.1-0ubuntu1
multipath-tools-boot 0.5.0-7ubuntu15
Kernel 4.4.0-8-generic

I had a call with Thorsten and he will re-verify with the latest version on his 
system.
If his case still fails he might give it a try with the "way I configured it".

Other than that Thorsten suggested he would like it to see the merge
happening to the more recent upstream content that Ryan mentioned.

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

Title:
  multipathd drops paths of a temporarily lost device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+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 1541914] Re: passwd depends on init-system-helpers (>= 1.18~); however: Version of init-system-helpers on system is 1.14

2016-02-29 Thread Martin Pitt

I did a couple of trusty→ xenial upgrades but could not reproduce this.

The first error in that log was this:

dpkg: considering deconfiguration of init-system-helpers, which would be broken 
by installation of upstart ...
dpkg: yes, will deconfigure init-system-helpers (broken by upstart)
Preparing to unpack .../upstart_1.13.2-0ubuntu18_amd64.deb ...
De-configuring init-system-helpers (1.14) ...
Unpacking upstart (1.13.2-0ubuntu18) over (1.12.1-0ubuntu4.2) ...

which got introduced by
http://launchpadlibrarian.net/222852012/upstart_1.13.2-0ubuntu16_1.13.2-0ubuntu17.diff.gz

This apparently leads to a dependency loop. The Replaces: must be kept,
but we could drop the Breaks: to make apt's job of  breaking such loops
simpler.

** Package changed: init-system-helpers (Ubuntu) => upstart (Ubuntu)

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

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  passwd depends on init-system-helpers (>= 1.18~); however: Version of
  init-system-helpers on system is 1.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1541914/+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 1549778] Re: ceph 0.94.6