Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ocf_local_nodename incorrectly detect pacemaker version causing incorrect behavior #1942

Open
Sildulir opened this issue May 29, 2024 · 1 comment
Assignees

Comments

@Sildulir
Copy link

Sildulir commented May 29, 2024

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).

@oalbrigt
Copy link
Contributor

Thanks. I'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants