Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in case you can help #5

Closed
eoq opened this issue Feb 26, 2024 · 3 comments
Closed

in case you can help #5

eoq opened this issue Feb 26, 2024 · 3 comments

Comments

@eoq
Copy link

eoq commented Feb 26, 2024

I found your youtube video on setting up the ARB with AKS which perfectly fit my scenario and your AKS+ARB script is very helpful!

I am on snippet 15 so very close but unfortunately I hit a snag and was wondering if you had any ideas.

If I run the following to setup the networking I get the below error:

az azurestackhci virtualnetwork create --subscription $SubscriptionId --resource-group $resource_group --extended-location name="/subscriptions/$SubscriptionId/resourceGroups/$resource_group/providers/Microsoft.ExtendedLocation/customLocations/$customloc_name" type="CustomLocation" --location $Location --network-type "Transparent" --name $customLocationNetworkName

Command group 'azurestackhci' is experimental and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Deployment failed. Correlation ID: 58671ff5-bf62-4a89-9836-781ccaf3193d. Supported OS Versions : 23H2 or higher. Node(s) not supported : amdcwazs381,amdcwazs380. : Not Supported

I am running 22H2.

In this case the name of the switch ($customLocationNetworkName) is the name of a logical HCI switch I created with New-MocVirtualNetwork. I tried to create the switch with the External switch name instead on the hope it would get farther but got this error:

HttpRequestPayloadAPISpecValidationFailed: HTTP request payload failed validation against API specification with one or more errors. Please see details for more information.

I am running 0.2.9 of the azurestackhci azure cli extension. (2.57.0 of the azure cli)

Any ideas on how I can progress short of upgrading to 23H2?

Thanks,
Ed

@eoq
Copy link
Author

eoq commented Mar 4, 2024

fyi, I asked MS support and they confirmed that Azure VM Management is not supported now (as of Feb 15 2024) and we need to move to 23H2 so the error I guess is correct. Instead of trying to hack around it we will do a fresh install of 23H2 (since an upgrade path from 22H2 to 23H2 isn't available yet - as of Mar 2024)

@eoq eoq closed this as completed Mar 4, 2024
@bfrankMS
Copy link
Owner

bfrankMS commented Mar 5, 2024

Hi,
apologies for the late reply. Correct Azure VM Management (aka ARBridge) was never released on 22H2 and functionality was switched of starting this Februrary - so yes it is deprecated on 22H2.
If you want to do Azure VM Management you need to switch to 23H2. The of it is included in the HCI setup:
image
i.e. you would not need these scripts anylonger. In fact they won't work as the az cli for Azure VM Management is different on 23H2

@Karl-WE
Copy link

Karl-WE commented Mar 7, 2024 via email

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

No branches or pull requests

3 participants