Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1571765 - Pending notify actions are recorded as complete [OpenStack-13.0]
Pending notify actions are recorded as complete [OpenStack-13.0]
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director-images (Show other bugs)
13.0 (Queens)
All All
urgent Severity urgent
: beta
: 13.0 (Queens)
Assigned To: Jon Schlueter
Udi Shkalim
: Triaged
Depends On: 1570618
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-25 07:48 EDT by Andrew Beekhof
Modified: 2018-07-09 07:22 EDT (History)
16 users (show)

See Also:
Fixed In Version: rhosp-director-images-13.0-20180425.2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
When record-pending is true (which is the default as of 7.5), Pacemaker sees two notifications that notify actions completed: one when the action is initiated and another when it completes. This confuses the cluster and triggers a re-computation of the cluster state, which results in more notifications and more re-computations. The issue was resolved by configuring Pacemaker to only record completed clone-notify actions as successful, not those that are pending, which enables the cluster to complete the process of recovering or starting services.
Story Points: ---
Clone Of: 1570618
Environment:
Last Closed: 2018-06-27 09:24:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2083 None None None 2018-06-27 09:26 EDT

  None (edit)
Comment 1 Andrew Beekhof 2018-04-25 07:49:36 EDT
Critical bugfix from RHEL-HA that prevents control plane recovery from stalling.
Comment 3 Jon Schlueter 2018-04-25 08:57:06 EDT
Confirmed this needs to make it into overcloud-full images for controller nodes
Comment 4 Lon Hohberger 2018-04-25 09:08:07 EDT
According to the parent bug, this is resolved by pacemaker-1.1.18-11.el7_5.2
Comment 10 Lon Hohberger 2018-04-26 07:59:49 EDT
pacemaker-1.1.18-11.el7_5.2 is in new images.
Comment 13 pkomarov 2018-04-30 06:56:24 EDT
Verified , 

Tested on core_puddle_version: 2018-04-26.1

verification of the pacemaker version on overcloud images: 

(undercloud) [stack@undercloud-0 ~]$ ansible controller -b -mshell -a'rpm -qa |grep pacemaker-1.1.18-11.el7_5.2'

controller-2 | SUCCESS | rc=0 >>
pacemaker-1.1.18-11.el7_5.2.x86_64

controller-1 | SUCCESS | rc=0 >>
pacemaker-1.1.18-11.el7_5.2.x86_64

controller-0 | SUCCESS | rc=0 >>
pacemaker-1.1.18-11.el7_5.2.x86_64

Functionality of the bug fix was verified on BZ1570130 and BZ1570618
Comment 16 errata-xmlrpc 2018-06-27 09:24:35 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2083

Note You need to log in before you can comment on or make changes to this bug.