Bug 1489728
| Summary: | Assorted bundle fixes | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Michele Baldessari <michele> | |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> | |
| Status: | CLOSED ERRATA | QA Contact: | Marian Krcmarik <mkrcmari> | |
| Severity: | urgent | Docs Contact: | Steven J. Levine <slevine> | |
| Priority: | urgent | |||
| Version: | 7.4 | CC: | abeekhof, aherr, cfeist, cluster-maint, kgaillot, michele, mkrcmari, rscarazz, sbradley, toneata, ushkalim | |
| Target Milestone: | rc | Keywords: | Triaged, ZStream | |
| Target Release: | 7.5 | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | pacemaker-1.1.18-1.el7 | Doc Type: | Release Note | |
| Doc Text: |
Pacemaker now probes guest nodes
Important update for users of guest nodes.
Pacemaker now probes guest nodes, which are Pacemaker remote nodes created using the `remote-node` parameter of a resource such as `VirtualDomain`. If users were previously relying on the fact that probes were not done, the probes may fail, potentially causing fencing of the guest node. If a guest node cannot run a probe of a resource (for example, if the software is not even installed on the guest), then the location constraint banning the resource from the guest node should have the `resource-discovery` option set to `never`, the same as would be required with a cluster node or remote node in the same situation.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1497602 1523352 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-10 15:30:29 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1489735, 1497602, 1501274 | |||
|
Description
Michele Baldessari
2017-09-08 08:36:37 UTC
Hello Michelle, This bug is not raised correctly. In order to have a zstream bug we need to clone from Y stream bug, we cannot raise directly a zstream bug. Please check the zstream process documentation, https://mojo.redhat.com/docs/DOC-1021938#jive_content_id_The_workflow Hi Oneata, yeah did this by mistake, undone. Thanks FYI the unfencing part has its own Bug 1394418 Additional patches in http://people.redhat.com/mbaldess/rpms/container-repo/srpms/pacemaker-1.1.16-12.13.el7.src.rpm + Andrew Beekhof (31 hours ago) 2709e5c: Fix: PE: Do not send notifications to unclean bundles + Andrew Beekhof (31 hours ago) e3485d6: Fix: PE: Prevent graph loops when fencing the host out from underneath a bundle These are all fixed upstream Ken: (Release note work) It turns out bundles remain in tech. preview for 7.5, but I don't think that affects this release note writeup. I downgraded the all-caps in your original note, since that's a little bit out of style. We can move this note to the top of the new feature list for clustering and it now has a title which should cause anybody who uses guest nodes to at least notice it and it begins with the isolated sentence about this being important (without being in all-caps). Do you think that's sufficient? Steven (For release note: We don't capitalize "Remote Node" in the docs so I uncapitalized it here.) The new text looks good, except for the Pacemaker Remote capitalization. I find the Pacemaker Remote terminology unfortunate, but it's what we have to work with ... We have: * cluster node = node running the full cluster stack including corosync * remote node = node running pacemaker_remote and integrated into the cluster via an ocf:pacemaker:remote resource * guest node = node running pacemaker_remote and integrated into the cluster via a resource such as VirtualDomain with the remote-node parameter set There's no accepted term for "any node running pacemaker_remote", aka "remote node or guest node", so I've been using "Pacemaker Remote node". Feel free to use something else, but the intention is not the same as "remote node". 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:0860 |