azure local
2 TopicsCannot run "Get-SolutionUpdate" or "Get-SolutionUpdateEnvironment" after updating to 2604
My Azure Local environment had been a bit out of date for the last few months so I was catching it up with the updates, stepping from 2602 to 2603 and then to 2604 last night. Since that update, when I run "Get-SolutionUpdate" or "Get-SolutionUpdateEnvironment" the command hangs for a few minutes and then eventually returns with something like the following: get-solutionUpdate : A WebException occurred while sending a RestRequest. WebException.Status: SendFailure on https://FQDN:4900/providers/Microsoft.Update.Admin/updateLocations?api-version=2022-08-01 + CategoryInfo : ConnectionError: (:) [Get-SolutionUpdate], SendFailureException + FullyQualifiedErrorId : SendFailureException,Microsoft.AzureStack.Lcm.PowerShell.GetSolutionUpdateCmdlet get-solutionUpdate : Object reference not set to an instance of an object. + CategoryInfo : InvalidOperation: (:) [Get-SolutionUpdate], NullReferenceException + FullyQualifiedErrorId : NullReferenceException,Microsoft.AzureStack.Lcm.PowerShell.GetSolutionUpdateCmdlet I have tried https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/Get-SolutionUpdate-GatewayTimeout.md to try resolve it as it seemed similar but it hasn't helped. Any idea what might be going on?Solved89Views0likes4CommentsTwo node Azure Local cluster updated to different versions
I'm not really sure how it's happened, but after trying to run an update against my Azure Local cluster, one of the two nodes has ended up at a higher version and now the update process is failing as it's detected that the nodes are at two different versions. Node 1 is at 26100.32690 Node 2 is at 26100.32522 Retrying the update process is failing as it's obviously detecting that the two nodes are at different update versions. Is there a way to update the node that has fallen behind to the the same version as the other?Solved106Views0likes2Comments