[BUG] Failed to get list of supported orchestrators
See original GitHub issueDescribe the bug Code below raised exception “Microsoft.Rest.Azure.CloudException: Failed to get list of supported orchestrators”
private Version getVersionList(IAzure client, IKubernetesCluster cluster )
{
// ...
var kubernetesVersions = client.KubernetesClusters.ListKubernetesVersions(cluster.Region);
// ...
}
It started failing several days ago.
Exception or Stack Trace
Microsoft.Rest.Azure.CloudException: Failed to get list of supported orchestrators
at Microsoft.Azure.Management.ContainerService.Fluent.ContainerServicesOperations.ListOrchestratorsWithHttpMessagesAsync(String location, String resourceType, Dictionary'2 customHeaders, CancellationToken cancellati onToken)
at Microsoft.Azure.Management.ContainerService.Fluent.ContainerServicesOperationsExtensions.ListOrchestratorsAsync(IContainerServicesOperations operations, String location, String resourceType, CancellationToken can cellationToken)
at Microsoft.Azure.Management.ContainerService.Fluent.KubernetesClustersImpl.ListKubernetesVersionsAsync(Region region, CancellationToken cancellationToken)
at Microsoft.Azure.Management.ResourceManager.Fluent.Core.Extensions.Synchronize[TResult](Func'l function)
at Microsoft.Azure.Management.ContainerService.Fluent.KubernetesClustersImpl.ListKubernetesVersions(Region region)
at Microsoft.Azure.Management.ContainerService.Fluent.KubernetesClustersImpl.Microsoft.Azure.Management.ContainerService.Fluent.IKubernetesClusters.ListKubernetesVersions(Region region)
at XxxCompany.YyyProduct.Core.Services.UpgradeKubernetesControlnane.getLatestMinorVersionList(IAzure client, IKubernetesCluster cluster) in /home/vsts/work/l/s/XxxCompany.YyyProduct.Core/Services/NpgradeKubernetesControlPlane.cs
at XxxCompany.YyyProduct.Core.Services.UpgradeKubernetesControlnane.Upgrade(IHangfireOutput output, IAzure client, String clusterName) in /home/vsts/work/1/s/XxxCompany.YyyProduct.Core/Services/UpgradeKubernetesControlPlane.cs
at XxxCompany.YyyProduct.Core.Systemlobs.MaintainKubernetesClusterslob.RunWaitForNodeRoolsToBeCreated(PerformContext context, IHangfireOutput hangfireOutput, IAzure azureClient, MaintainKubernetesClustersjobParameters input) in /home/vsts/work/l/s/XxxCompany.YyyProduct.Core/Systemlobs/MaintainKubernetesClustersJob.cs
Expected behavior Should get valid kubernetes versions
Additional context Here is solution for the problem: https://docs.microsoft.com/en-us/answers/questions/932362/failed-to-get-list-of-supported-orchestrators-erro.html
It works when invoke the API directly, but the parameter “resource-type” is not public accessible with the Fluent library.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Failed to get list of supported orchestrators Error in Azure ...
Hi Team, I am using the below API to get the AKE Kubernetes versions list.
Read more >[BUG] Agent v7.40.0 fails to get hostname from Kubernetes ...
Solution 1: Make sure the Agent is able to access the Kubelet API. This is usually handled automatically by our Helm chart/Operator. @JamieSinn ......
Read more >Solution to Azure Kubernetes Service version not supported ...
I got this error while deploying a new Azure Kubernetes Cluster. ... [az aks get-versions] command to get the supported version list in...
Read more >Frequently Encountered Orchestrator Errors
This error is occasionally encountered when trying to get assets or queue items during workflow execution. This happens due to a Transport Layer...
Read more >Central Troubleshooting - Operations Orchestration
Go to Studio and search for the flow, operation, or configuration item with the given UUID in either the OO content packs or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@xinfli The linked issue above https://github.com/Azure/azure-libraries-for-net/issues/1302 should be the workaround for you, for this problem.
Currently it is “maintenance mode”, we would still fix bugs (but this one seems do not have a satisfactory fix, as the API as it is no longer work, and if we change the parameters the API behavior would change).
It is likely get to “deprecated” in this year, and you may need to plan the migration sooner or later.
@weidongxu-microsoft Yes, I think it’s caused by changes of the API behavior, maybe the Azure SDK for .NET can handle it.
But migration to the new lib is too expensive for us, we changed the code to use API directly to fix the problem in our code.
And what does “maintenance mode” mean? will bug like this be fixed?
Thanks!