Application deployment is failing in newly deployed cluster

Garima Chauhan (HCL Technologies Ltd) 20 Reputation points • Microsoft External Staff

We tried deploying cluster and vmss in location other than resource group location which is west europe and tried deploying vmss &cluster in westus2. Resource deployment got successful but applictaion deployment is failing in cluster .We need help to understand th eissue .

  1. Manish Deshpande 7,010 Reputation points • Microsoft External Staff • Moderator

    Hello Garima,

    I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail .

  2. Garima Chauhan (HCL Technologies Ltd) 20 Reputation points • Microsoft External Staff

    Hello Manish

    👁 User's image

    We do have node with name "awrnode2" and all nodes are in healthy & up state.

  3. Hemalatha 14,525 Reputation points • Microsoft External Staff • Moderator

    Hello Garima

    Could you please provide the specific error message you are encountering during the application deployment failure?

    Additionally, are you receiving any errors from SF as well?

  4. Garima Chauhan (HCL Technologies Ltd) 20 Reputation points • Microsoft External Staff

    Hi @Jilakara Hemalatha

    We are not seeing any error during application deployment. Application deployment completed without any error, but application is showing error.

    Error in SF explorer for different roles in application .

    The Cluster Resource Manager was unable to find a placement for one or more of the Service's Replicas:

    Secondary replica could not be placed due to the following constraints and properties:

    TargetReplicaSetSize: 3

    Placement Constraint: (NodeType==asenode2)

    Parent Service: N/A

    Constraint Elimination Sequence:

    Down nodes count 0, Deactivated nodes count 0, Deactivating nodes count 0, NodesPendingClose count 0

    ({15 Service PlacementConstraint Nodes}, {5 ServiceTypeDisabled/NodesBlockListed Nodes})'s set union eliminated 20 possible node(s) for placement -- 0/20 node(s) remain (total of 15 nodes blocklisted for this service).

    Nodes Eliminated By Constraints:

    Set Union of {15 Service PlacementConstraint Nodes}, {5 ServiceTypeDisabled/NodesBlockListed Nodes}:

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/1 NodeName:_pwebnode2_1 NodeType:pwebnode2 NodeTypeName:pwebnode2 UpgradeDomain:1 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/1 NodeName:_awrnode2_1 NodeType:awrnode2 NodeTypeName:awrnode2 UpgradeDomain:1 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/0 NodeName:_awrnode2_0 NodeType:awrnode2 NodeTypeName:awrnode2 UpgradeDomain:0 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/2 NodeName:_awrnode2_2 NodeType:awrnode2 NodeTypeName:awrnode2 UpgradeDomain:2 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/3 NodeName:_asenode2_3 NodeType:asenode2 NodeTypeName:asenode2 UpgradeDomain:3 Deactivation Intent/Status: None/None

    Node is currently blocklisted for this particular Service Type

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/4 NodeName:_asenode2_4 NodeType:asenode2 NodeTypeName:asenode2 UpgradeDomain:4 Deactivation Intent/Status: None/None

    Node is currently blocklisted for this particular Service Type

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/0 NodeName:_pwebnode2_0 NodeType:pwebnode2 NodeTypeName:pwebnode2 UpgradeDomain:0 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/2 NodeName:_awebnode2_2 NodeType:awebnode2 NodeTypeName:awebnode2 UpgradeDomain:2 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/3 NodeName:_awebnode2_3 NodeType:awebnode2 NodeTypeName:awebnode2 UpgradeDomain:3 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/0 NodeName:_asenode2_0 NodeType:asenode2 NodeTypeName:asenode2 UpgradeDomain:0 Deactivation Intent/Status: None/None

    Node is currently blocklisted for this particular Service Type

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/4 NodeName:_awebnode2_4 NodeType:awebnode2 NodeTypeName:awebnode2 UpgradeDomain:4 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/1 NodeName:_asenode2_1 NodeType:asenode2 NodeTypeName:asenode2 UpgradeDomain:1 Deactivation Intent/Status: None/None

    Node is currently blocklisted for this particular Service Type

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/2 NodeName:_asenode2_2 NodeType:asenode2 NodeTypeName:asenode2 UpgradeDomain:2 Deactivation Intent/Status: None/None

    Node is currently blocklisted for this particular Service Type

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/2 NodeName:_pwebnode2_2 NodeType:pwebnode2 NodeTypeName:pwebnode2 UpgradeDomain:2 Deactivation Intent/Status: None/None

    Node is eliminated because of placement constraints

    --

    AllowStatefulWorkloads:true FaultDomain:fd:/0 NodeName:_awebnode2_0 NodeType:awebnode2 NodeTypeName:awebnode2 UpgradeDomain:0 Deactivation Intent/Status: None/ [Truncated]

  5. Deleted

    This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Sign in to comment

Answer accepted by question author

Manish Deshpande 7,010 Reputation points • Microsoft External Staff • Moderator

Hello Garima.

Your cluster and VM Scale Sets deployed successfully in the new location (westus2), but the fabric:/AzureStackEdge application is in an Error health state. The Cluster Resource Manager cannot place secondary replicas for partition [GUID REMOVED] because no nodes satisfy the placement constraint NodeType==awrnode2. Many nodes were eliminated (15 by placement constraints and 5 by ServiceTypeDisabled/NodesBlockListed), leaving zero suitable nodes for the required replica set size.

This is a common Service Fabric placement-constraint mismatch that occurs when an application’s service manifest expects a specific node type that is either missing, not scaled out, or unhealthy in the target cluster.

Recommended solution Check and align your cluster’s node types with the requirements of the AzureStackEdge application:

  1. Open Service Fabric Explorer → Nodes and verify:
    • Are any nodes listed with NodeType = awrnode2.
    • Are those nodes in Up and OK health state?
  2. If the awrnode2 node type is missing or has zero healthy nodes:
    • Update your cluster ARM template (or Bicep) to include a VM Scale Set with nodeTypeRef: "awrnode2".
    • Redeploy or scale the cluster to add the missing node type.
  3. Review the full constraint elimination sequence in the partition’s details for any additional block-listing or disabled service types.

Latest Update from the PG upon investigation :

The error we see is because of App issue and not related to SF runtime specific, it could be because of -

  1. Code package activation failures on the node (exe crashes at startup, DllMain failures, missing dependencies).
  2. Service package download / image store failures for that service type.
  3. Configuration issues – port conflicts, endpoint binding errors, invalid certs/secrets, missing resource-governance capacity.
  4. Repeated crashes / exit codes from the service host shortly after activation.
  5. Health check / safety check failures attributed to that partition on that node.

PG suggested to login into the Node and check if there any Cert expiry issue is with the App config not from the Engineering side.

Link :

https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-resource-manager-cluster-description#node-properties-and-placement-constraints
https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-understand-and-troubleshoot-with-system-health-reports

Thanks,
Manish.

0 comments No comments
Sign in to comment

1 additional answer

  1. kagiyama yutaka 3,685 Reputation points

    I think the naming primary just never settles after the cross‑region build… if SFX shows no steady primary, rebuild everything in one region; if that still fails, recreate the RG to clear the metadata.

    0 comments No comments
    Sign in to comment
Sign in to answer

Your answer