Bug 1833384
| Summary: | crm_node -n does not output the remote node [rhel-8.2.0.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.2 | CC: | cfeist, cluster-maint, kgaillot, michele, pkomarov |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | 8.2 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-2.0.3-5.el8_2.1 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Pacemaker did not initialize a variable used to inspect a command-line node name request from a Pacemaker Remote node.
Consequence: "crm_node -n", when run manually or scripted on a Pacemaker Remote node (calls from within a resource agent executed by Pacemaker were not affected), sometimes reports the name of the cluster node hosting the remote connection instead of the Pacemaker Remote node's name.
Fix: The variable is now initialized properly.
Result: "crm_node -n" reliably reports the correct name on a Pacemaker Remote node.
|
Story Points: | --- |
| Clone Of: | 1830535 | Environment: | |
| Last Closed: | 2020-06-10 09:21:52 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: | 1830535 | ||
| Bug Blocks: | |||
|
Comment 1
Ken Gaillot
2020-05-08 15:01:49 UTC
Verified , [stack@undercloud-0 ~]$ ansible overcloud -b -mshell -a'rpm -q pacemaker' controller-2 | CHANGED | rc=0 >> pacemaker-2.0.3-5.el8_2.1.x86_64 controller-1 | CHANGED | rc=0 >> pacemaker-2.0.3-5.el8_2.1.x86_64 compute-0 | CHANGED | rc=0 >> pacemaker-2.0.3-5.el8_2.1.x86_64 compute-1 | CHANGED | rc=0 >> pacemaker-2.0.3-5.el8_2.1.x86_64 controller-0 | CHANGED | rc=0 >> pacemaker-2.0.3-5.el8_2.1.x86_64 [stack@undercloud-0 ~]$ ansible overcloud -b -mshell -a' crm_node -n' controller-2 | CHANGED | rc=0 >> controller-2 controller-0 | CHANGED | rc=0 >> controller-0 controller-1 | CHANGED | rc=0 >> controller-1 compute-1 | CHANGED | rc=0 >> overcloud-novacomputeiha-1 compute-0 | CHANGED | rc=0 >> overcloud-novacomputeiha-0 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/RHBA-2020:2455 |