Bug 1344223
| Summary: | pacemaker does not flush the attrd cache fully after a crm_node -R node removal | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | abeekhof, cfeist, cluster-maint, dbecker, dciabrin, dmacpher, hbrock, jkortus, kgaillot, mburns, mcornea, michele, mjuricek, mnavrati, morazi, rhel-osp-director-maint, sasha, srevivo |
| Target Milestone: | rc | Keywords: | Documentation, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-1.1.13-10.el7_2.3 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, Pacemaker's node attribute manager removed attribute values from its memory but not the attributes themselves when purging a node removed from the cluster. As a consequence, if a new node was later added to the cluster with the same node ID, attributes that existed on the original node could not be set for the new node. With this update, Pacemaker purges the attributes themselves when removing a node. As a result, attributes can be set as expected on a node with the same ID as an older node.
|
Story Points: | --- |
| Clone Of: | 1338623 | Environment: | |
| Last Closed: | 2016-08-02 18:24:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1338623 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-06-09 08:27:38 UTC
QA: As mentioned in parent bz, this requires two tests, described in Bug 1338623 Comment 2 and Bug 1299348 Comment 4. 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://rhn.redhat.com/errata/RHBA-2016-1537.html |