Add Storage TSG: physical disks stuck in verification (CanPool=False) due to a wedged Health Service#333
Open
1008covingtonlane wants to merge 3 commits into
Conversation
… due to a wedged Health Service New disks can stay CanPool=False with CannotPoolReason 'Verification in progress' that never clears because the cluster Health Service (the Health resource in the SDDC Group) is wedged and its supportability verification never completes. The same disk pools fine in a healthy cluster. This is a focused companion to Troubleshoot-Storage-PhysicalDiskCanPoolFalse.md (which covers the general CannotPoolReason decision tree). It adds the Health-Service deep-dive: confirm the block is cluster-side, inspect the Health Service and its Providers parameter, then remediate least-risk-first (Step A: fail the Health group over; Step B, support-assisted: restore the Providers list vs a healthy same-build peer), then claim and rebalance the disks. Covers discover -> debug -> mitigate with an at-a-glance box, an 8-surface admin discoverability table, safety gates on every state-changing step, and a glossary. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4fd8e523-73e9-4f9c-851a-7c5c1a8b08a0
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a focused Storage TSG for disks stuck in Health Service verification.
Changes:
- Adds diagnosis and remediation procedures.
- Includes guarded provider restoration and disk pooling steps.
- Adds the guide to the Storage index.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
TSG/Storage/Troubleshoot-Storage-PhysicalDiskVerificationStuck.md |
Adds the troubleshooting guide. |
TSG/Storage/README.md |
Links the new guide. |
Fixes from the Copilot PR review on Azure#333: - Step 2: do not recommend moving a disk into another PRODUCTION cluster as a diagnostic (a clean disk can be auto-claimed there); frame as already-observed evidence or use a spare/non-production cluster. - Step B backup: create C:\Temp and stop on backup failure before continuing, so the internal-parameter edit never proceeds without a verified rollback copy. - Step B completeness gate: prove completeness against an independently recorded peer count (not "larger than the broken set"), reject placeholders, and require every entry to be a unique GUID before writing. - Step B reinitialize: re-run Step A's full guarded failover procedure instead of a duplicated, weaker block that omitted the node/storage-job gates. - Step C: validate each intended serial matches exactly one eligible disk (per serial, not in aggregate) and reject duplicate serials. Lint A; all rewritten PowerShell blocks parse clean. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4fd8e523-73e9-4f9c-851a-7c5c1a8b08a0
Merge the pre-move inspection/gate and the failover blocks into a single continuous block so the variables it derives ($hs, $upNodes, $originalOwner) are always in scope, and it is copy-paste-robust if run on its own. The gate is now enforced in code (throws if a node is down or a storage job is running) instead of relying on the operator reading the previous block's output. Addresses the review note on out-of-order execution. Lint A; block parses clean. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4fd8e523-73e9-4f9c-851a-7c5c1a8b08a0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a focused Storage TSG for the scenario where new, clean, vendor-supported disks stay
CanPool=FalsewithCannotPoolReason = Verification in progressthat never clears, because the cluster Health Service (theHealthresource in theSDDC Group) is wedged and its supportability verification never completes. The tell is that the same disk pools normally in a different, healthy cluster.This is a companion to the existing
Troubleshoot-Storage-PhysicalDiskCanPoolFalse.md, which covers the generalCannotPoolReasondecision tree. That guide'sVerification in progressstep is "wait and recheck"; this guide picks up where that stalls forever, and adds the Health-Service deep-dive.Contents
Providerscluster parameter vs a healthy same-build peer.SDDC Groupover; single-node usesStop/Start-ClusterResource); Step B (support-assisted, gated) restore theProviderslist from a healthy same-build peer with a backup, hard-stops, and round-trip verification; Step C claim the eligible disks and rebalance.Validation
Built and graded with an internal tsg-forge harness. The Health Service provider-config remediation loop (Step A + Step B) was validated end-to-end on a lab S2D cluster: baseline healthy providers, injected an incomplete set, detected it, restored + failed the group over, revalidated. Report card: Grade A, 5/5 usability panel across 13 reader personas, 8/8 admin discoverability surfaces. The downstream
CanPoolchain is described from the source support case and the Microsoft LearnCannotPoolReason/ verification model.No PII: all cluster names, serials, and provider GUIDs are placeholders.