[Ubuntu-ha] [Bug 1644530] Update Released

2017-03-30 Thread Steve Langasek 
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1644530

Title:
  keepalived fails to restart cleanly due to the wrong systemd settings

Status in keepalived package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in keepalived source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in keepalived package in Debian:
  New

Bug description:
  [Impact]

   * Restarts of keepalived can leave stale processes with the old
  configuration around.

   * The systemd detection of the MainPID is suboptimal, and combined
  with not waiting on signals being handled it can fail on second
  restart killing the (still) remaining process of the first start.

   * Upstream has a PIDFile statement, this has proven to avoid the
  issue in the MainPID guessing code of systemd.

  [Test Case]

   * Set up keepalived, the more complex the config is the "bigger" is the 
reace window, below in the description is a trivial sample config that works 
well.
   
   * As a test run the loop restarting the service head-to-head while staying 
under the max-restart limit
  $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo 
systemctl restart keepalived; sudo systemctl status keepalived | egrep 
'Main.*exited'; done; done

   Expectation: no output other than timing
   Without fix: sometimes MainPIDs do no more exist, in these cases the child 
processes are the "old" ones from last execution with the old config.

  [Regression Potential]

   * Low because
 * A PIDFile statement is recommended by systemd for type=forking services 
anyway.
 * Upstream keepalived has this statement in their service file
 * By the kind of change, it should have no functional impact to other 
parts of the service other than for the PID detection of the job by Systemd.

   * Yet regression potential is never zero. There might be the unlikely
  case, which were considered working before due to a new config not
  properly being picked up. After the fix they will behave correctly and
  might show up as false-positives then if e.g. config was bad.

  [Other Info]
   
   * Usually a fix has to be in at least the latest Development release before 
SRUing it. But as I outlined below in later Releases than Xenial systemd seems 
to have improved making this change not-required. We haven't identified the 
bits for this (there is a bug task here), and they might as well be very 
complex. I think it is correct to fix Xenial in this regard with the simple 
change to the service file for now.

   * To eventually match I created a Debian bug task to ask them for the
  inclusion of the PIDFile so it can slowly tickle back down to newer
  Ubuntu Releases - also there more often people run backports where the
  issue might occur on older systemd versions (just as it does for us on
  Xenial)

  ---

  Because "PIDFile=" directive is missing in the systemd unit file,
  keepalived sometimes fails to kill all old processes. The old
  processes remain with old settings and cause unexpected behaviors. The
  detail of this bug is described in this ticket in upstream:
  https://github.com/acassen/keepalived/issues/443.

  The official systemd unit file is available since version 1.2.24 by
  this commit:

  
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15

  This includes "PIDFile" directive correctly:

  PIDFile=/var/run/keepalived.pid

  We should go the same way.

  I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.

  Package: keepalived
  Version: 1.2.19-1

  ===

  How to reproduce:

  I used the two instances of Ubuntu 16.04.2 on DigitalOcean:

  Configurations
  --

  MASTER server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state BACKUP
  priority 100

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    chk_nothing
  }
    }

  BACKUP server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state MASTER
  priority 200

  virtual_router_id 123
  unicast_src_ip

[Ubuntu-ha] [Bug 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings

2017-03-30 Thread Launchpad Bug Tracker 
This bug was fixed in the package keepalived - 1:1.2.19-1ubuntu0.2

---
keepalived (1:1.2.19-1ubuntu0.2) xenial; urgency=medium

  * Add PIDFile to avoid misdetection of MainPID on restart (LP:
#1644530).

 -- Christian Ehrhardt   Mon, 13 Mar
2017 13:23:47 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1644530

Title:
  keepalived fails to restart cleanly due to the wrong systemd settings

Status in keepalived package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in keepalived source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in keepalived package in Debian:
  New

Bug description:
  [Impact]

   * Restarts of keepalived can leave stale processes with the old
  configuration around.

   * The systemd detection of the MainPID is suboptimal, and combined
  with not waiting on signals being handled it can fail on second
  restart killing the (still) remaining process of the first start.

   * Upstream has a PIDFile statement, this has proven to avoid the
  issue in the MainPID guessing code of systemd.

  [Test Case]

   * Set up keepalived, the more complex the config is the "bigger" is the 
reace window, below in the description is a trivial sample config that works 
well.
   
   * As a test run the loop restarting the service head-to-head while staying 
under the max-restart limit
  $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo 
systemctl restart keepalived; sudo systemctl status keepalived | egrep 
'Main.*exited'; done; done

   Expectation: no output other than timing
   Without fix: sometimes MainPIDs do no more exist, in these cases the child 
processes are the "old" ones from last execution with the old config.

  [Regression Potential]

   * Low because
 * A PIDFile statement is recommended by systemd for type=forking services 
anyway.
 * Upstream keepalived has this statement in their service file
 * By the kind of change, it should have no functional impact to other 
parts of the service other than for the PID detection of the job by Systemd.

   * Yet regression potential is never zero. There might be the unlikely
  case, which were considered working before due to a new config not
  properly being picked up. After the fix they will behave correctly and
  might show up as false-positives then if e.g. config was bad.

  [Other Info]
   
   * Usually a fix has to be in at least the latest Development release before 
SRUing it. But as I outlined below in later Releases than Xenial systemd seems 
to have improved making this change not-required. We haven't identified the 
bits for this (there is a bug task here), and they might as well be very 
complex. I think it is correct to fix Xenial in this regard with the simple 
change to the service file for now.

   * To eventually match I created a Debian bug task to ask them for the
  inclusion of the PIDFile so it can slowly tickle back down to newer
  Ubuntu Releases - also there more often people run backports where the
  issue might occur on older systemd versions (just as it does for us on
  Xenial)

  ---

  Because "PIDFile=" directive is missing in the systemd unit file,
  keepalived sometimes fails to kill all old processes. The old
  processes remain with old settings and cause unexpected behaviors. The
  detail of this bug is described in this ticket in upstream:
  https://github.com/acassen/keepalived/issues/443.

  The official systemd unit file is available since version 1.2.24 by
  this commit:

  
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15

  This includes "PIDFile" directive correctly:

  PIDFile=/var/run/keepalived.pid

  We should go the same way.

  I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.

  Package: keepalived
  Version: 1.2.19-1

  ===

  How to reproduce:

  I used the two instances of Ubuntu 16.04.2 on DigitalOcean:

  Configurations
  --

  MASTER server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state BACKUP
  priority 100

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    chk_nothing
  }
    }

  BACKUP server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state MASTER
  priority 200

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    

[Ubuntu-ha] [Bug 1677879] [NEW] Missing dep8 tests

2017-03-30 Thread Joshua Powers 
Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source keepalived zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/keepalived
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3YFoAAoJEIP8BxPaZgwlUXwP/AokfL3WQ3xsVBjQMdJsUH6X
8T9M27FgQyH5PVFCrtYi52yAcqCfx8UoNMuXqKJpbmcQDpdlmz4hWvnq0RXPdHAn
IDIGE8PjSmcOJFAP+OgRiviIJ4QQAaV1M1E38aF6dDRo0JBvnVDuo8DL7d4xI2Og
VQyaaow16OnlKJIReHnoWkGU0kjK+0/Vfix/80tmiU1nsPyeo8jrcFOxJWwy4JRu
h99Ap71aBOuRLu3nMilJENqqwM8qt4LKo52cdheVwxbLwyyMNJCRAoRWRBj9/imD
U6+1P6xjPeoyMkjvCbDCdyY7hCpz1N0Hdr2ZgY64ZO3POrC5EOHAwyHVe0PvRo6C
K6woImGctsFhM/1I0T9g++JgzPY2VaZoTiJv+SvLBlJxv4+iShwHacAYO90epSVY
CKCmiRlUorbag870p/1OGCNYGHc74fST5XAov2eKBDHpREHGmXu3uT/H23dy0kKS
kbviv5dySfYLDq3ZSgKE7MY3yE+c9porXBjpdKbG2JxTBE/Qvy0rK9adFLDJ9ZLM
BAnFsfJyMhYiBhb+WzKyIaUJqQcg5VTeg1yboVs1E+gsc7qtYPtx+BEeKBC8Kdqs
n0aPq70mvYBxI9KVB3V/isS4b3O75nf3JRgSwibuNpRa5FeOvwrn6Cc4FpVQZ7mk
dEDa3tDf28QHUHWZqXNO
=b9rK
-END PGP SIGNATURE-

