Skip to content

ocf_local_nodename incorrectly detect pacemaker version causing incorrect behavior #1942

Description

@Sildulir

Since ClusterLabs/pacemaker@67e342d pacemakerd -$ return two lines containing matching the regex used by ocf_local_nodename to detect the version of pacemaker used.

This break version detection and cause ocf_local_nodename to use uname -n instead of crm_node -n to get the name of the local node. Breaking any agent relying on this function on a node that doesn't use its hostname as its nodename.

I noticed this problem when attempting to use ganesha_grace from the GlusterFS project, but this function seems to be used by agents in this repository too (and using this function should be the correct thing to do anyway).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions