Repository navigation
docs(storage): add stale iSCSI state reset guide - #363
Closed
Lucy Yan (nevsaynev) wants to merge 1 commit into
Closed
Lucy Yan (nevsaynev) wants to merge 1 commit into
Lucy Yan (nevsaynev) wants to merge 1 commit into
Conversation
Document the reset procedure for node-configuration retries while preserving safety gates and native fallbacks. Remove internal queries and update storage navigation. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The destructive reset procedure lacks required metadata, surface characterization, risk labeling, rollback coverage, and live validation.
4 open findings
What changed in this PR
Adds a storage TSG for diagnosing and resetting stale iSCSI state before retrying node configuration.
Changes:
- Documents diagnostics, safety gates, reset ordering, fallbacks, and verification.
- Adds the guide to storage navigation and inventory.
| File | Description |
|---|---|
TSG/Storage/README.md |
Adds navigation and inventory metadata. |
TSG/Storage/iSCSI/Troubleshoot-iSCSI-ResetStaleStateBeforeRetryingNodeConfiguration.md |
Adds the iSCSI troubleshooting guide. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| @@ -0,0 +1,355 @@ | |||
| # Reset Stale iSCSI State Before Retrying Node Configuration | |||
|
|
|||
| ## Section 1 - Metadata | |||
Comment on lines
+186
to
+188
| ### Mitigation Step 2: Reset the iSCSI state | ||
|
|
||
| Run 2a, 2b and 2c in order. Confirm that stored logins are gone before disconnecting sessions. |
Comment on lines
+1
to
+3
| # Reset Stale iSCSI State Before Retrying Node Configuration | ||
|
|
||
| ## Section 1 - Metadata |
| | Re-run fails at the same iSCSI step | Either error above | Repetition alone does not establish stale state | [Check reachability and configured paths](#powershell-validation-steps) | | ||
| | Unexpected sessions return after reboot | N/A | Stored logins replay at boot | [Reset iSCSI state, then re-run](#mitigation-step-1-record-the-current-state) | | ||
|
|
||
| ## Section 4 - Issue Validation |
Lucy Yan (nevsaynev)
marked this pull request as draft
October 7, 2026 19:03
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.
Summary
Adds guidance for diagnosing stale iSCSI state before retrying initial node configuration. The guide distinguishes network reachability and SAN access failures from stale state so a reset is not used for unrelated failures.
Uses the author's original TSG structure as requested, removes the internal Kusto section and its references, renumbers sections, and adds storage navigation. Preserves reset ordering (stored logins, live sessions, target portals), native fallbacks, removal-error handling, and verification.
Safety and validation
Review limitations
The author requested retaining the original template rather than the repository's current troubleshooting template. The article therefore lacks the current JSON metadata marker, canonical risk labels, full administrator-surface characterization, and explicit rollback coverage. Exact supported solution-version applicability is not established. Validation grade and automation readiness are not established; inventory records those gaps. Maintainer review is required before merge.
Impact
Documentation only. No runtime changes, dependencies, or migration.