** Affects: keepalived (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1677879

Title:
  Missing dep8 tests

Status in keepalived package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source keepalived zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/keepalived
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3YFoAAoJEIP8BxPaZgwlUXwP/AokfL3WQ3xsVBjQMdJsUH6X
  8T9M27FgQyH5PVFCrtYi52yAcqCfx8UoNMuXqKJpbmcQDpdlmz4hWvnq0RXPdHAn
  IDIGE8PjSmcOJFAP+OgRiviIJ4QQAaV1M1E38aF6dDRo0JBvnVDuo8DL7d4xI2Og
  VQyaaow16OnlKJIReHnoWkGU0kjK+0/Vfix/80tmiU1nsPyeo8jrcFOxJWwy4JRu
  h99Ap71aBOuRLu3nMilJENqqwM8qt4LKo52cdheVwxbLwyyMNJCRAoRWRBj9/imD
  U6+1P6xjPeoyMkjvCbDCdyY7hCpz1N0Hdr2ZgY64ZO3POrC5EOHAwyHVe0PvRo6C
  K6woImGctsFhM/1I0T9g++JgzPY2VaZoTiJv+SvLBlJxv4+iShwHacAYO90epSVY
  CKCmiRlUorbag870p/1OGCNYGHc74fST5XAov2eKBDHpREHGmXu3uT/H23dy0kKS
  kbviv5dySfYLDq3ZSgKE7MY3yE+c9porXBjpdKbG2JxTBE/Qvy0rK9adFLDJ9ZLM
  BAnFsfJyMhYiBhb+WzKyIaUJqQcg5VTeg1yboVs1E+gsc7qtYPtx+BEeKBC8Kdqs
  n0aPq70mvYBxI9KVB3V/isS4b3O75nf3JRgSwibuNpRa5FeOvwrn6Cc4FpVQZ7mk
  dEDa3tDf28QHUHWZqXNO
  =b9rK
  -END PGP SIGNATURE-

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

___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-ha] [Bug 1677873] [NEW] Missing dep8 tests

2017-03-30 Thread Joshua Powers 
Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source ipvsadm zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/ipvsadm
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3YDdAAoJEIP8BxPaZgwlfF8P/07h38PjwhLxOKmcB6NXhk2/
5MCTN5oV2ju3683J17zQ9/pRO6PZkSC78bCTWvpg7/KfUQNgDtLpie+HHsKOGjze
NvBG/SbkZP3ckq306JiuQKveSLRYM5T+WbwpOxa1srWX6zsdCcTHTldTJu8xBy6y
pIfxJE3wqgniB0lcBNzH7ko5hyHNgG1CjsAZXXBf/fBCN7eLvqY/AqTYpAr/IbN+
mhoj4ckWck6kaMD+x9YrioeS1Bbbw+DOLKYhHJ0RrOtfomp93A6+YSVQ5l5hQlOh
sWcGC1NxSq/Y3Rn0xUwKQltkeHWE6hXxqU3tMN+Fekvd0Bo+1h4trRK9mPcedcoR
RkMXVHktn+c8ezfvskyvoPzal/muHAlWTjQZLVmJkrhxR+8oVgAz4U2PlBU3TOov
g2z4YjTjVw10YYWFk94ePaUBkNUg2LWZY45QhXeGyPwdpZX9bGtFX3jO1JSqSAmn
OJfBAjsLZZo+JeQssQCydy0EKxyoaGUBnWkqckqBeMfDIA4YbJV2NvqGGvmnftsV
S65dE5/LabFZoJumGszeXLGLJP0XML/hSdcnmhtvUcoD1T/BQ/BWVHyJIIsVp61p
shxyBEjWWyzM39PSIwdjTEH74y55QVRB4h4QBNCve8WuKXvzKu+mSSfABfz2x2Gw
BNJUF4RItN7x9TYLoSzj
=wEdz
-END PGP SIGNATURE-

** Affects: ipvsadm (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ipvsadm in Ubuntu.
https://bugs.launchpad.net/bugs/1677873

Title:
  Missing dep8 tests

Status in ipvsadm package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source ipvsadm zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/ipvsadm
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3YDdAAoJEIP8BxPaZgwlfF8P/07h38PjwhLxOKmcB6NXhk2/
  5MCTN5oV2ju3683J17zQ9/pRO6PZkSC78bCTWvpg7/KfUQNgDtLpie+HHsKOGjze
  NvBG/SbkZP3ckq306JiuQKveSLRYM5T+WbwpOxa1srWX6zsdCcTHTldTJu8xBy6y
  pIfxJE3wqgniB0lcBNzH7ko5hyHNgG1CjsAZXXBf/fBCN7eLvqY/AqTYpAr/IbN+
  mhoj4ckWck6kaMD+x9YrioeS1Bbbw+DOLKYhHJ0RrOtfomp93A6+YSVQ5l5hQlOh
  sWcGC1NxSq/Y3Rn0xUwKQltkeHWE6hXxqU3tMN+Fekvd0Bo+1h4trRK9mPcedcoR
  RkMXVHktn+c8ezfvskyvoPzal/muHAlWTjQZLVmJkrhxR+8oVgAz4U2PlBU3TOov
  g2z4YjTjVw10YYWFk94ePaUBkNUg2LWZY45QhXeGyPwdpZX9bGtFX3jO1JSqSAmn
  OJfBAjsLZZo+JeQssQCydy0EKxyoaGUBnWkqckqBeMfDIA4YbJV2NvqGGvmnftsV
  S65dE5/LabFZoJumGszeXLGLJP0XML/hSdcnmhtvUcoD1T/BQ/BWVHyJIIsVp61p
  shxyBEjWWyzM39PSIwdjTEH74y55QVRB4h4QBNCve8WuKXvzKu+mSSfABfz2x2Gw
  BNJUF4RItN7x9TYLoSzj
  =wEdz
  -END PGP SIGNATURE-

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

___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-ha] [Bug 1677776] [NEW] Missing dep8 tests

2017-03-30 Thread Joshua Powers 
Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source cluster-glue zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/cluster-glue
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3XYgAAoJEIP8BxPaZgwlTF8P/2xJ8jLaR8FhFX6GKD4biZkq
hbo88HMufM1hmyYq00ps9DmOAhU4Ck/eTlmvtm/UJ9L+8vyD+MBrTb9lzH0IEunt
7q7TEXvSnsK15RMpEehtO/DrlATurTtGa8vSIJHtpiWTpZCetP/i/UqTsFX1/0vK
zfZcvquVPdBdwKYD7bWQxVOJyzki4ZzSjDG2sexYPtFyjnBN5fIkRuAtN4bPurgE
GgS4xhkNDsQJFZP23q547Rh8g1DsfczZZw+xLOs45DJFFwK7xuXpFbIZi1/TipHX
yErejpmMwp25SQ9kxBBHjkwI1Or7sxZX25igJ2/n2ITUge3eZHY6wBvjObjBc+cV
35foRiCSwdivgI1b8TH4OxGgNUBZ9wTIOTGLVSaKoxfFuBMkmUlqFWjGpKwD8j9q
AfRbAwgFkn7cgFhJ0e/ZyMRDup9u/bx0+40CN16tzVGdg0nwzdlfhnb5Y7z/H/O3
CuH5GGvsldSBcmR10FdvS0PLGhM4y8VX2WTyOellKdCHpvE5BeZ9GKUOiB9bL3aq
HXezKvQZAtLWVs7z+wcHxLBQ65KKYnsCWiDMUbKrjk5qIPUnvVIv5PFSWPDtveO8
lGT04S0X6kTXcbyCISad5XDYOvq1PzJajJyE37+HQQkDfE/WFK9QQjWPS+3WCm9F
wJjkogJGLQ05NyMo0g04
=P3Tc
-END PGP SIGNATURE-

