add cluster pool troubleshooting skill for hosted-mgmt

[deepsm007]

/cc @openshift/test-platform

Summary by CodeRabbit

• Documentation
  • Added a comprehensive troubleshooting guide for diagnosing Hive ClusterPool issues, featuring detailed diagnostic workflows, log inspection techniques from multiple sources, failure pattern reference tables, and operational best practices to support cluster troubleshooting and diagnostics.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[coderabbitai]

Walkthrough

A new Markdown troubleshooting runbook is added that provides a step-by-step diagnostic workflow for investigating Hive ClusterPool issues, including procedures for inspecting resource status, tracing failures through provisioning stages, extracting logs, and checking Hive controller health.

Changes

Cohort / File(s)	Summary
Cluster Pools Troubleshooting Guide .claude/.claude-plugin/skills/Troubleshooting/Cluster-pools/SKILL.md	New 273-line troubleshooting runbook documenting oc commands and diagnostic procedures for ClusterPool issues, including resource inspection, log extraction, failure patterns, and operational checks.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: adding a cluster pool troubleshooting skill documentation file for the hosted-mgmt context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The custom check for stable Ginkgo test names applies only to Go test files, but this PR modifies only a Markdown documentation file.
Test Structure And Quality	✅ Passed	The custom check for Ginkgo test code quality is not applicable to this PR as it modifies only a Markdown documentation file, not test code.
Microshift Test Compatibility	✅ Passed	PR adds only Markdown documentation without Go test code or Ginkgo test patterns, so MicroShift Test Compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Pull request adds only Markdown documentation file; no Ginkgo e2e tests are present.
Topology-Aware Scheduling Compatibility	✅ Passed	Pull request adds only a troubleshooting runbook (SKILL.md) with diagnostic commands; contains no deployment manifests, operator code, or controllers, so topology-aware scheduling check does not apply.
Ote Binary Stdout Contract	✅ Passed	This PR adds only a Markdown documentation file with no Go code, binaries, or test code that could violate OTE binary stdout contracts.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR adds only Markdown documentation file, not Ginkgo e2e test code with IPv4 assumptions or external connectivity requirements.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/.claude-plugin/skills/Troubleshooting/Cluster-pools/SKILL.md:
- Line 73: The column header "STAGE" in the kubectl custom-columns output is
misleading because it maps to .status.installRestarts (a restart count); update
the header to reflect that field (for example change "STAGE" to
"INSTALL_RESTARTS" or "RESTARTS") while keeping the selector
.status.installRestarts unchanged so the command becomes -o
custom-columns="NAME:.metadata.name,INSTALLED:.spec.installed,INSTALL_RESTARTS:.status.installRestarts,PROVISION:.status.provisionRef.name".
- Around line 14-16: The fenced code block containing the path
"clusters/hosted-mgmt/hive/pools/<owner-namespace>/" should be labeled to
satisfy MD040 and enable syntax highlighting—edit the fence that wraps that
exact line and change the opening backticks from ``` to ```text so the block
becomes a text-labeled fenced code block.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e0474b00-0d3e-4eb5-8a88-d21e675eda7d

📥 Commits

Reviewing files that changed from the base of the PR and between 7032dee and 4e20444.

📒 Files selected for processing (1)

• .claude/.claude-plugin/skills/Troubleshooting/Cluster-pools/SKILL.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Add a language tag to this fenced code block.

Line 14 uses an unlabeled fence, which triggers markdownlint MD040 and hurts editor syntax highlighting.

Suggested fix

-```
+```text
 clusters/hosted-mgmt/hive/pools/<owner-namespace>/

</details>

<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion

🧰 Tools

🪛 markdownlint-cli2 (0.22.0)

[warning] 14-14: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.claude/.claude-plugin/skills/Troubleshooting/Cluster-pools/SKILL.md around
lines 14 - 16, The fenced code block containing the path
"clusters/hosted-mgmt/hive/pools/<owner-namespace>/" should be labeled to
satisfy MD040 and enable syntax highlighting—edit the fence that wraps that
exact line and change the opening backticks from ``` to ```text so the block
becomes a text-labeled fenced code block.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Rename STAGE column to match the actual field.

Line 73 labels .status.installRestarts as STAGE, but that field is a restart count. This can mislead triage.

Suggested fix

-  -o custom-columns="NAME:.metadata.name,INSTALLED:.spec.installed,STAGE:.status.installRestarts,PROVISION:.status.provisionRef.name"
+  -o custom-columns="NAME:.metadata.name,INSTALLED:.spec.installed,INSTALL_RESTARTS:.status.installRestarts,PROVISION:.status.provisionRef.name"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	-o custom-columns="NAME:.metadata.name,INSTALLED:.spec.installed,STAGE:.status.installRestarts,PROVISION:.status.provisionRef.name"
	-o custom-columns="NAME:.metadata.name,INSTALLED:.spec.installed,INSTALL_RESTARTS:.status.installRestarts,PROVISION:.status.provisionRef.name"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.claude/.claude-plugin/skills/Troubleshooting/Cluster-pools/SKILL.md at line
73, The column header "STAGE" in the kubectl custom-columns output is misleading
because it maps to .status.installRestarts (a restart count); update the header
to reflect that field (for example change "STAGE" to "INSTALL_RESTARTS" or
"RESTARTS") while keeping the selector .status.installRestarts unchanged so the
command becomes -o
custom-columns="NAME:.metadata.name,INSTALLED:.spec.installed,INSTALL_RESTARTS:.status.installRestarts,PROVISION:.status.provisionRef.name".

[openshift-merge-bot]

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

• The changed files don't match any pipeline_run_if_changed patterns
• All files match pipeline_skip_if_only_changed patterns
• No pipeline-controlled jobs are defined for the main branch

Use /test ? to see all available tests.

[openshift-merge-bot]

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

• The changed files don't match any pipeline_run_if_changed patterns
• All files match pipeline_skip_if_only_changed patterns
• No pipeline-controlled jobs are defined for the main branch

Use /test ? to see all available tests.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, Prucek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Prucek,deepsm007]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@deepsm007: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/breaking-changes	4e20444	link	false	/test breaking-changes

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.