Back to bug 1394418

Who When What Removed Added
Chris Feist 2016-11-28 23:07:28 UTC CC cfeist
Ken Gaillot 2017-01-16 23:46:50 UTC Status NEW ASSIGNED
Assignee kgaillot abeekhof
michal novacek 2017-08-04 08:54:02 UTC CC mnovacek
Chris Feist 2017-08-11 16:40:53 UTC Priority unspecified urgent
Severity high urgent
Anthony Herr 2017-08-11 16:56:36 UTC CC aherr
Ken Gaillot 2017-09-13 16:28:03 UTC Status ASSIGNED POST
Target Release --- 7.5
CC kgaillot
Oneata Mircea Teodor 2017-09-14 06:40:12 UTC Blocks 1491544
Oneata Mircea Teodor 2017-09-14 06:40:28 UTC Keywords ZStream
Ken Gaillot 2017-10-10 17:06:48 UTC Status POST MODIFIED
Fixed In Version pacemaker-1.1.18-1.el7
Doc Text Previously, Pacemaker did not implement unfencing for remote nodes. As a consequence, in a cluster using a fence agent that supports unfencing, such as fence_scsi or fence_mpath, fenced remote nodes could not rejoin the cluster without manually being unfenced. With this update, Pacemaker correctly implements unfencing for Pacemaker remote nodes, and the described problem no longer occurs.
Doc Type If docs needed, set a value Release Note
errata-xmlrpc 2017-10-10 17:47:46 UTC Status MODIFIED ON_QA
Ioanna Gkioka 2017-10-11 06:48:33 UTC CC igkioka
Doc Text Previously, Pacemaker did not implement unfencing for remote nodes. As a consequence, in a cluster using a fence agent that supports unfencing, such as fence_scsi or fence_mpath, fenced remote nodes could not rejoin the cluster without manually being unfenced. With this update, Pacemaker correctly implements unfencing for Pacemaker remote nodes, and the described problem no longer occurs. Previously, Pacemaker did not implement unfencing for Pacemaker remote nodes. As a consequence, Pacemaker remote nodes were fenced even if a fence device required unfencing. With this update, Pacemaker correctly implements unfencing
for Pacemaker remote nodes, and the described problem no longer occurs.
Ioanna Gkioka 2017-10-12 06:43:29 UTC Doc Text Previously, Pacemaker did not implement unfencing for Pacemaker remote nodes. As a consequence, Pacemaker remote nodes were fenced even if a fence device required unfencing. With this update, Pacemaker correctly implements unfencing
for Pacemaker remote nodes, and the described problem no longer occurs.
Previously, Pacemaker did not implement unfencing for Pacemaker remote nodes. As a consequence, Pacemaker remote nodes remained fenced even if a fence device required unfencing. With this update, Pacemaker correctly implements both fencing and unfencing for Pacemaker remote nodes, and the described problem no longer occurs.
Lenka Špačková 2017-11-15 14:04:36 UTC Docs Contact slevine
michal novacek 2017-12-04 16:28:03 UTC QA Contact cluster-qe oblaut
Steven J. Levine 2017-12-07 18:20:20 UTC Doc Text Previously, Pacemaker did not implement unfencing for Pacemaker remote nodes. As a consequence, Pacemaker remote nodes remained fenced even if a fence device required unfencing. With this update, Pacemaker correctly implements both fencing and unfencing for Pacemaker remote nodes, and the described problem no longer occurs. Pacemaker correctly implements fencing and unfencing for Pacemaker remote nodes

Previously, Pacemaker did not implement unfencing for Pacemaker remote nodes. As a consequence, Pacemaker remote nodes remained fenced even if a fence device required unfencing. With this update, Pacemaker correctly implements both fencing and unfencing for Pacemaker remote nodes, and the described problem no longer occurs.
Marian Krcmarik 2018-02-27 13:29:12 UTC Status ON_QA VERIFIED
errata-xmlrpc 2018-04-10 02:09:29 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2018-04-10 15:28:37 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2018-04-10 11:28:37 UTC
errata-xmlrpc 2018-04-10 15:29:53 UTC Link ID Red Hat Product Errata RHEA-2018:0860

Back to bug 1394418