Skip to content

Add SBEHealth Test-Version-Supports-OperationType-Tests TSG#318

Open
1008covingtonlane wants to merge 1 commit into
Azure:mainfrom
1008covingtonlane:tsg-sbehealth-test-version-supports-operationtype
Open

Add SBEHealth Test-Version-Supports-OperationType-Tests TSG#318
1008covingtonlane wants to merge 1 commit into
Azure:mainfrom
1008covingtonlane:tsg-sbehealth-test-version-supports-operationtype

Conversation

@1008covingtonlane

Copy link
Copy Markdown
Collaborator

What

Adds an Environment Validator remediation guide for the SBEHealth Test-Version-Supports-<OperationType>-Tests check (AzStackHci_SBEHealth_Test-Version-Supports-OperationType-Tests).

The check

This SBEHealth check runs during pre-update readiness (Test-AzStackHciSBEHealth, PreUpdate / PreUpdateJIT). It emits a SUCCESS-only informational skip-notice when the installed SBE version is older than 4.1, telling the operator that SBE health checks for the operation are only supported on version 4.1.x.x or later. It is informational (not a hard failure): it explains why the deeper SBE health tests were skipped.

What the guide covers

  • Where the notice appears (pre-update readiness output, on-box AzStackHciEnvironmentChecker EventID 17205 read via AdditionalData.Status / AdditionalData.Detail).
  • How to read the on-box result and confirm the SBE version.
  • How to bring the SBE to a supported version and re-run the pre-update / system health check (Invoke-SolutionUpdatePrecheck -SystemHealth + Get-SolutionUpdateEnvironment).

Notes

  • Lint Grade A (H1 = canonical check name, severity, where-it-appears, verify-the-fix, balanced PowerShell fences).
  • Prose follows the no spaced double-hyphen / em-dash convention.
  • Internally validated end-to-end (Grade A) via the SRE embedded-test harness against the exact module predicate. INTERNAL USE ONLY -- findings must be independently validated before action.

Environment Validator remediation guide for the SBEHealth
Test-Version-Supports-<OperationType>-Tests check
(AzStackHci_SBEHealth_Test-Version-Supports-OperationType-Tests).

The check emits a SUCCESS-only informational skip-notice, telling the operator
that SBE health checks for the operation are only supported when the SBE version
is 4.1.x.x or later. This guide explains where the notice appears, how to read the
on-box result, and how to bring the SBE version to a supported level.

Adds the TSG markdown and a README index entry.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new Environment Validator troubleshooting guide for the SBEHealth Test-Version-Supports-<OperationType>-Tests check (AzStackHci_SBEHealth_Test-Version-Supports-OperationType-Tests). The check is an informational, SUCCESS-only skip-notice emitted during pre-update readiness when the installed Solution Builder Extension (SBE) is older than version 4.1, indicating the SBE health tests were skipped. The guide explains where the notice appears (portal and on-box Event ID 17205), how to read the result and confirm the SBE version, and how to update the SBE and re-run the pre-update health check. It fits into the existing TSG/EnvironmentValidator supportability content set.

Changes:

  • Adds Troubleshooting-SBEHealth-Test-Version-Supports-OperationType-Tests.md documenting the check, its severity/meaning, detection, remediation, and verification.
  • Registers the new guide in the TSG/EnvironmentValidator/README.md table of contents.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
TSG/EnvironmentValidator/Troubleshooting-SBEHealth-Test-Version-Supports-OperationType-Tests.md New TSG describing the informational SBE version skip-notice, on-box detection via Event ID 17205, and SBE update/re-run remediation steps.
TSG/EnvironmentValidator/README.md Adds a table-of-contents link to the new troubleshooting guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants