Skip to content

Commit b39d8de

Browse files
committed
Add new TSG for known issue with Test-AzStackHciARBStack
1 parent a1d29ce commit b39d8de

2 files changed

Lines changed: 22 additions & 1 deletion

File tree

TSG/Update/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,4 +30,5 @@
3030
* [Troubleshooting MSI Does Not Have Access to Subscription](../EnvironmentValidator/Troubleshooting-MSI-Does-Not-Have-Access-To-Subscription.md)
3131
* [2510 Update fails at CauPostVersionCheck](./CauPostVersionCheck-2510-23H2.md)
3232
* [Update preparation fails with 'Could not find part of the path' after 24H2 upgrade](./Update-preparation-fails-Could-not-find-part-of-the-file-path.md)
33-
* [2509 | Update Service terminated repeatedly by ALM due to high memory usage](./Update-Service-terminated-repeatedly-by-ALM.md)
33+
* [2509 | Update Service terminated repeatedly by ALM due to high memory usage](./Update-Service-terminated-repeatedly-by-ALM.md)
34+
* [Test-AzStackHciARBStack: Fails on Non-Numeric Az CLI Extension Versions](./Test-AzStackHciARBStack-NonNumericAzCLIExtensionVersions.md)
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
2+
# Test-AzStackHciARBStack Fails on Non-Numeric Az CLI Extension Versions
3+
4+
## Symptoms
5+
- Environment Validator fails in the Test-AzStackHciARBStack function with an error related to parsing az cli extension versions containing non-numeric characters (e.g., "1.0.0b1").
6+
- Error message similar to:
7+
Exception occurred (Test-AzStackHciARBStack): Cannot convert value "1.0.0b1" to type "System.Version". Error: "Input string was not in a correct format."
8+
9+
10+
## Summary
11+
A bug in the Environment Validator's Test-AzStackHciARBStack function causes it to fail when az cli extensions have non-numeric version strings (such as beta versions like "1.0.0b1").
12+
13+
**Applies to:**
14+
- Azure Stack HCI releases 2601, 2602, and 2603 only.
15+
- **Note:** From release 2604 onwards, the validator has been reworked and no longer checks extension versions in this way.
16+
17+
## Mitigation
18+
Refer to the main TSG for incompatible az cli extensions for mitigation steps:
19+
20+
- [UpdatePrerequisites Failure: Remove Incompatible Extensions](./UpdatePrerequisites-Failure-Remove-Incompatible-Extensions.md)

0 commit comments

Comments
 (0)