** Affects: cluster-glue (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-glue in Ubuntu.
https://bugs.launchpad.net/bugs/166

Title:
  Missing dep8 tests

Status in cluster-glue package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source cluster-glue zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/cluster-glue
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XYgAAoJEIP8BxPaZgwlTF8P/2xJ8jLaR8FhFX6GKD4biZkq
  hbo88HMufM1hmyYq00ps9DmOAhU4Ck/eTlmvtm/UJ9L+8vyD+MBrTb9lzH0IEunt
  7q7TEXvSnsK15RMpEehtO/DrlATurTtGa8vSIJHtpiWTpZCetP/i/UqTsFX1/0vK
  zfZcvquVPdBdwKYD7bWQxVOJyzki4ZzSjDG2sexYPtFyjnBN5fIkRuAtN4bPurgE
  GgS4xhkNDsQJFZP23q547Rh8g1DsfczZZw+xLOs45DJFFwK7xuXpFbIZi1/TipHX
  yErejpmMwp25SQ9kxBBHjkwI1Or7sxZX25igJ2/n2ITUge3eZHY6wBvjObjBc+cV
  35foRiCSwdivgI1b8TH4OxGgNUBZ9wTIOTGLVSaKoxfFuBMkmUlqFWjGpKwD8j9q
  AfRbAwgFkn7cgFhJ0e/ZyMRDup9u/bx0+40CN16tzVGdg0nwzdlfhnb5Y7z/H/O3
  CuH5GGvsldSBcmR10FdvS0PLGhM4y8VX2WTyOellKdCHpvE5BeZ9GKUOiB9bL3aq
  HXezKvQZAtLWVs7z+wcHxLBQ65KKYnsCWiDMUbKrjk5qIPUnvVIv5PFSWPDtveO8
  lGT04S0X6kTXcbyCISad5XDYOvq1PzJajJyE37+HQQkDfE/WFK9QQjWPS+3WCm9F
  wJjkogJGLQ05NyMo0g04
  =P3Tc
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/166/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-ha] [Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

2017-03-30 Thread Jorge Niedbalski 
** Patch added: "lp1677684-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+attachment/4850762/+files/lp1677684-trusty.debdiff

** Description changed:

  [Environment]
  
  Ubuntu Xenial 16.04
  Amd64
  
- [Reproduction]
+ [Test Case]
  
- - Install corosync
- - Run the corosync-blackbox executable.
+ 1) sudo apt-get install corosync
+ 2) sudo corosync-blackbox.
  
  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep 
black
  /usr/bin/corosync-blackbox
  
  Expected results: corosync-blackbox runs OK.
+ 
  Current results:
  
  $ sudo corosync-blackbox
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found
  
- Fix:
+ [Impact]
  
+  * Cannot run corosync-blackbox
+ 
+ [Regression Potential]
+ 
+ * None identified.
+ 
+ [Fix]
  Make the package dependant of libqb-dev
  
  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
  /usr/sbin/qb-blackbox

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1677684

Title:
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-
  blackbox: not found

Status in corosync package in Ubuntu:
  In Progress
Status in corosync source package in Trusty:
  In Progress
Status in corosync source package in Xenial:
  In Progress

