Bug 1420426 - When deploying a cluster using short hostnames, resources running via pacemaker-remote won't work correctly if the remote's hostname is a FQDN
Summary: When deploying a cluster using short hostnames, resources running via pacemak...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.3
Hardware: All
OS: All
urgent
urgent
Target Milestone: rc
: 7.3
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1417936
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-08 15:43 UTC by Jaroslav Reznik
Modified: 2017-03-02 17:12 UTC (History)
10 users (show)

Fixed In Version: pacemaker-1.1.15-11.el7_3.4
Doc Type: Bug Fix
Doc Text:
Prior to this update, if a resource agent used the crm_node command to obtain the node name, the resource agent sometimes received incorrect information if it was running on a Pacemaker remote node. This negatively affected the functionality of resource agents that use the node name. Now, Pacemaker automatically sets an environment variable with the node name, and crm_node uses this variable when it is available. As a result, the described problem no longer occurs.
Clone Of: 1417936
Environment:
Last Closed: 2017-03-02 17:12:37 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0383 0 normal SHIPPED_LIVE pacemaker bug fix update 2017-03-02 22:05:51 UTC

Description Jaroslav Reznik 2017-02-08 15:43:08 UTC
This bug has been copied from bug #1417936 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 3 Ken Gaillot 2017-02-08 18:34:43 UTC
Fixed upstream by commit e0eb9e7

Comment 7 errata-xmlrpc 2017-03-02 17:12:37 UTC
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-2017-0383.html


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