from:"ryan"

Now with less libaio-dev in control file for no AIO.  Thanks for
catching my mistake

** Patch added: "old_ubuntu-new_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616629/+files/old_ubuntu-new_ubuntu.debdiff

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

Title:
  Please merge tgt 1.0.63 from 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

Re: [Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

On Tue, Mar 29, 2016 at 9:05 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:

> Ryan, for ease of review and sponsorship please provide an incremental
> debdiff against the package that's already in xenial-proposed.
>

I actually did in comment 18, but I didn't know that was sufficient and
subsequently uploaded
those larger debdiffs.  Thanks for the tips.


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1473691
>
> Title:
>   [FFe] squid: Update to latest upstream release (3.5)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions
>

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

Title:
  [FFe] squid: Update to latest upstream release (3.5)

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

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

Re: [Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

As far as I can see, the entire versioned code block here is wrong, and
> you should *only* be restarting squid.
>
>
The block (without my addition) is from debian itself.  The original block
that's
present in debian:

update-rc.d squid defaults 30 >/dev/null

if test -d /etc/squid3 && dpkg --compare-versions "$2" lt '3.5'; then
invoke-rc.d squid3 stop
invoke-rc.d squid start
else
invoke-rc.d squid restart
fi


However, this failed in our dist-upgrade from trusty scenario as the squid3
service file no longer
exists.  Reading your analysis; it seems that /etc/init.d/squid3 should
still be on disk;
but it was not.

In the dist-upgrade from trusty case; I believe we can just use the squid
restart.

In the upgrade from wily case, it's not clear to me why the
/etc/init.d/squid3 service
file would still be on disk when it wasn't when upgrading from trusty?

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

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

I've attached new debdiff integrating the change to the squid.postinst
fix.  We would like to get this build uploaded into proposed (and locked
as the current one is) to continue wider testing of the new squid.

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

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

Old Ubuntu to New Ubuntu debdiff

** Patch added: "old-ubuntu-to-new-ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4616441/+files/old-ubuntu-to-new-ubuntu.debdiff

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

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

Old Ubuntu to New Debian debdiff

** Patch added: "old-ubuntu-to-new-debian.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4616440/+files/old-ubuntu-to-new-debian.debdiff

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

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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: Please merge tgt 1.0.63 from Debian (unstable)

Dropped AIO enablement; while the feature was isolated, we've had no
testing on the aio backend; we can always enable it later if we get
enough testing to ensure proper functionality.  Therefore dropping the
FFE and just requesting a merge with Debian.

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

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

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

Old Ubuntu -> New Debian debdiff

** Patch added: "old_ubuntu-new_debian.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616323/+files/old_ubuntu-new_debian.debdiff

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

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

Old Ubuntu to New Ubuntu

** Patch added: "old_ubuntu-new_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616324/+files/old_ubuntu-new_ubuntu.debdiff

** Summary changed:

- [FFE] Please merge tgt 1.0.63 from Debian (unstable)
+ Please merge tgt 1.0.63 from Debian (unstable)

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

Title:
  Please merge tgt 1.0.63 from 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 1546445] Re: support vhost user without specifying vhostforce

2016-03-29 Thread Ryan Beisner

FYI, following additional regression tests, today we promoted qemu 2.2
+dfsg-5expubuntu9.7~cloud2 from kilo-proposed to kilo-updates in the
Ubuntu Cloud Archive.


** Changed in: cloud-archive/kilo
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are 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 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..

2016-03-29 Thread Ryan Beisner

FYI, following additional regression tests, today we promoted neutron
2014.1.5-0ubuntu4~cloud0 from proposed to icehouse-updates in the Ubuntu
Cloud Archive.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

2016-03-28 Thread Ryan Harper

Kick,

Thanks for the thorough upgrade test. I was able to recreate and debug
the proposed package install script. It appears that the squid.postinst
expects to find a /etc/init.d/squid3 service script if we also have an
existing /etc/squid3 directory. However, in my testing, we do have the
/etc/squid3, but the service script itself is called /etc/init.d/squid.

Manually fixing up this in the /var/lib/dpkg/info/squid.postinst and
then running sudo apt-get -f install will allow squid upgrade to
proposed levels complete successfully.

After the upgrade, I can confirm that squid-deb-proxy and squidGuard
work correctly. I'm attaching a debdiff with a fix for this issue (we
can check which init script is present and use that to stop/start the
squid service after install).

I build squid from the merge branch from rabc's git repo with the
attached debdiff, created a local ppa (including a copy of the libecap3
package) and performed an apt-get update && apt-get install squid which
upgrades and installs successfully.

After this, squid, squid-deb-proxy and squidGuard all continue to work.

** Patch added: "lp1473691-dist-upgrade-from-1404.debdiff"

https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4614978/+files/lp1473691-dist-upgrade-from-1404.debdiff

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

Title:
[FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1560939] Re: libvirt-bin fails to install on a fresh xenial server

2016-03-25 Thread Ryan Harper

This error was unrelated to libvirt-bin itself, rather the locales
package from glibc in Xenial had an issue with generating locales (and
locale-archive);  This was fixed in a new release (on 3/23) and
subsequent cloud builds after 3/22 which have newer glibc locales
package do not experience this issue.

If you still feel there is an issue after updating the locales package,
please re-open this bug.

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

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

Title:
  libvirt-bin fails to install on a fresh xenial server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1560939/+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 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 1559775] Re: package slapd 2.4.42+dfsg-2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-03-20 Thread Ryan Tandy

from DpkgTerminalLog:

Setting up slapd (2.4.42+dfsg-2ubuntu3) ...
  Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.31-1+nmu2ubuntu8.2... 
done.
  Moving old database directories to /var/backups:

  Backup path /var/backups/dc=nodomain-2.4.31-1+nmu2ubuntu8.2.ldapdb
exists. Giving up...

The upgrade script is trying to back up your existing slapd config
before upgrading, but the location it wants to back it up to already
exists (maybe from a previous upgrade attempt, or a dpkg-reconfigure, or
something else). Remove or rename that directory, and issue the command

dpkg --configure --pending

to complete the upgrade.

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

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

Title:
  package slapd 2.4.42+dfsg-2ubuntu3 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/openldap/+bug/1559775/+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

Here's my initial test with the merged multipath-tools test.
I had the FCP devices enabled with the 0.5.0+git-1ubuntu2 package 
installed from the merges ppa  and rebooted the system.

After booting, I confirmed the paths were up, then used a vmcp command to 
disconnect the devices.
I then queried mulitpath over a number of minutes to ensure the path remains 
(but shows faulty).
After 15 minutues or so I contacted an admin to renable the FCP devices and 
observed the paths
becoming restored in multipath

** Attachment added: "z.txt"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+attachment/4595271/+files/z.txt

-- 
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 1550646] Re: package exim4-daemon-light 4.86-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137

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

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

Title:
  package exim4-daemon-light 4.86-3ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 137

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

Install log of tgt 1.0.63-1ubuntu1 under lxd machine container.

** Attachment added: "install.log"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595176/+files/install.log

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

sbuild build log of 1.0.63-1ubuntu1 on amd64

** Attachment added: "tgt_1.0.63-1ubuntu1_amd64-20160309-1702.build"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595175/+files/tgt_1.0.63-1ubuntu1_amd64-20160309-1702.build

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

debdiff (old/ubuntu) 1.0.62-1ubuntu1 to (new/ubuntu) 1.0.63-1ubuntu1

** Patch added: "old_ubuntu-new_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595174/+files/old_ubuntu-new_ubuntu.debdiff

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

debdiff (old/ubuntu) 1.0.62-1ubuntu1  to (new/debian) 1.0.63-1

** Patch added: "old_ubuntu-new_debian.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595173/+files/old_ubuntu-new_debian.debdiff

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

Public bug reported:

New Upstream release which incorporates one outstanding patch in 1.0.62
and adds support for AIO backend for tgt.

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

-- 
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 1540407] Re: multipathd drops paths of a temporarily lost device

Thorsten,

Here's my PPA with the merged multipath-tools package for s390x:

https://launchpad.net/~raharper/+archive/ubuntu/merges/

You can add it via:

sudo add-apt-repository ppa:raharper/merges
sudo apt-get update
sudo apt-cache policy multipath-tools

The last command should show you a newer version from the ppa as
Candidate.

Then you can update the multpath-tools binaries (and kpartx friends)
with:

sudo apt-get install kpartx kpartx-boot multipath-tools multipath-tools-
boot

This package in the PPA is not in final form; but any testing/feedback on it 
will help us
close any issues with the merge to latest debian.

-- 
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 1540407] Re: multipathd drops paths of a temporarily lost device

Hi Thorsten,

We're going to merge with upstream debian.  That work is tracked under
bug 1551952.

I'm now working on getting an s390x build of the package and reproducing on one 
of the systems to
help test that the merge addresses this bug (and doesn't regress anything as 
well).

-- 
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 1551952] Re: FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable

dpkg install of kpartx and multipath-tools on Xenial amd64 kvm VM.

** Attachment added: "install.log"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594203/+files/install.log

