[Bug 1720397] Re: qemu-kvm doesnt restart after node reboot

2017-10-25 Thread Corey Bryant
Regression testing with OpenStack tempest for Ocata has completed
successfully.

xenial-ocata proposed stable charms:

==   
Totals   
==   
Ran: 102 tests in 1742.1837 sec.  
 - Passed: 93
 - Skipped: 9
 - Expected Fail: 0  
 - Unexpected Success: 0 
 - Failed: 0 
Sum of execute time for each test: 856.3288 sec.

xenial-ocata proposed dev charms:

==
Totals
==
Ran: 102 tests in 1987.3271 sec.
 - Passed: 93
 - Skipped: 9
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 1008.6304 sec.

zesty-ocata proposed stable charms:

==
Totals
==
Ran: 102 tests in 1604.2247 sec.
 - Passed: 93
 - Skipped: 9
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 843.3645 sec.

zesty-ocata proposed dev charms:

==
Totals
==
Ran: 102 tests in 1579.9423 sec.
 - Passed: 93
 - Skipped: 9
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 867.0801 sec.

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

Title:
  qemu-kvm doesnt restart after node reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1720397/+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 1718668] Re: Libvirt FTBFS in Artful on x86

2017-10-25 Thread Corey Bryant
This bug was fixed in the package libvirt - 3.6.0-1ubuntu5~cloud0
---

 libvirt (3.6.0-1ubuntu5~cloud0) xenial-pike; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 libvirt (3.6.0-1ubuntu5) artful; urgency=medium
 .
   * d/p/u/gnulib-getopt-posix-Fix-build-failure-when-using-ac_cv_head.patch:
 fix FTBFS with glibc 2.26 (LP: #1718668)


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

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

Title:
  Libvirt FTBFS in Artful on x86

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1718668/+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 1720397] Re: qemu-kvm doesnt restart after node reboot

2017-10-25 Thread Corey Bryant
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3~cloud0
---

 qemu (1:2.10+dfsg-0ubuntu3~cloud0) xenial-pike; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 qemu (1:2.10+dfsg-0ubuntu3) artful; urgency=medium
 .
   * fix enablement of qemu-kvm service (LP: #1720397)
 - rename d/qemu-kvm.service to d/qemu-system-common.qemu-kvm.service
 - d/rules: add proper enablement debhelper calls
 - d/qemu-system-common.install: install covered by dh_installinit


** Changed in: cloud-archive/pike
   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/1720397

Title:
  qemu-kvm doesnt restart after node reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1720397/+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 1720397] Update Released

2017-10-25 Thread Corey Bryant
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. 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
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1720397

Title:
  qemu-kvm doesnt restart after node reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1720397/+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 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

2017-10-25 Thread Andreas Hasenack
Ah, Java, I hadn't realised that. I have a couple a
I can try too with ssh -X.

On Oct 25, 2017 12:31, "thomas duriez" <1726...@bugs.launchpad.net>
wrote:

> I will try. For the moment I double boot 16.04 because I need to have it
> working, but I can run tests on spare time. Because I couldn't find
> problems when not running the java machine of Matlab  I will focus on
> applications relying heavily on java. If you have any suggestion it
> would help. Thanks again for your time.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1726595
>
> Title:
>   Running Matlab (R) from ssh session with X forwarding doesn't work
>   anymore in 17.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/
> 1726595/+subscriptions
>

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

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1726595/+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 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

2017-10-25 Thread Andreas Hasenack
Most curious. It would be of tremendous help if you could find another
application that behaves like that, one that is opensource and part of
the ubuntu archive preferably.

DISPLAY being set to, for example, localhost:10.0, is indicating that
the X alls are going through ssh in that particular case. It's setup by
the -X parameter.

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

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1726595/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Also validated that the update fixes an existing machine with the 1.2
update on it (with pacemaker services not running).

Pacemaker started after the update.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Also tested proposed fix on a three unit gnocchi HA deployment; all
pacemaker updates applied and restarted pacemaker postinst as desired.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Testing from security-proposed PPA:

Broken install (dpkg-reconfigure pacemaker already run, daemons
stopped):  Packages updated and pacemaker daemon restarted by postinst:
OK

Running install (pacemaker daemons running prior to pkg upgrade):
Packages update, pacemaker daemon stop prior to unpack and restarted by
postinst: OK

>From my perspective the update looks good - but would appreciate a
second pair of eyes on this one.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Updates building in:

  https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
** Description changed:

  [Impact]
  upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.
  
  [Test Case]
  sudo apt install pacemaker
  sudo systemctl start pacemaker
  sudo dpkg-reconfigure pacemaker
  
  pacemaker daemons will not be restarted.
  
  [Regression Potential]
- TBC as not quite sure where the fix for this is.
+ Minimal, earlier and later versions provide the defaults in the lsb header.
  
  [Original Bug Report]
  We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).
  
  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.
  
  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.
  
  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)
  
  I have not checked whether this affects trusty environments.
  
  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop entries.
  
  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Tested OK (pacemaker was restarted after upgrade)

Uploaded to unapproved queue for SRU Team review - I'd suggest we
fasttrack this ASAP into -updates and -security to catch auto updates
for those systems not already updated.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Doing some testing via:

  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3010

before upload to xenial-proposed; not that the act of fixing this
problem will in itself cause the pacemaker daemons to be started on
upgrade.  However it won't be auto-applied on a default install (unlike
the security update that caused the original issue).

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Proposed update for xenial

