[Ubuntu-ha] [Bug 1227580] Re: Monitoring in Master state doesn't always work

2020-03-29 Thread Rafael David Tinoco
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment 
stating why and then change the status of the bug to 'New'.

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

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

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

Title:
  Monitoring in Master state doesn't always work

Status in pacemaker package in Ubuntu:
  Fix Released
Status in pacemaker source package in Precise:
  Incomplete

Bug description:
  Hi
  There is a bug that master/slave resources are not always monitored. It is 
already fixed in pacemaker trunk, but not in libpengine3 1.1.6-2ubuntu3. I 
patched lib/pengine/unpack.c

  
  1391c1391,1395
  <   } else if(safe_str_eq(task, CRMD_ACTION_START)) {
  ---
  >   } else if(safe_str_eq(task, CRMD_ACTION_START) || 
  >   safe_str_eq(task, CRMD_ACTION_MIGRATED) || 
  >   safe_str_eq(task, CRMD_ACTION_PROMOTE) || 
  >   safe_str_eq(task, CRMD_ACTION_DEMOTE)) {
  > 

  With this monitoring also works if resource has been promoted. This
  bug can cause much trouble as a failed service wont be recognized.

  Best regards

  Achim

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1227580/+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 1227580] Re: Monitoring in Master state doesn't always work

2020-03-29 Thread Rafael David Tinoco
The mentioned patch is the following one:

commit fc03be02bf3a045babfe8233cbc99227da71d024
Author: David Vossel 
Date:   Fri Jun 29 11:24:52 2012 -0500

High: pengine: cl#5072 - Fixes monitor op stopping after rsc
promotion.

and was supposed to be applied to Precise.

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

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

Title:
  Monitoring in Master state doesn't always work

Status in pacemaker package in Ubuntu:
  Fix Released
Status in pacemaker source package in Precise:
  Incomplete

Bug description:
  Hi
  There is a bug that master/slave resources are not always monitored. It is 
already fixed in pacemaker trunk, but not in libpengine3 1.1.6-2ubuntu3. I 
patched lib/pengine/unpack.c

  
  1391c1391,1395
  <   } else if(safe_str_eq(task, CRMD_ACTION_START)) {
  ---
  >   } else if(safe_str_eq(task, CRMD_ACTION_START) || 
  >   safe_str_eq(task, CRMD_ACTION_MIGRATED) || 
  >   safe_str_eq(task, CRMD_ACTION_PROMOTE) || 
  >   safe_str_eq(task, CRMD_ACTION_DEMOTE)) {
  > 

  With this monitoring also works if resource has been promoted. This
  bug can cause much trouble as a failed service wont be recognized.

  Best regards

  Achim

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