Open ivansharamok opened 6 years ago
This error can be avoided if you specify the --cluster-name
parameter for az sf cluster create
as well.
I'm running into a similar issue, trying to add a VM Scale Set to a existing Service Fabric. Using az sf cluster node add -g resource_group -n cluster_name --number-of-nodes-to-add int --node-type 'type_name'
It produces the same results. msrest.exceptions : Operation returned an invalid status code 'Not Found'
Thank you for your feedback. We have added this to our backlog.
@tjprescott please assign this to @a-santamaria.
Had similar issue. Resolved after having same ClusterName
and ResourceGroupName
.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @QingChenmsft, @vaishnavk, @juhacket.
When deploying SF cluster using ARM template, the error may occur at the end of deployment if cluster name is not the same as resource group name. I used ARM templates provided in repo service-fabric-api-management to deploy SF cluster. I specified
clusterName
parameter that is different from resource group name that I used to deploy the cluster. Each time I use cluster name that differs from the resource group, I get the following error message at the end of deployment:It seems that at the end of cluster deployment CLI attempts to form a request to the cluster but it uses resource group name instead of the cluster name:
Environment summary