-
Notifications
You must be signed in to change notification settings - Fork 8
NO-JIRA: Claude tool - etcd troubleshooting skill #32
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fonta-rh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@fonta-rh: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
a4c5145 to
50f415d
Compare
e527c8e to
8b1da20
Compare
clobrano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some comments
|
|
||
| ```bash | ||
| # From repository root | ||
| ./.claude/commands/etcd/scripts/collect-all-diagnostics.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having scripts in an hidden directories works against discoverability. What's the reasoning behind this choice?
Also, .claude/commands is a special one for Claude. One could try to execute it as a "custom command":
[in Claude CLI] > /etcd:scripts:collect-all-diagnostic.shI'm curious to see if this works :D
| @@ -0,0 +1,2052 @@ | |||
| #!/bin/sh | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to keep this file in sync automatically?
| when: podman_inspect.rc == 0 | ||
|
|
||
| - name: Get podman logs for etcd | ||
| ansible.builtin.command: podman logs --tail 100 etcd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why limit to 100? Would it be too much to get all logs?
| - Added `force-new-cluster.yml` for automated etcd cluster recovery via CIB attributes | ||
| - Ansible conversion of Carlo Lobrano's shell script using `cluster_vms` inventory group |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a warning about the playbook assuming the first node in the inventory is the leader.
Another option would be to add some confirmation step in the playbook itself, to ensure the target node is correct.
8b1da20 to
8f455fb
Compare
Add etcd troubleshooting skill for Claude Code
Adds a comprehensive Claude Code skill that helps troubleshoot etcd issues on two-node fencing clusters.
The skill enables automated diagnosis and remediation of common etcd/Pacemaker problems.
New feature: Claude Code Skill (.claude/commands/etcd/):
Diagnostic Tools:
Helper:
Documentation:
Tested with: