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.

Sign up for GitHub

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

Jump to bottom

SHC captain logic fails when existing captain exists #168

Closed
haidangwa opened this issue May 15, 2020 · 0 comments
Closed

SHC captain logic fails when existing captain exists #168

haidangwa opened this issue May 15, 2020 · 0 comments
Assignees
@haidangwa

Comments

@haidangwa
Copy link
Contributor

In a distributed cluster environment, the SHC captain role sometimes does not detect or is incorrectly detecting that an existing captain in the SHC.
@haidangwa haidangwa self-assigned this May 15, 2020
haidangwa added a commit that referenced this issue Jun 29, 2020
@haidangwa
Fixes Issue [#168](#168)
8cb1b2c 
  * uses `node.normal` when `ruby_block[captain elected]` executes to persist that value between chef runs
  * requires manually updating node data to set `node.normal['splunk']['shclustering']['captain_elected'] = true` if you've already deployed v6.2.6 of this cookbook previously; otherwise, skip v6.2.6 and run v6.2.7 directly.

Signed-off-by: Dang H. Nguyen <[email protected]>
@haidangwa haidangwa mentioned this issue Jun 29, 2020
Merged
4 tasks
haidangwa added a commit that referenced this issue Jun 29, 2020
@haidangwa
Merge pull request #175 from chef-cookbooks/gh-168
ef2a65c 
Fixes Issue #168
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@haidangwa haidangwa

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@haidangwa