-- 
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 1551952] Re: FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable

debdiff old/ubuntu (0.5.0-7ubuntu16 ) to new/debian
(0.5.0+git1.656f8865-5)

** Patch added: "old_ubuntu-new_debian.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594201/+files/old_ubuntu-new_debian.debdiff

-- 
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 1551952] Re: FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable

I've run the package under adt-run and it passes.

After installing and running in a VM using virtio-scsi configured as
multipath, I can successfully find the devices configure.

ubuntu@mp1:~$ dpkg --list | grep multipath-tools
ii  multipath-tools  0.5.0+git1.656f8865-5ubuntu2
amd64maintain multipath block device access
ii  multipath-tools-boot 0.5.0+git1.656f8865-5ubuntu2
all  Support booting from multipath devices
ubuntu@mp1:~$ sudo multipath -ll
0QEMU_QEMU_HARDDISK_0001 dm-0 QEMU,QEMU HARDDISK
size=10G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 2:0:0:0 sda 8:0  active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
  `- 2:0:0:1 sdb 8:16 active ready running

-- 
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 1551952] Re: FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable

sbuild log of updated multipath-tools

** Attachment added: 
"multipath-tools_0.5.0+git1.656f8865-5ubuntu2_amd64-20160309-1159.build"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594202/+files/multipath-tools_0.5.0+git1.656f8865-5ubuntu2_amd64-20160309-1159.build

-- 
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 1551952] Re: FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable

debdiff from old/ubuntu (0.5.0-7ubuntu16) to new/ubuntu
(0.5.0+git1.656f8865-5ubuntu1)


** Patch added: "old_ubuntu-new_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594200/+files/old_ubuntu-new_ubuntu.debdiff

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

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

On Mon, Mar 7, 2016 at 5:40 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> This appears to have fixed the nvme partition problem but, I'm sure
> there are nicer ways to do it.
>
>
Hi Rob!

Thanks for confirming a workaround.


> root@maas1:~# diff -u
> /usr/lib/python3/dist-packages/curtin/commands/block_meta.py
> /usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
> --- /usr/lib/python3/dist-packages/curtin/commands/block_meta.py
> 2016-03-07 23:37:34.137946135 +
> +++ /usr/lib/python3/dist-packages/curtin/commands/block_meta.py.orig
>  2016-03-07 23:37:28.565864667 +
> @@ -368,13 +368,7 @@
>  partnumber = determine_partition_number(vol.get('id'),
> storage_config)
>  disk_block_path = get_path_to_storage_volume(vol.get('device'),
>   storage_config)
> -
> -if disk_block_path == '/dev/nvme0n1':
> -volume_path = disk_block_path + 'p' + str(partnumber)
> -else
> -volume_path = disk_block_path +  str(partnumber)
> -
> +volume_path = disk_block_path + str(partnumber)
>  devsync_vol = os.path.join(disk_block_path)
>
>  elif vol.get('type') == "disk":
>
> --
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> https://bugs.launchpad.net/bugs/1401190
>
> Title:
>   curtin makes assumptions about partition names on all devices
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
>

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

Title:
  curtin makes assumptions about partition names on all devices

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

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

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

On Mon, Mar 7, 2016 at 1:50 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> Thanks, let me know if you need me to make any changes or run through
> any tests.
>
> A quick question if I may: How is the config generated when the node is
> deploying? I have found that storage config in curtin_userdata on the
> maas server appears to be ignored or clobbered e.g.
>

If you're using maas 1.8, or maas 1.9; maas itself is generating storage
configuration

https://maas.ubuntu.com/docs/storage.html#storage

Ideally you don't need to inject your own custom partitioning/storage
config; you
configure maas in the UI and it emits storage configuration to curtin.

It's not clear to me how you're combining your own user-data with what MaaS
supplies.

> If I execute: /var/lib/cloud/instance/scripts/part-001 # fails due to bug
> cd curtin

> cat configs/config-000.cfg # I see the storage config I have set on the
> maas server in curtin_userdata
>
> #cloud-config
> ...
> ...
>
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
>   - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 1, offset:
> 4194304B, size: 128026935296B, type: partition, wipe: superblock}
>   - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format,
> path: /dev/nvme0n1p1, volume: nvme0n1p1}
>   version: 1
>
> cat configs/config-002.cfg # appears to be the device(s) that are found
> during commissioning
>
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {grub_device: true, id: sdc, model: Samsung SSD 840, name: sdc,
> ptable: gpt, serial: S1D9NSAFB19195M,
> type: disk, wipe: superblock}
>   - {device: sdc, id: sdc-part1, name: sdc-part1, number: 1, offset:
> 4194304B, size: 1000198897664B,
> type: partition, uuid: 8bcce503-ad8f-495e-a158-669829585db2, wipe:
> superblock}
>   - {fstype: ext4, id: sdc-part1_format, label: '', type: format, uuid:
> 0195af9d-764d-4b35-8e53-07573aa4c057,
> volume: sdc-part1}
>   - {device: sdc-part1_format, id: sdc-part1_mount, path: /, type: mount}
>   version: 1
> ...
> ...
> 
>
> I was trying to test an install to one of the other disks which also
> failed.
>

It's hard to say;  if you have the entire curtin config sent I may be able
to parse out what's going on:
>From the maas cli:

maas  node get-curtin-config 

and attach to this bug.

>
> I had to remove the nvme device and 2 other devices from the web ui as
> configs/config-002.cfg had every disk listed, including the nvme device
> which I had specified in curtin_userdata. The config data is that from
> commissioning.
>
> I also noted that despite me selecting a different boot device that it
> was still trying to install grub to sda.
>

>
> Does this sound like another bug with curtin or should I raise it with
> the maas project?
>

Boot device selection *could* be a maas issue or curtin.  I suggest
opening a new bug against MAAS for the boot device selection,
and I can add a MAAS task to this one.  In both places, please append
the output from the maas get-curtin-config output attached.  This helps
us debug whether MAAS sent curtin valid configuration and determine
if we need to fix the bug in MAAS or curtin itself.

In _this_ bugs case; if the config you send which defines 'number' field in
the partition dictionary, then curtin will *faithfully* attempt to use
 directly; ie; curtin is doing what it was told.

In the case where 'number' is not defined, curtin will attempt to determine
the
correct partition number.  For NVME devices, the logic is not sufficient
since
it doesn't really know that the underlying device is an NVME and NVME
devices
use different scheme for naming partition device entries (p vs.
just )

In this bug, we will teach curtin to detect NVME devices and pick the
correct partition dev path
if the config does _NOT_ include a specified 'number' value.

I'll open a MAAS task in this bug to help track if MAAS itself needs to
know a device is an NVME
and then specify the 'number' differently ('p1' vs '1').

--
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> https://bugs.launchpad.net/bugs/1401190
>
> Title:
>   curtin makes assumptions about partition names on all devices
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
>

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

Title:
  c

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

On Mon, Mar 7, 2016 at 2:15 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> Here you go
>
> /var/lib/cloud/instance/scripts/part-001 extract
>
> cd curtin
>
> cat configs/config-000.cfg
> #cloud-config
> …
> ...
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
>   - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1',
> offset: 4194304B, size: 128026935296B, type: partition, wipe: superblock}
>   - {fstype: ext4, id: nvme0n1p1_format, label: 'rootfs', type: format,
> path: /dev/nvme0n1p1, volume: nvme0n1p1}
>   version: 1
>
> bin/curtin --showtrace --install-deps install
> --config=configs/config-000.cfg
> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
> Creating new GPT entries.
> The operation has completed successfully.
> An error occured handling 'nvme0n1p1': IOError - [Errno 2] No such file or
> directory: '/sys/block/nvme0n1/nvme0n1None/size'
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/block_meta.py", line 62, in block_meta
> meta_custom(args)
>   File "curtin/commands/block_meta.py", line 1083, in meta_custom
> handler(command, storage_config_dict)
>   File "curtin/commands/block_meta.py", line 565, in partition_handler
> with open(os.path.join(previous_partition, "size"), "r") as fp:
> IOError: [Errno 2] No such file or directory:
> '/sys/block/nvme0n1/nvme0n1None/size'
> [Errno 2] No such file or directory: '/sys/block/nvme0n1/nvme0n1None/size'
> Installation failed with exception: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nAn error occured handling \'nvme0n1p1\': IOError - [Errno 2]
> No such file or directory:
> \'/sys/block/nvme0n1/nvme0n1None/size\'\nTraceback (most recent call
> last):\n  File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in
> main\nret = args.func(args)\n  File "curtin/commands/block_meta.py",
> line 62, in block_meta\nmeta_custom(args)\n  File
> "curtin/commands/block_meta.py", line 1083, in meta_custom\n
> handler(command, storage_config_dict)\n  File
> "curtin/commands/block_meta.py", line 565, in partition_handler\nwith
> open(os.path.join(previous_partition, "size"), "r") as fp:\nIOError: [Errno
> 2] No such file or directory:
> \'/sys/block/nvme0n1/nvme0n1None/size\'\n[Errno 2] No such file or
> directory: \'/sys/block/nvme0n1/nvme0n1None/size\'\n'
> Stderr: ''
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/install.py", line 399, in cmd_install
> raise e
>


OK, no need to let you continue to debug getting curtin partition handling
to learn about NVME.

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

Title:
  curtin makes assumptions about partition names on all devices

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

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

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

One more try, lets specify the partition "number" as 'p1' instead.

- {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1', offset:
4194304B, size: 128026935296B, type: partition, uuid:
e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}


On Mon, Mar 7, 2016 at 1:24 PM, Ryan Harper <ryan.har...@canonical.com>
wrote:

> OK; thanks.  I need to work with nvme devices on Xenial;  it looks like
> the storage naming rules for partitions are different for NVME devices (p1,
> p2, p3) versus other disks (1, 2, 3 4);
>
>
> On Mon, Mar 7, 2016 at 12:54 PM, Rob Sanderson <1401...@bugs.launchpad.net
> > wrote:
>
>> Hi Ryan,
>>
>> I have tried that but no luck.
>>
>> Config using curtin defaults:
>>
>> --
>> cat configs/config-002.cfg
>>
>> partitioning_commands:
>>   builtin: [curtin, block-meta, custom]
>> storage:
>>   config:
>>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
>> disk, wipe: superblock}
>>   - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1,
>> offset: 4194304B, size: 128026935296B, type: partition, uuid:
>> e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
>>   - {fstype: ext4, id: nvme0n1-part1_format, label: 'rootfs', type:
>> format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1-part1,
>> path: /dev/nvme0n1p1}
>>   - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /,
>> type: mount}
>>   version: 1
>>
>> bin/curtin --showtrace --install-deps install
>> --config=configs/config-002.cfg
>>
>>
>> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
>> Creating new GPT entries.
>> The operation has completed successfully.
>> The operation has completed successfully.
>> An error occured handling 'nvme0n1-part1_format': ValueError -
>> '/dev/nvme0n11': no such file or directory
>> Traceback (most recent call last):
>>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
>> ret = args.func(args)
>>   File "curtin/commands/block_meta.py", line 62, in block_meta
>> meta_custom(args)
>>   File "curtin/commands/block_meta.py", line 1083, in meta_custom
>> handler(command, storage_config_dict)
>>   File "curtin/commands/block_meta.py", line 672, in format_handler
>> mkfs.mkfs_from_config(volume_path, info)
>>   File "curtin/block/mkfs.py", line 207, in mkfs_from_config
>> label=info.get('label'))
>>   File "curtin/block/mkfs.py", line 145, in mkfs
>> raise ValueError("'%s': no such file or directory" % path)
>> ValueError: '/dev/nvme0n11': no such file or directory
>> '/dev/nvme0n11': no such file or directory
>> Installation failed with exception: Unexpected error while running
>> command.
>> Command: ['curtin', 'block-meta', 'custom']
>> Exit code: 3
>> Reason: -
>> Stdout: 'Creating new GPT entries.\nThe operation has completed
>> successfully.\nThe operation has completed successfully.\nAn error occured
>> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
>> file or directory\nTraceback (most recent call last):\n  File
>> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
>> args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in
>> block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py",
>> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
>> File "curtin/commands/block_meta.py", line 672, in format_handler\n
>> mkfs.mkfs_from_config(volume_path, info)\n  File "curtin/block/mkfs.py",
>> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n  File
>> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
>> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
>> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
>> Stderr: ''
>> Traceback (most recent call last):
>>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
>> ret = args.func(args)
>>   File "curtin/commands/install.py", line 399, in cmd_install
>> raise e
>> ProcessExecutionError: Unexpected error while running command.
>> Command: ['curtin', 'block-meta', 'custom']
>> Exit code: 3
>> Reason: -
>> Stdout: 'Creating new GP

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

OK; thanks.  I need to work with nvme devices on Xenial;  it looks like the
storage naming rules for partitions are different for NVME devices (p1, p2,
p3) versus other disks (1, 2, 3 4);


On Mon, Mar 7, 2016 at 12:54 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi Ryan,
>
> I have tried that but no luck.
>
> Config using curtin defaults:
>
> --
> cat configs/config-002.cfg
>
> partitioning_commands:
>   builtin: [curtin, block-meta, custom]
> storage:
>   config:
>   - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
> disk, wipe: superblock}
>   - {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1,
> offset: 4194304B, size: 128026935296B, type: partition, uuid:
> e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
>   - {fstype: ext4, id: nvme0n1-part1_format, label: 'rootfs', type:
> format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1-part1,
> path: /dev/nvme0n1p1}
>   - {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /, type:
> mount}
>   version: 1
>
> bin/curtin --showtrace --install-deps install
> --config=configs/config-002.cfg
>
> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
> Creating new GPT entries.
> The operation has completed successfully.
> The operation has completed successfully.
> An error occured handling 'nvme0n1-part1_format': ValueError -
> '/dev/nvme0n11': no such file or directory
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/block_meta.py", line 62, in block_meta
> meta_custom(args)
>   File "curtin/commands/block_meta.py", line 1083, in meta_custom
> handler(command, storage_config_dict)
>   File "curtin/commands/block_meta.py", line 672, in format_handler
> mkfs.mkfs_from_config(volume_path, info)
>   File "curtin/block/mkfs.py", line 207, in mkfs_from_config
> label=info.get('label'))
>   File "curtin/block/mkfs.py", line 145, in mkfs
> raise ValueError("'%s': no such file or directory" % path)
> ValueError: '/dev/nvme0n11': no such file or directory
> '/dev/nvme0n11': no such file or directory
> Installation failed with exception: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nThe operation has completed successfully.\nAn error occured
> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
> file or directory\nTraceback (most recent call last):\n  File
> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
> args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in
> block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py",
> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
> File "curtin/commands/block_meta.py", line 672, in format_handler\n
> mkfs.mkfs_from_config(volume_path, info)\n  File "curtin/block/mkfs.py",
> line 207, in mkfs_from_config\nlabel=info.get(\'label\'))\n  File
> "curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
> such file or directory" % path)\nValueError: \'/dev/nvme0n11\': no such
> file or directory\n\'/dev/nvme0n11\': no such file or directory\n'
> Stderr: ''
> Traceback (most recent call last):
>   File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
> ret = args.func(args)
>   File "curtin/commands/install.py", line 399, in cmd_install
> raise e
> ProcessExecutionError: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: 'Creating new GPT entries.\nThe operation has completed
> successfully.\nThe operation has completed successfully.\nAn error occured
> handling \'nvme0n1-part1_format\': ValueError - \'/dev/nvme0n11\': no such
> file or directory\nTraceback (most recent call last):\n  File
> "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
> args.func(args)\n  File "curtin/commands/block_meta.py", line 62, in
> block_meta\nmeta_custom(args)\n  File "curtin/commands/block_meta.py",
> line 1083, in meta_custom\nhandler(command, storage_config_dict)\n
> File "curtin/commands/block_meta.py", line 672, in format_handler\n
> mkfs.mkfs_from

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

Yeah, looks like the mkfs code is expecting you to include label: 'some
label' in the format dictionary.
Can you try injecting a label into the format dictionary:


 - {fstype: ext4, id: nvme0n1-part1_format, label: 'SOME_LABEL_HERE', type:
format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877,
volume: nvme0n1-part1}

This is a bug in curtin as label's aren't required.

On Sun, Mar 6, 2016 at 3:58 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> ls -la /dev/nvme0*
> crw--- 1 root root  10, 57 Mar  6 21:10 /dev/nvme0
> brw-rw 1 root disk 259,  0 Mar  6 21:44 /dev/nvme0n1
> brw-rw 1 root disk 259,  1 Mar  6 21:44 /dev/nvme0n1p1
>
> --
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> https://bugs.launchpad.net/bugs/1401190
>
> Title:
>   curtin makes assumptions about partition names on all devices
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
>

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

Title:
  curtin makes assumptions about partition names on all devices

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

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

Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices

2016-03-06 Thread Ryan Harper

On Sat, Mar 5, 2016 at 3:56 AM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:

> Hi,
>
> I'm still seeing this issue on Xenial.
>
> root@maas1:~# cat /etc/lsb-release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=16.04
> DISTRIB_CODENAME=xenial
> DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"
> root@maas1:~# uname -a
> Linux maas1 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016
> x86_64 x86_64 x86_64 GNU/Linux
> root@maas1:~# dpkg -l|grep curtin
> ii  curtin-common   0.1.0~bzr359-0ubuntu1   all
>   Library and tools for curtin installer
> ii  python3-curtin  0.1.0~bzr359-0ubuntu1   all
>   Library and tools for curtin installer
>
> I have tried with the default curtin_userdata and have also tried:
>
> partitioning_commands:
>  builtin: curtin block-meta custom
>
> storage:
> version: 1
> config:
>   - id: nvme0n1
> type: disk
> ptable: msdos
>

If you don't specify a 'serial': or 'path' then curtin will attempt to
deduce the path via the id.

Can you try adding:

 path: /dev/nvme0

If that is indeed the path to the device.


>   - id: nvme0n1p1
> type: partition
> number: 1
> size: 128GB
> device: nvme0n1
> flag: boot
>   - id: nvme0n1p1_root
> type: format
> fstype: ext4
> volume: nvme0n1p1
>   - id: nvme0n1p1_mount
> type: mount
> path: /
> device: nvme0n1p1_root
>
> The error is as follows:
>
> + exec curtin --install-deps install --config=configs/config-000.cfg
> --config=configs/config-001.cfg --config=configs/config-002.cfg
> --config=configs/config-003.cfg --config=configs/config-004.cfg
> http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
> Error: /dev/sda: unrecognised disk label
> Error: /dev/sda: unrecognised disk label
> Error: /dev/sdb: unrecognised disk label
> Error: /dev/sdb: unrecognised disk label
> Error: /dev/sdc: unrecognised disk label
> Error: /dev/sdc: unrecognised disk label
> An error occured handling 'nvme0n1-part1_format': ValueError -
> '/dev/nvme0n11': no such file or directory
> '/dev/nvme0n11': no such file or directory
> Installation failed with exception: Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: "Error: /dev/sda: unrecognised disk label\nError: /dev/sda:
> unrecognised disk label\nError: /dev/sdb: unrecognised disk label\nError:
> /dev/sdb: unrecognised disk label\nError: /dev/sdc: unrecognised disk
> label\nError: /dev/sdc: unrecognised disk label\nAn error occured handling
> 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or
> directory\n'/dev/nvme0n11': no such file or directory\n"
> Stderr: ''
> Unexpected error while running command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: "Error: /dev/sda: unrecognised disk label\nError: /dev/sda:
> unrecognised disk label\nError: /dev/sdb: unrecognised disk label\nError:
> /dev/sdb: unrecognised disk label\nError: /dev/sdc: unrecognised disk
> label\nError: /dev/sdc: unrecognised disk label\nAn error occured handling
> 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or
> directory\n'/dev/nvme0n11': no such file or directory\n"
> Stderr: ''
>
> --
> You received this bug notification because you are subscribed to curtin
> in Ubuntu.
> Matching subscriptions: curtin-bugs, curtin-bugs-all
> https://bugs.launchpad.net/bugs/1401190
>
> Title:
>   curtin makes assumptions about partition names on all devices
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions
>

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

Title:
  curtin makes assumptions about partition names on all devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1401190/+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-01 Thread Ryan Harper

** Attachment added: "Changelog from 0.5.0 to version in Debian unstable; 
dropped "fix" entries and other non-features."
   
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4585938/+files/Changelog-0.5.0..656f8865.txt

-- 
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 1551952] [NEW] FFE: Please merge multipath-tools 0.5.0+git1.656f8865 from Debian unstable

2016-03-01 Thread Ryan Harper

Public bug reported:

Upstream hasn't released a new version, but there are a large number of
new features available in the version included in Debian unstable.

This version from Debian has been confirmed to fix bug 1540407

The new version of the package will be tested with:
  - MAAS driven Power8 installs on hosts with multipath configured
 -  s390x FCP multipath devices as in bug 1540407.
  - kvm VM with virtio-scsi multipath

** Affects: multipath-tools (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Upstream hasn't released a new version, but there are a large number of
  new features available in the version included in Debian unstable.
  
- This version from Debian has been confirmed to fix LP:#1540407
+ This version from Debian has been confirmed to fix bug 1540407
  
  The new version of the package will be tested with:
-   - MAAS driven Power8 installs on hosts with multipath configured
-  -  s390x FCP multipath devices as in LP:#1540407.
-   - kvm VM with virtio-scsi multipath
+   - MAAS driven Power8 installs on hosts with multipath configured
+  -  s390x FCP multipath devices as in bug 1540407.
+   - kvm VM with virtio-scsi multipath

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

Re: [Bug 1540407] Comment bridged from LTC Bugzilla

2016-03-01 Thread Ryan Harper

On Tue, Mar 1, 2016 at 3:00 AM, bugproxy <bugpr...@us.ibm.com> wrote:

> --- Comment From thorsten.di...@de.ibm.com 2016-03-01 03:58 EDT---
> (In reply to comment #19)
> > 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.
>
> Results show, that this combination does not harm, instead it solves the
> subject problem, even after 100 cycles.
>
> Ryan, but it's up to you what you are going to integrate to fix this
> bug.
>

Thorsten,

Thanks for the thorough testing of the scenarios.  I'm currently examining
the changes
introduced into the newer Debian package and looking at which changes we'd
need
to fix this bug and also understand if a merge of the package makes more
sense.


Ryan


>
> --
> You received this bug notification because you are a member of Canonical
> Server Team, which is a bug assignee.
> 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
>

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

Re: [Bug 1550437] Re: [BUG] Unable to install: dependency problem

2016-02-26 Thread Ryan Tandy

On Fri, Feb 26, 2016 at 07:56:59PM -, Michal Dziczkowski wrote:
>I don't have the mantioned PPA in my repositories, so how could I
>install slapd from it?

The 'apt-cache policy' output you posted does include it.

> 500 http://ppa.launchpad.net/dirk-computer42/c42-backport/ubuntu/ trusts / 
> main i386 Packages
> release v = 14.04, o = LP-PPA-dirk-computer42-c42-backport, a = trusts, n 
> = trusts, l = c42-backport, c = main
> origin ppa.launchpad.net

Not sure why that says "trusts" rather than "trusty", but that is 
definitely the version apt-get wants to install.

'apt-cache policy slapd' would tell you exactly which versions of slapd 
are available, which is going to be installed, and why.

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

Title:
  [BUG] Unable to install: dependency problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1550437/+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 1550437] Re: [BUG] Unable to install: dependency problem

2016-02-26 Thread Ryan Tandy

> Investigating (0) slapd [i386]  2.4.40-4 ~ ~ ubuntu14.04.1
c42.ppa1> (net)

This package (slapd 2.4.40-4~ubuntu14.04.1~c42.ppa1) is not part of
Ubuntu. It comes from one of the PPAs you have installed:
https://launchpad.net/~dirk-computer42/+archive/ubuntu/c42-backport

This is either a problem with that specific PPA, or an incompatibility
between some of the many PPAs you have. Either way, this is not a bug in
the slapd package in Ubuntu.

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

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

Title:
  [BUG] Unable to install: dependency problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1550437/+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 1550437] Re: [BUG] Unable to install: dependency problem

2016-02-26 Thread Ryan Tandy

Hi Michal,

Thanks for the report. Can I ask you to provide some more information?
The output from the following commands would be very helpful:

lsb_release -a

uname -a

apt-cache policy

apt-get -y install slapd

apt-get -y -o Debug::pkgProblemResolver=1 install slapd

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

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

Title:
  [BUG] Unable to install: dependency problem

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

2016-02-25 Thread Ryan Harper

Hi Thorsten,

Thanks for the update.  I'll attempt to find out if I can force a detach
on the host-side to recreate the issue on x86 while I'm waiting for a Z
system with FCP devices.

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.

-- 
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 1540407] Re: multipathd drops paths of a temporarily lost device

2016-02-24 Thread Ryan Harper

Hi Thorsten,

The latest version of the multipath-tools package is  0.5.0-7ubuntu14.
Can you confirm you're still seeing the issue?

Meanwhile, I'm hoping to recreate this issue on zKVM shortly.  In the
meantime I'm testing this on in an x86 VM with multipath via virtio-
scsi, using the same multipath.conf as mentioned in the bug.

# dpkg -s multipath-tools| grep ^Version
Version: 0.5.0-7ubuntu14

# multipath -ll
mpatha (0QEMU_QEMU_HARDDISK_0001) dm-0 QEMU,QEMU HARDDISK
size=10G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 2:0:0:0 sda 8:0  active ready running
  `- 2:0:0:1 sdb 8:16 active ready running


I can mark the device offline with:


# echo "offline" > /sys/class/block/sdb/device/state
# multipath -ll
mpatha (0QEMU_QEMU_HARDDISK_0001) dm-0 QEMU,QEMU HARDDISK
size=10G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 2:0:0:0 sda 8:0  active ready  running
  `- 2:0:0:1 sdb 8:16 active faulty offline


# sleep 60 && multipath -ll 
mpatha (0QEMU_QEMU_HARDDISK_0001) dm-0 QEMU,QEMU HARDDISK
size=10G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 2:0:0:0 sda 8:0  active ready  running
  `- 2:0:0:1 sdb 8:16 failed faulty offline

And bring it back online with:

# echo "1" > /sys/block/sdb/device/delete
# for RESCAN in /sys/class/scsi_host/*; do echo "- - -" > $RESCAN/scan; done 
# multipath -v2 
# multipath -ll
mpatha (0QEMU_QEMU_HARDDISK_0001) dm-0 QEMU,QEMU HARDDISK
size=10G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 2:0:0:0 sda 8:0  active ready running
  `- 2:0:0:1 sdb 8:16 active ready running

It maybe that the underlying device would need to be in error instead of the 
scsi layer in the kernel.
I'll update this when I get the zKVM instance up with multipath as described in 
the bug.

Looking at the delta between 0.5.0 in Ubuntu and the newer version in
Debian, there are a number of changes in the area of discovery and path
checking which may resolve this issue if we can confirm we're still
seeing the issue on the latest version in Xenial.

-- 
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 1545821] Re: Regression: spice usbredirect causes windows client to crash

2016-02-23 Thread Ryan

Excellent -- However, ATM I'm away on business and I won't be able to
try this until next week.

I'll report my findings then.

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

Title:
  Regression: spice usbredirect causes windows client to crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1545821/+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 1518440] Re: tgt fails to install in LXD

2016-02-22 Thread Ryan Harper

This fix has been released in Xenial, as tgt 1:1.0.62-1ubuntu2

** Changed in: tgt (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: tgt (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)

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

Title:
  tgt fails to install in LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1518440/+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 1545821] Re: Regression: spice usbredirect causes windows client to crash

2016-02-19 Thread Ryan

I'm certainly willing to try, but I cannot find the debian qemu binaries
for version 2.0.0+dfsg-2ubuntu1.21 (I only have 2.0.0+dfsg-2ubuntu1.19
cached locally).

Are these packages mirrored somewhere?

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

Title:
  Regression: spice usbredirect causes windows client to crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1545821/+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 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

** Patch added: "debdiff netween debian 5.3.5-1 and ubuntu 5.3.5-1ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+attachment/4573963/+files/debian-5.3.5-1-to-5.3.5-1ubuntu1.debdiff

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+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 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

** Patch added: "Ubuntu debdiff between 5.1.2-0ubuntu8 and 5.3.5-1ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+attachment/4573962/+files/ubuntu-5.1.2-0ubuntu8-to-5.3.5-1ubuntu1.debdiff

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+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 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

I've pushed the latest revisions into the PPA:

strongswan (5.3.5-1ubuntu7) xenial; urgency=medium

  * debian/{rules,control,libstrongswan-extra-plugins.install}
Enable bliss plugin
  * debian/patches/increase-bliss-test-timeout.patch
Under QEMU/KVM for autopkgtest bliss test takes a bit longer
  * debian/patches/dont-load-kernel-libipsec-plugin-by-default.patch
Upstream suggests to not load this plugin by default as it has
some limitations.
https://wiki.strongswan.org/projects/strongswan/wiki/Kernel-libipsec

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+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 1511735] Re: libnl: fail to bind() netlink sockets

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

2016-02-16 Thread Ryan Harper

I've done some more verification tests by installing as many of the
reverse depends on libnl to see if any other package implodes like
Network-Manager did.

Sniff Check OK: Tested by install and invoke binaries.
batctl 
bmon 
ipvsadm 
keepalived 
libfsobasics3 
libnetcf1 
libnl-3-200-dbg 
libnl-3-dev 
libnl-cli-3-200 
libnl-genl-3-200 
libnl-nf-3-200 
libnl-route-3-200 
libnl-utils 
libnss-gw-name 
libvirt-bin 
libvirt0 
network-manager (with what's in proposed)
powertop 
quota 

SKIPPED: Packages that depended on wireless devices for testing 
crda 
hostapd 
iw 
kismet 
knemo 
lowpan-test-tools 
lowpan-tools 
neard 
neard-tools 
ntrack-module-libnl-0 
plainbox-provider-resource-generic 
sssd-common
wpasupplicant


** Changed in: libnl3 (Ubuntu Trusty)
 Assignee: Ryan Harper (raharper) => (unassigned)

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

Title:
  libnl: fail to bind() netlink sockets

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

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

Re: [Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

2016-02-16 Thread Ryan Harper

On Tue, Feb 16, 2016 at 8:46 AM, mrq1  wrote:

> it looks like strongswan is faking a nat situation if the  kernel-libipsec
> is used, so there are only problems with transport & beet mode ..
>

It sounds like it could be confusing.  I'd prefer not to have a one-off for
just this
package but if it's disruptive then it's likely warranted.


> btw: did you get this audit entries too?
>

No.  Are you running 1ubuntu6 and have you reloaded the apparmor profile
and restarted strongswan?

sudo apparmor_parser -r /etc/apparmor.d/usr.lib.ipsec.charon
sudo systemctl restart strongswan

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

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

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

Re: [Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

2016-02-15 Thread Ryan Harper

On Sun, Feb 14, 2016 at 3:36 AM, mrq1  wrote:

> looks good so far :-)
>
> i think the kernel-libipsec plugin should not be loaded by default
>
> the plugin works only with  UDP encapsulated packets
>
> (look here: https://wiki.strongswan.org/projects/strongswan/wiki/Kernel-
> libipsec)
>
> and this will break most of the "normal"/LAN setups
>

The kernel-libipsec plugin is optional; a user must apt-get install
libstrongswan-extra-plugins.
I've installed the extra plugins in a VM which uses NAT configuration and
none of the
networking was broken if the kernel-libipsec module was loaded (but
unconfigured).

However, I'm interested if you can expand on what setup would break?  We
certainly don't want
break or surprise users so I'd like understand what "breaks" if the module
is loaded by default.

>
> i would build and include the plugin but disable the loading with
>
> /etc/strongswan.d/charon/kernel-libipsec.conf
> > load = no
>

This would be a change compared to all other plugins so I'd like to
understand why
this plugin in the default configuration breaks any normal/LAN setups.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535951
>
> Title:
>   Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+subscriptions
>

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+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 1545821] [NEW] Regression: spice usbredirect causes windows client to crash

2016-02-15 Thread Ryan

Public bug reported:

I have been using Ubuntu 14.04.3 as the host OS for a series of Windows
based VM clients (Windows XP SP3 32-bit and Windows 10 Pro - 64bit) and
using 'spice-client-gtk' to proxy a usb device (a webcam).  Everything
is fine if I use:

hi  qemu-keymaps  2.0.0+dfsg-2ubuntu1.19
  all  QEMU keyboard maps
hi  qemu-kvm  2.0.0+dfsg-2ubuntu1.19
  amd64QEMU Full virtualization
hi  qemu-system-common2.0.0+dfsg-2ubuntu1.19
  amd64QEMU full system emulation binaries (common files)
hi  qemu-system-x86   2.0.0+dfsg-2ubuntu1.19
  amd64QEMU full system emulation binaries (x86)
hi  qemu-utils2.0.0+dfsg-2ubuntu1.19
  amd64QEMU utilities

However, after I've upgraded to the latest stable version: 2.0.0+dfsg-
2ubuntu1.22.

* I start 'spicy'
* Connect to the remote windows guest
* Choose the webcam to export

Thus, far everything is normal (the device connects).  Once I try to use
the webcam (from either skype or chrome) - I get a brief indeicator
light from the webcam... then the Windows XP Guest blue-screens and the
Windows 10 Pro Guest hardlocks.

I get no useful information from the Host's /var/log/syslog.

I've also tried to compile the latest version of remote-viewer from
source (version 3.1).  When, it tries to connect to 2.0.0+dfsg-
2ubuntu1.22 the effect is the same, both windows guests crash.  However,
after I've downgraded to 2.0.0+dfsg-2ubuntu1.19 both 'spicy' and the
compiled remote-version v3.1 work perfectly.

I also tried upgrading the usbdk version on the windows clients to the
most recent version v1.0.12 (from http://www.spice-
space.org/download/windows/usbdk/), but it had no effect.  I also tried
a series of different webcams, the result was the same.

Here is a list of the packages that caused the error:

ii  qemu-keymaps
2.0.0+dfsg-2ubuntu1.22  all  QEMU keyboard 
maps
ii  qemu-kvm
2.0.0+dfsg-2ubuntu1.22  amd64QEMU Full 
virtualization
ii  qemu-system-common  
2.0.0+dfsg-2ubuntu1.22  amd64QEMU full 
system emulation binaries (common files)
ii  qemu-system-x86 
2.0.0+dfsg-2ubuntu1.22  amd64QEMU full 
system emulation binaries (x86)
ii  qemu-utils  
2.0.0+dfsg-2ubuntu1.22  amd64QEMU utilities

Here is the version of spicy, I've used with both 1.19 and 1.22:

ii  libspice-client-glib-2.0-8:amd64  0.22-0nocelt2 
  amd64GObject for communicating with Spice servers (runtime library)
ii  libspice-client-gtk-2.0-4:amd64   0.22-0nocelt2 
  amd64GTK2 widget for SPICE clients (runtime library)
ii  libspice-server1:amd640.12.4-0nocelt2ubuntu1.2  
  amd64Implements the server side of the SPICE protocol
ii  spice-client-glib-usb-acl-helper  0.22-0nocelt2 
  amd64Spice client glib usb acl helper
ii  spice-client-gtk  0.22-0nocelt2 
  amd64Simple clients for interacting with SPICE servers

My current work-around was to revert the qemu-* packages back to version
1.19.  I don't know at which revision this error occurred, but it was
somewhere between 1.20 and 1.22.

How to recreate the problem:
* Create a windows VM (it might also apply to other guest o/s)
* Install spice-client-gtk
* Configure the VM to use spice 
(https://people.freedesktop.org/~teuf/spice-doc/html/ch02s06.html)
* Start the VM
* Attach a webcam (or probably another other device)
* Within the VM start an application that uses the device (I'd used both Skype 
and https://www.onlinemictest.com/webcam-test-in-adobe-flash via google-chrome)

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Regression: spice usbredirect causes windows client to crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1545821/+subscriptions

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

Re: [Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

2016-02-14 Thread Ryan Harper

On Sun, Feb 14, 2016 at 2:12 AM, mrq1  wrote:

> thanks for the fast pace!
>
> > should be ready in a bit with the new plugin
>
> NOPE. still no chapoly & ntru plugin included
>

chapoly and ntru are part of libstrongswan-extra-plugins


>
> # ipsec statusall
> Status of IKE charon daemon (strongSwan 5.3.5, Linux 4.4.0-4-generic,
> x86_64):
>   uptime: 10 minutes, since Feb 14 08:59:01 2016
>   malloc: sbrk 1650688, mmap 0, used 547408, free 1103280
>   worker threads: 7 of 16 idle, 5/0/4/0 working, job queue: 0/0/0/0,
> scheduled: 0
>   loaded plugins: charon test-vectors aes rc2 sha1 sha2 md4 md5 random
> nonce x509 revocation constraints pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp
> dnskey sshkey pem openssl fips-prf gmp agent xcbc hmac gcm attr
> kernel-libipsec kernel-netlink resolve socket-default connmark farp stroke
> updown eap-identity eap-sim eap-sim-pcsc eap-aka eap-aka-3gpp2
> eap-simaka-pseudonym eap-simaka-reauth eap-md5 eap-gtc eap-mschapv2
> eap-dynamic eap-radius eap-tls eap-ttls eap-peap eap-tnc xauth-generic
> xauth-eap xauth-pam xauth-noauth tnc-tnccs tnccs-20 tnccs-11 tnccs-dynamic
> dhcp lookip error-notify certexpire led addrblock unity
>

You might need to restart after upgrade: systemctl restart strongswan

# ipsec statusall
Status of IKE charon daemon (strongSwan 5.3.5, Linux 4.4.0-4-generic,
x86_64):
  uptime: 99 seconds, since Feb 14 14:40:22 2016
  malloc: sbrk 2834432, mmap 532480, used 1004336, free 1830096
  worker threads: 7 of 16 idle, 5/0/4/0 working, job queue: 0/0/0/0,
scheduled: 0
  loaded plugins: charon test-vectors unbound ldap pkcs11 aes rc2 sha1 sha2
md4 md5 random nonce x509 revocation constraints acert pubkey pkcs1 pkcs7
pkcs8 pkcs12 pgp dnskey sshkey dnscert ipseckey pem openssl gcrypt af-alg
fips-prf gmp agent chapoly xcbc cmac hmac ctr ccm gcm ntru curl soup mysql
sqlite attr kernel-libipsec kernel-netlink resolve socket-default connmark
farp stroke updown eap-identity eap-sim eap-sim-pcsc eap-aka eap-aka-3gpp2
eap-simaka-pseudonym eap-simaka-reauth eap-md5 eap-gtc eap-mschapv2
eap-dynamic eap-radius eap-tls eap-ttls eap-peap eap-tnc xauth-generic
xauth-eap xauth-pam xauth-noauth tnc-tnccs tnccs-20 tnccs-11 tnccs-dynamic
dhcp whitelist lookip error-notify certexpire led radattr addrblock unity
Listening IP addresses:
  192.168.122.147
  10.0.3.1
Connections:
Security Associations (0 up, 0 connecting):
  none


> i installed a new virtual machine and installed the ppa-strongswan
>
> looks like it is not enough to
> # apt install libcharon-extra-plugins
> this package does not depend on
> # apt install strongswan
> which it should!
>

if you apt-get install libstrongswan-extra-plugins, this will pull in the
strongswan package.


>
> now starts the testing ;-)
>

Excellent!


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535951
>
> Title:
>   Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+subscriptions
>

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+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 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

Yes, quite close.  I'll handle the FFE if needed but I feel on-track.
I'm preparing the merge debdiff for review.

Threads:
https://lists.ubuntu.com/archives/ubuntu-devel/2016-January/039144.html
https://lists.ubuntu.com/archives/ubuntu-devel/2016-February/039201.html

Please give the test-package a go if you're a strongswan user.

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

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

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

Re: [Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

Ah, yes.  I've a fix for that;  I hadn't pushed my latest update in to the
ppa.  The extra-plugins package need some more privs for the charon binary
in the apparmor profile.

Look for 1ubuntu5 in the ppa in just a bit and see if that fixes up the
issue with the extras plugins.


On Sat, Feb 13, 2016 at 10:39 AM, mrq1  wrote:

> the startup segfault disappears if a purge the extra-plugin package but
> NOT if i only remove it :-O
>
> maybe the bug comes with one of the dependency packages?
>
> Feb 13 17:31:24 kvm-xenial charon: 00[LIB] loaded plugins: charon
> test-vectors aes rc2 sha1 sha2 md4 md5 random nonce x509 revocation
> constraints pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey pem openssl
> fips-prf gmp xcbc hmac ccm gcm attr kernel-netlink resolve socket-default
> connmark farp stroke updown eap-identity eap-sim eap-sim-pcsc eap-aka
> eap-aka-3gpp2 eap-simaka-pseudonym eap-simaka-reauth eap-md5 eap-gtc
> eap-mschapv2 eap-dynamic eap-radius eap-tls eap-ttls eap-peap eap-tnc
> xauth-generic xauth-eap xauth-noauth tnc-tnccs tnccs-20 tnccs-11
> tnccs-dynamic dhcp lookip error-notify certexpire led addrblock unity
> Feb 13 17:31:24 kvm-xenial charon: 00[LIB] dropped capabilities, running
> as uid 0, gid 0
> Feb 13 17:31:24 kvm-xenial charon: 00[JOB] spawning 16 worker threads
> Feb 13 17:31:24 kvm-xenial charon: 02[DMN] thread 2 received 11
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]  dumping 7 stack frame
> addresses:
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]
>  /lib/x86_64-linux-gnu/libpthread.so.0 @ 0x7f77069c9000 [0x7f77069d9cd0]
> Feb 13 17:31:24 kvm-xenial charon: 08[DMN] thread 8 received 11
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]  dumping 7 stack frame
> addresses:
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]
>  /lib/x86_64-linux-gnu/libpthread.so.0 @ 0x7f77069c9000 [0x7f77069d9cd0]
> Feb 13 17:31:24 kvm-xenial charon: 07[DMN] thread 7 received 11
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB]  dumping 7 stack frame
> addresses:
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB]
>  /lib/x86_64-linux-gnu/libpthread.so.0 @ 0x7f77069c9000 [0x7f77069d9cd0]
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]   /usr/lib/ipsec/libipsec.so.0
> @ 0x7f770176d000 [0x7f7701770f4b]
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]   /usr/lib/ipsec/libipsec.so.0
> @ 0x7f770176d000 [0x7f770176ffdc]
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB]   /usr/lib/ipsec/libipsec.so.0
> @ 0x7f770176d000 [0x7f7701770b5b]
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070a60c2]
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070a60c2]
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070a60c2]
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070a69fb]
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070a69fb]
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070a69fb]
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070b772c]
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070b772c]
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB]
>  /usr/lib/ipsec/libstrongswan.so.0 @ 0x7f7707079000 [0x7f77070b772c]
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]
>  /lib/x86_64-linux-gnu/libpthread.so.0 @ 0x7f77069c9000 [0x7f77069d066a]
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]
>  /lib/x86_64-linux-gnu/libpthread.so.0 @ 0x7f77069c9000 [0x7f77069d066a]
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 07[LIB]
>  /lib/x86_64-linux-gnu/libpthread.so.0 @ 0x7f77069c9000 [0x7f77069d066a]
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 02[LIB]
>  /lib/x86_64-linux-gnu/libc.so.6 @ 0x7f77065ff000 (clone+0x6d)
> [0x7f7706705e4d]
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB] ->
> Feb 13 17:31:24 kvm-xenial charon: 08[LIB]
>  /lib/x86_64-linux-gnu/libc.so.6 @ 0x7f77065ff000 (clone+0x6d)
>

Re: [Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

On Sat, Feb 13, 2016 at 12:27 PM, mrq1  wrote:

> great! starts now :-)
>
> what about the chapoly plugin? can you enable it in the extra package?
> it would be very important for me!
>

I can look at enabling it.  It's new in 5.3.5.  If enabled, can you test
and confirm it works?
Looks like something quite interesting.
https://en.wikipedia.org/wiki/Poly1305

Comments here in the Debian bug indicate that this requires at least 4.2
kernel.
For Xenial, this will be sufficient I suppose.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803787


>
> btw: the output of service looks strange to me
>
> # service strongswan status
> ● strongswan.service - strongSwan IPsec services
>Loaded: loaded (/lib/systemd/system/strongswan.service; enabled; vendor
> preset: enabled)
>Active: inactive (dead) since Sat 2016-02-13 19:22:46 CET; 42s ago
>   Process: 25807 ExecStopPost=/bin/rm -f /var/run/charon.pid
> /var/run/starter.charon.pid (code=exited, status=0/SUCCESS)
>   Process: 25789 ExecStop=/usr/sbin/ipsec stop (code=exited,
> status=0/SUCCESS)
>  Main PID: 25643 (code=exited, status=0/SUCCESS)
>

That looks like from the initial install;  You may need to reload the new
apparmor policy

apparmor_parser -r /etc/apparmor.d/usr.lib.ipsec.charon

And then you can restart it with:

systemctl restart strongswan

and check status

systemctl status strongswan


>
> looks like the service is not running anymore but via
> # ipsec statusall
> everything looks ok
>
> is the some systemd-integration-magic missing?
>

I'm not sure what ipsec statusall invokes to check status.

In an up-to-date Xenial VM, installing the current packages in the PPA, I
get the following:

# systemctl status strongswan
● strongswan.service - strongSwan IPsec services
   Loaded: loaded (/lib/systemd/system/strongswan.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sat 2016-02-13 21:50:59 UTC; 18s ago
 Main PID: 2798 (starter)
   CGroup: /system.slice/strongswan.service
   ├─2798 /usr/lib/ipsec/starter --daemon charon
   └─2799 /usr/lib/ipsec/charon --use-syslog

Feb 13 21:50:59 sw1 charon[2799]: 00[CFG] loading ocsp signer certificates
from '/...ts'
Feb 13 21:50:59 sw1 charon[2799]: 00[CFG] loading attribute certificates
from '/et...ts'
Feb 13 21:50:59 sw1 charon[2799]: 00[CFG] loading crls from
'/etc/ipsec.d/crls'
Feb 13 21:50:59 sw1 charon[2799]: 00[CFG] loading secrets from
'/etc/ipsec.secrets'
Feb 13 21:50:59 sw1 charon[2799]: 00[LIB] loaded plugins: charon
test-vectors aes ...own
Feb 13 21:50:59 sw1 charon[2799]: 00[LIB] dropped capabilities, running as
uid 0, gid 0
Feb 13 21:50:59 sw1 charon[2799]: 00[JOB] spawning 16 worker threads
Feb 13 21:50:59 sw1 ipsec_starter[2798]: charon (2799) started after 20 ms
Feb 13 21:50:59 sw1 systemd[1]: Started strongSwan IPsec services.
Feb 13 21:51:00 sw1 systemd[1]: Started strongSwan IPsec services.
Hint: Some lines were ellipsized, use -l to show in full.
root@sw1:~#
root@sw1:~# ipsec statusall
Status of IKE charon daemon (strongSwan 5.3.5, Linux 4.4.0-4-generic,
x86_64):
  uptime: 30 seconds, since Feb 13 21:51:00 2016
  malloc: sbrk 946176, mmap 0, used 229008, free 717168
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0,
scheduled: 0
  loaded plugins: charon test-vectors aes rc2 sha1 sha2 md4 md5 random
nonce x509 revocation constraints pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp
dnskey sshkey pem fips-prf gmp xcbc hmac attr kernel-netlink resolve
socket-default stroke updown
Listening IP addresses:
  192.168.122.147
  10.0.3.1
Connections:
Security Associations (0 up, 0 connecting):
  none


>
> thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535951
>
> Title:
>   Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+subscriptions
>

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+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 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

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

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

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

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

Re: [Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

On Sat, Feb 13, 2016 at 7:51 PM, Simon Déziel <1535...@bugs.launchpad.net>
wrote:

> On 2016-02-13 05:09 PM, Ryan Harper wrote:
> > On Sat, Feb 13, 2016 at 12:27 PM, mrq1 <tempusfugit...@gmail.com> wrote:
> >
> >> great! starts now :-)
> >>
> >> what about the chapoly plugin? can you enable it in the extra package?
> >> it would be very important for me!
> >>
> >
> > I can look at enabling it.  It's new in 5.3.5.
>
> +1
>
> ChaCha20/Poly1305 actually made it in 5.3.3 [1] and I haven't heard of
> any problem on the mailing list.
>
> >  If enabled, can you test and confirm it works?
>
> I too would be glad to give it a spin and report about it.
>
> > Looks like something quite interesting.
> > https://en.wikipedia.org/wiki/Poly1305
>
> Indeed! Chacha20 and Poly1305 are cool and getting quite some traction
> these days [2].
>

Excellent!  I've just uploaded a new version to the PPA; should be ready in
a bit with the new plugin
and updated apparmor profiles from your repo.

One question, the profile included /dev/tun, and in my Xenial setups, I
need
/dev/net/tun so I've both allowed in the profile. Not clear to me if it's
useful/needed
to have both, or if only one is sufficient.


> > Comments here in the Debian bug indicate that this requires at least 4.2
> > kernel.
>
> For the IKE part, the kernel version shouldn't matter. For the ESP part,
> you indeed need a recent kernel or you can always use the userspace
> implementation (libipsec).
>
>
OK


> libipsec support is very cool (thanks for enabling it!) as it should
> allow running a IPsec in containers.
>
>
Please do confirm if that's working.  I suspect they'll need to be
privileged containers
or will need some additional permissions/configs for unprivileged since
it'll want access to
/dev/net/tun which won't be present by default.

I'd like to capture how to run strongswan in containers like LXD so if
you've any experience
with getting that working it'd be very helpful for us to document.


> > For Xenial, this will be sufficient I suppose.
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803787
>
> The reporter was looking for NTRU (enabled in your PPA build IIRC) and
>

Yes


> BLISS. That said, I'm sure the reporter would welcome having another
> AEAD cipher available because they are well regarded [3] in terms of
> security.
>
> Thanks,
> Simon
>
> 1: https://wiki.strongswan.org/versions/58
> 2:
>
> https://en.wikipedia.org/w/index.php?title=Salsa20=no#ChaCha20_adoption
> 3: https://www.imperialviolet.org/2015/05/16/aeads.html
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535951
>
> Title:
>   Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+subscriptions
>

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

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

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

Re: [Bug 1535951] Re: Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

Excellent!  I had forgotten about that.  I'll update.

On Sat, Feb 13, 2016 at 7:00 PM, Simon Déziel <1535...@bugs.launchpad.net>
wrote:

> On 2016-02-13 12:39 PM, Ryan Harper wrote:
> > The extra-plugins package need some more privs for the charon binary
> > in the apparmor profile.
>
> Ryan, please take a look at [1] for refreshed AA profiles that could
> address many more LP bugs (all mentioned in debian/changelog). Thanks.
>
> Regards,
> Simon
>
> 1:
>
> https://github.com/simondeziel/ubuntu-strongswan/commit/9f414ee4e04d6d88810c85029cc0dcbaed58fba8
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535951
>
> Title:
>   Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+subscriptions
>

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

Title:
  Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+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 1511735] Re: libnl: fail to bind() netlink sockets

2016-02-04 Thread Ryan Harper

v3 debdiff
  - Removed unneeded spaces in debian/control Breaks entry
  - Fixed up libnl-3-200.symbols file to tag private symbols as optional 
(removes dpkg-gensymbols warning)
  - Removed invalid use of Closes() for Debian bugs;  instead use LP: #

** Patch added: "lp_1511735_libnl3_v3.diff"
   
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+attachment/4563661/+files/lp_1511735_libnl3_v3.diff

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

2016-02-03 Thread Ryan Harper

I've updated the debdiff to include a Breaks:  network-manager (<<
0.9.8.8-0ubuntu7.3) to ensure that users are forced to use the newer
network-manager (ie, this libnl won't install unless user has already
updated their network-manager)   Thanks Mathew for the suggestion.

I've built and tested this in the following way:

1. deploy trusty 14.04
2. apt-get install network-manager
3. download the libnl3 packages (3.2.21-1ubuntu2)
4. dpkg --install libnl-3-200_3.2.21-1ubuntu2_amd64.deb 
libnl-genl-3-200_3.2.21-1ubuntu2_amd64.deb 
libnl-route-3-200_3.2.21-1ubuntu2_amd64.deb 

This results in the following (successful blocking of upgrade):

dpkg: regarding libnl-3-200_3.2.21-1ubuntu2_amd64.deb containing 
libnl-3-200:amd64:
 libnl-3-200:amd64 breaks network-manager (<< 0.9.8.8-0ubuntu7.3)
  network-manager (version 0.9.8.8-0ubuntu7.2) is present and installed.

dpkg: error processing archive libnl-3-200_3.2.21-1ubuntu2_amd64.deb 
(--install):
 installing libnl-3-200:amd64 would break network-manager, and
 deconfiguration is not permitted (--auto-deconfigure might help)
(Reading database ... 37060 files and directories currently installed.)
Preparing to unpack libnl-genl-3-200_3.2.21-1ubuntu2_amd64.deb ...
Unpacking libnl-genl-3-200:amd64 (3.2.21-1ubuntu2) over (3.2.21-1) ...
Preparing to unpack libnl-route-3-200_3.2.21-1ubuntu2_amd64.deb ...
Unpacking libnl-route-3-200:amd64 (3.2.21-1ubuntu2) over (3.2.21-1) ...
dpkg: dependency problems prevent configuration of libnl-genl-3-200:amd64:
 libnl-genl-3-200:amd64 depends on libnl-3-200 (= 3.2.21-1ubuntu2); however:
  Version of libnl-3-200:amd64 on system is 3.2.21-1.

dpkg: error processing package libnl-genl-3-200:amd64 (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnl-route-3-200:amd64:
 libnl-route-3-200:amd64 depends on libnl-3-200 (= 3.2.21-1ubuntu2); however:
  Version of libnl-3-200:amd64 on system is 3.2.21-1.

dpkg: error processing package libnl-route-3-200:amd64 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libnl-3-200_3.2.21-1ubuntu2_amd64.deb
 libnl-genl-3-200:amd64
 libnl-route-3-200:amd64


After installing network-manager 0.9.8.8-0ubuntu7.3, I can successfully re-run 
the libnl3 install command:

dpkg --install libnl-3-200_3.2.21-1ubuntu2_amd64.deb 
libnl-genl-3-200_3.2.21-1ubuntu2_amd64.deb 
libnl-route-3-200_3.2.21-1ubuntu2_amd64.deb 
(Reading database ... 41021 files and directories currently installed.)
Preparing to unpack libnl-3-200_3.2.21-1ubuntu2_amd64.deb ...
Unpacking libnl-3-200:amd64 (3.2.21-1ubuntu2) over (3.2.21-1) ...
Selecting previously unselected package libnl-genl-3-200:amd64.
Preparing to unpack libnl-genl-3-200_3.2.21-1ubuntu2_amd64.deb ...
Unpacking libnl-genl-3-200:amd64 (3.2.21-1ubuntu2) ...
Selecting previously unselected package libnl-route-3-200:amd64.
Preparing to unpack libnl-route-3-200_3.2.21-1ubuntu2_amd64.deb ...
Unpacking libnl-route-3-200:amd64 (3.2.21-1ubuntu2) ...
Setting up libnl-3-200:amd64 (3.2.21-1ubuntu2) ...
Setting up libnl-genl-3-200:amd64 (3.2.21-1ubuntu2) ...
Setting up libnl-route-3-200:amd64 (3.2.21-1ubuntu2) ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...


** Patch added: "lp_1511735_libnl3_v2.diff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/libnl3/+bug/1511735/+attachment/4563004/+files/lp_1511735_libnl3_v2.diff

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1539513] Re: networkmanager segfaults with 3.2.21-1ubuntu1

2016-02-02 Thread Ryan Harper

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

** This bug has been marked a duplicate of bug 1539634
   network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

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

Title:
  networkmanager segfaults with 3.2.21-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1539513/+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 1511735] Re: libnl: fail to bind() netlink sockets

2016-02-02 Thread Ryan Harper

I've retagged this as verification-needed since we've had one regression
(NetworkManager, a bug there) and we'd like to request other users of
libnl to test out the version included in proposed so we can ensure
we're flushing out other applications that may be exposed due to the
behavior changed in this update.

** Tags removed: verification-failed
** Tags added: verification-needed

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

2016-02-02 Thread Ryan Harper

This has not been released;  this version is only available in trusty-
proposed.  It's not been verified at this point.

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

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1518440] Re: tgt fails to install in LXD

Forwarded patch to upstream via: https://github.com/fujita/tgt/pull/17

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

Title:
  tgt fails to install in LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1518440/+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 1518440] Re: tgt fails to install in LXD

Updated debdiff:
  - Fix spelling of attempt
  - replace spaces with tabs in patch.

** Patch added: "tgt_fix_lp1518440_v3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1518440/+attachment/4560974/+files/tgt_fix_lp1518440_v3.debdiff

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

Title:
  tgt fails to install in LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1518440/+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 1518440] Re: tgt fails to install in LXD

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

** Also affects: tgt (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813368
   Importance: Unknown
   Status: Unknown

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

Title:
  tgt fails to install in LXD

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

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

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

Blueprint changed by Ryan Harper:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
+ [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
- [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
- [nacc] logwatch merge and cleanup: INPROGRESS
+ [kick-d] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
+ [nacc] logwatch cleanup: TODO
  [smoser] openiscsi merge: TODO
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [wesley-wiedenmeier] dovecot merge (doko: done in wily, update to 2.2.2x 
would be good): TODO
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  
  Work items for ubuntu-16.03:
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  puppet merge and cleanup: TODO
  [paelzer] DPDK MIR: INPROGRESS
  [paelzer] DPDK upstream work: TODO
- [rharper] Tomcat updates and cleanup (=14days): TODO
+ [nacc] Tomcat updates and cleanup (=14days): TODO
  Java-related work (=10days): TODO
  mail-stack-delivery deprecation plan: TODO
  [racb] squid3 merge (=4days): TODO
  [louis-bouchard] nut merge: DONE
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  Consider postfix update: TODO
+ [raharper] docker.io: INPROGRESS

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

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

[Bug 1511735] Re: libnl: fail to bind() netlink sockets

Thanks Nicolas.  I'm working on fixing up NetworkManager;  we'll need
that fix as well to go out at the sametime.

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

Hi Jakub,

Thanks for testing the new package.  It would be helpful to collect any
core files and backtraces.

apport-collect -p network-manager 1511735

Should collect the info for this bug report.

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

I've filed 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634 to track 
the updated needed there.
I attached a debdeff in the NM bug after applying the patches from comment #24. 
 

I tested the updated NM with proposed libnl-3 and it works as expected.

1. Download 14.04.03 Desktop iso, amd64
2. Launched in a VM, run from iso
3. In terminal, enable proposed
4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
5. sudo restart network-manager
# note the nm-applet disappears as NM has now crashed
6. dmesg to confirm network-manager crash
7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
8. sudo start network-manager
# nm-applet restored, network connectivity restored.

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

** Tags removed: verification-done
** Tags added: verification-failed

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

Looks like the changes in libnl exposed a bug in the N-M 0.98 code:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1539513] Re: networkmanager segfaults with 3.2.21-1ubuntu1

This bug is related to an attempted SRU for libnl here:

https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735

The updated package exposes a bug in NetworkManager, which we're testing
a fix:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634

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

Title:
  networkmanager segfaults with 3.2.21-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1539513/+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 1511735] Re: libnl: fail to bind() netlink sockets

Hi Nick,

We've not built a new NetworkManager package with the fix.  For now,
you'll need to downgrade your libnl-3 packages:

% apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-
route-3-200=3.2.21-1

And you may need to apply a hold until a fix for NetworkManager can be
released.

% sudo apt-mark hold libnl-3-200 libnl-genl-3-200 libnl-route-3-200

And after the fix:

% sudo apt-mark auto libnl-3-200 libnl-genl-3-200 libnl-route-3-200

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1511735] Re: libnl: fail to bind() netlink sockets

2016-01-27 Thread Ryan Harper

Nicolas,

Thanks for the ping.  I'm looking for a sponsor to review the update.
If approved, then it'll get uploaded and continue through the SRU
process.

Thanks again for following up on this.

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

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1536301] Re: package libldap-2.4-2 2.4.41+dfsg-1ubuntu3 [modified: usr/share/doc/libldap-2.4-2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libldap-2

Sounds like a case of multi-arch skew. If I'm reading correctly, you had
libldap-2.4-2 2.4.41+dfsg-1ubuntu2 installed for both i386 and amd64;
but then you tried to upgrade to -1ubuntu3 on i386 only.

Updating your system should resolve this, I think.

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

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

Title:
  package libldap-2.4-2 2.4.41+dfsg-1ubuntu3 [modified:
  usr/share/doc/libldap-2.4-2/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libldap-2.4-2/changelog.Debian.gz', which is different
  from other instances of package libldap-2.4-2:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1536301/+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 1537762] Re: syncrepl does not work when using tls

Hi Ian,

I found https://stathers.net/2016/01/14/thawte-premium-ssl-
md5-gnutls.html but it would be surprising if that broke syncrepl but
not ldapsearch. Still, worth checking if you haven't already.
(ldapsearch and syncrepl are using the same CA certificate, right?)

Is there any interesting output if you run the consumer slapd at a
higher debug level?

Separate from slapd, are gnutls-serv/gnutls-cli able to communicate
using the same certificates?

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

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

Title:
  syncrepl does not work when using tls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1537762/+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 1537762] Re: syncrepl does not work when using tls

Please also have a look at
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1534230 (thanks
to sarnold for the pointer)

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

Title:
  syncrepl does not work when using tls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1537762/+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 874339] Re: package slapd 2.4.23-6ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** This bug has been marked a duplicate of bug 1040177
   slapd install fails when requesting to 'Omit OpenLDAP server configuration"

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

Title:
  package slapd 2.4.23-6ubuntu6 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/openldap/+bug/874339/+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 694707] Re: database doesn't get purged during purge