** Patch added: "pacemaker.debdiff"
   
https://bugs.launchpad.net/ubuntu/zesty/+source/pacemaker/+bug/1727063/+attachment/4993845/+files/pacemaker.debdiff

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Actually this only impacts Xenial; Debian carried a patch from:

pacemaker (1.1.15~rc3-1) unstable; urgency=medium

  [ Christoph Berg ]
  * [23ee108] libcrmservice3.symbols: Exclude systemd symbol on non-linux
  * [41dea05] Fix time formatting on x32
  * [533c5cc] Fix FTBFS on GNU Hurd

  [ Arturo Borrero Gonzalez ]
  * [698053d] d/tests/control: add isolation-container restriction

  [ Ferenc Wágner ]
  * [065159d] New patch Enable-the-init-scripts-on-multi-user-runlevels.patch
  * [7a5008b] New patch Make-the-asciidoc-documentation-reproducible.patch
  * [08a4162] New patch Add-remote_fs-dependencies-to-the-init-scripts.patch
  * [7a65d2c] New upstream release (1.1.15~rc1)
  * [dd9f5f4] Remove upstreamed patches, refresh the rest
  * [0cdd116] Update symbol files
  * [3de7a21] New patch Add-documentation-URIs-to-the-service-files.patch
  * [9faaa02] Move documentation generators into Build-Depends-Indep
  * [9362a46] Move documentation into /usr/share/doc/pacemaker
  * [64c0e84] Move misc documentation files into the pacemaker-doc package
  * [837e74d] New patch Read-default-files-in-pacemaker.service.patch
  * [72fef80] New upstream release (1.1.15~rc2)
  * [69ee575] Remove patch included in 1.1.15~rc2
  * [46dce98] Also add documentation URI to our version of crm_mon.service
  * [8c25aff] New patch to avoid using WIFCONTINUED entirely
  * [a28e0ae] New upstream release (1.1.15~rc3)
  * [a8976fe] Remove freshly upstreamed patches, refresh the rest

 -- Ferenc Wágner   Sat, 28 May 2016 22:28:49 +0200


Which re-enables the default runlevels.

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

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

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

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
This issue can be fixed by re-adding the required Start/Stop bits to the
LSB header; however the behaviour of update-rc.d when native systemd
unit files are in use looks odd to me.

Raising an init-system-helpers bug task for foundations team input on
this.

** Also affects: init-system-helpers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Hmmm - however pacemaker@xenial ships with a native systemd unit; so I'm
baffled as to the behaviour of the package upgrade.

** Description changed:

- We have found on our openstack charm-hacluster implementations that the
- pacemaker .deb packaging along with the upstream pacemaker configuration
- result in pacemaker stopping but not starting upon package upgrade
- (while attended or unattended).
+ [Impact]
+ upgrades of the pacemaker package don't restart pacemaker after the package 
upgrade, resulting in down HA clusters.
+ 
+ [Test Case]
+ sudo apt install pacemaker
+ sudo systemctl start pacemaker
+ sudo dpkg-reconfigure pacemaker
+ 
+ pacemaker daemons will not be restarted.
+ 
+ [Regression Potential]
+ TBC as not quite sure where the fix for this is.
+ 
+ [Original Bug Report]
+ We have found on our openstack charm-hacluster implementations that the 
pacemaker .deb packaging along with the upstream pacemaker configuration result 
in pacemaker stopping but not starting upon package upgrade (while attended or 
unattended).
  
  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.
  
  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.
  
  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to 
start the service, but silently fails due to policy denial.  It appears the 
policy check fails because /etc/rcX.d/S*pacemaker does not exist because 
/etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB 
init headers.  (or rather, they are blank.)
  
  I have not checked whether this affects trusty environments.
  
  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop entries.
  
  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1322899] Re: pacemaker init script links aren't created on upgrade

2017-10-25 Thread James Page
See related bug 1727063

** Changed in: pacemaker (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  pacemaker init script links aren't created on upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1322899/+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 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts

2017-10-25 Thread James Page
See related bug 1727063

** Changed in: pacemaker (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  corosync hangs due to missing pacemaker shutdown scripts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Marking charm bug task as invalid - its doing the right things, however
the package does not declare default start/stop levels so its all
foobar.

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Other related bugs - bug 1322899 and bug 1052449

** Changed in: pacemaker (Ubuntu)
   Status: Confirmed => Triaged

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

** Changed in: pacemaker (Ubuntu)
   Importance: High => Critical

** Also affects: pacemaker (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: pacemaker (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: pacemaker (Ubuntu Bionic)
   Importance: Critical
   Status: Triaged

** Also affects: pacemaker (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: pacemaker (Ubuntu Zesty)
   Importance: Undecided => Critical

** Changed in: pacemaker (Ubuntu Artful)
   Importance: Undecided => Critical

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

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

** Changed in: pacemaker (Ubuntu Xenial)
   Importance: Undecided => Critical

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

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
I think this is a packaging/upstream bug which I appear to have had a go
at before (see #4); however I've not seen this specific symptom before.

** Changed in: charm-hacluster
   Status: New => Invalid

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
And

https://github.com/ClusterLabs/pacemaker/pull/656

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage

2017-10-25 Thread James Page
Hmm

https://github.com/ClusterLabs/pacemaker/commit/fc11a4651b971bd3b9dfc15b8b5c538c7ee9ab75
#diff-06baf804b1f5edee72fb63df4b884b7c

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

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+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