Bug description:
  [Environment]

  Ubuntu Xenial 16.04
  Amd64

  [Test Case]

  1) sudo apt-get install corosync
  2) sudo corosync-blackbox.

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep 
black
  /usr/bin/corosync-blackbox

  Expected results: corosync-blackbox runs OK.

  Current results:

  $ sudo corosync-blackbox
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found

  [Impact]

   * Cannot run corosync-blackbox

  [Regression Potential]

  * None identified.

  [Fix]
  Make the package dependant of libqb-dev

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
  /usr/sbin/qb-blackbox

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

___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-ha] [Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

2017-03-30 Thread Jorge Niedbalski 
** Patch added: "lp1677684-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+attachment/4850713/+files/lp1677684-xenial.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1677684

Title:
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-
  blackbox: not found

Status in corosync package in Ubuntu:
  In Progress
Status in corosync source package in Trusty:
  In Progress
Status in corosync source package in Xenial:
  In Progress

Bug description:
  [Environment]

  Ubuntu Xenial 16.04
  Amd64

  [Reproduction]

  - Install corosync
  - Run the corosync-blackbox executable.

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep 
black
  /usr/bin/corosync-blackbox

  Expected results: corosync-blackbox runs OK.
  Current results:

  $ sudo corosync-blackbox
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found

  Fix:

  Make the package dependant of libqb-dev

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
  /usr/sbin/qb-blackbox

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

___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-ha] [Bug 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

2017-03-30 Thread Jorge Niedbalski 
** Tags removed: sts
** Tags added: sts-sponsor

** Patch added: "lp1677684-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+attachment/4850712/+files/lp1677684-zesty.debdiff

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

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

** Changed in: corosync (Ubuntu)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

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

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

** Changed in: corosync (Ubuntu Trusty)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

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

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

** Changed in: corosync (Ubuntu Xenial)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1677684

Title:
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-
  blackbox: not found

Status in corosync package in Ubuntu:
  In Progress
Status in corosync source package in Trusty:
  In Progress
Status in corosync source package in Xenial:
  In Progress

Bug description:
  [Environment]

  Ubuntu Xenial 16.04
  Amd64

  [Reproduction]

  - Install corosync
  - Run the corosync-blackbox executable.

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep 
black
  /usr/bin/corosync-blackbox

  Expected results: corosync-blackbox runs OK.
  Current results:

  $ sudo corosync-blackbox
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found

  Fix:

  Make the package dependant of libqb-dev

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
  /usr/sbin/qb-blackbox

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

___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-ha] [Bug 1677684] [NEW] /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

2017-03-30 Thread Jorge Niedbalski 
Public bug reported:

[Environment]

Ubuntu Xenial 16.04
Amd64

[Reproduction]

- Install corosync
- Run the corosync-blackbox executable.

root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep black
/usr/bin/corosync-blackbox

Expected results: corosync-blackbox runs OK.
Current results:

$ sudo corosync-blackbox
/usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found

Fix:

Make the package dependant of libqb-dev

root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
/usr/sbin/qb-blackbox

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


** Tags: sts

** Tags added: sts

** Description changed:

  [Environment]
  
  Ubuntu Xenial 16.04
  Amd64
  
  [Reproduction]
  
  - Install corosync
  - Run the corosync-blackbox executable.
  
  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep 
black
  /usr/bin/corosync-blackbox
  
  Expected results: corosync-blackbox runs OK.
  Current results:
  
  $ sudo corosync-blackbox
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found
+ 
+ Fix:
+ 
+ Make the package dependant of libqb-dev
+ 
+ root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
+ /usr/sbin/qb-blackbox

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1677684

Title:
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-
  blackbox: not found

Status in corosync package in Ubuntu:
  New

Bug description:
  [Environment]

  Ubuntu Xenial 16.04
  Amd64

  [Reproduction]

  - Install corosync
  - Run the corosync-blackbox executable.

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep 
black
  /usr/bin/corosync-blackbox

  Expected results: corosync-blackbox runs OK.
  Current results:

  $ sudo corosync-blackbox
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found

  Fix:

  Make the package dependant of libqb-dev

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
  /usr/sbin/qb-blackbox

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

___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp