Red Hat Bugzilla – Bug 493165
group_tool ls fence returns one for fence id ZERO
Last modified: 2016-04-26 11:25:35 EDT
Description of problem:
In some occasions groupd allows the fence domain to be ZERO:
type level name id state
fence 0 default 00000000 none
[1 2 3]
When that happens queries to the 'default fence domain' will fail:
# group_tool ls fence default
groupd has no information about the specified group
# echo $?
# group_tool ls fence default &> /dev/null
# echo $?
Because such queries are used by rgmanager, this causes rgmanager to hang on startup.
Every time that the fence domain id is zero.
Steps to Reproduce:
Startup the cluster and obtain id zero for the fence domain. This is not the normal case.
Created attachment 337401 [details]
Previous fix just allows group_tool to work if id == 0; it doesn't change the problem that causes groupd to assign a group the id of 0.
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
- cause: command "group_tool ls fence default"
- consequence: command reports the group does not exist, when the group does exist but has zero id
- fix: group_tool checks for name instead of id
- result: group_tool ls now correctly reports about a group even if the group has zero id
Adding issue 301850.
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.