How can we force remove an application stuck in a deleting state with services in an unknown state

Hi @Ben Way
Thanks for reaching out, I am checking with the product team on this behavior. Please standby while I get back.

i am trying to put down all possible options that i could try

When an application is stuck in a deleting state in Azure Service Fabric, it can be challenging to remove it. Here are some steps you can try to force delete the application and its services:

1. Use the Service Fabric Explorer:
   • Open Service Fabric Explorer and connect to your cluster.
   • Navigate to the application and try to delete it from the UI.
2. Remove Application with PowerShell:
   • Use the Remove-ServiceFabricApplication cmdlet with the -Force parameter to force removal.

   
      Remove-ServiceFabricApplication -ApplicationName 'fabric:/YourAppName' -Force
   
   

3. Remove Service with PowerShell:
   • If the application cannot be removed, try removing the individual services using Remove-ServiceFabricService.

   
      Remove-ServiceFabricService -ServiceName 'fabric:/YourAppName/YourServiceName' -Force
   
   

4. Remove Replicas:
   • For the service that keeps restarting, try removing the replicas individually using Remove-ServiceFabricReplica.

   
      Get-ServiceFabricReplica -ServiceName 'fabric:/YourAppName/YourServiceName' | Remove-ServiceFabricReplica -ForceRemove
   
   

5. Disable the Node:
   • If the service keeps starting on a different node, try disabling the node temporarily.

   
      Disable-ServiceFabricNode -NodeName 'NodeName' -Intent RemoveNode
   
   

6. Restart Node:
   • Sometimes restarting the node where the service is stuck can help.
   • You can restart the node from the Azure portal or using PowerShell.
7. Clear Local State:
   • If the above steps do not work, you may need to manually clear the local state on the nodes.
   • Connect to each node via Remote Desktop and stop the Service Fabric host service, then manually delete the application data from the Service Fabric data folders.
8. Contact Support:
   • If none of the above steps work, you may need to contact Microsoft Support for assistance with your Service Fabric cluster.
9. Cluster Health Check:
   • Run a health check on your cluster to ensure there are no underlying issues causing the problem.

   
      Get-ServiceFabricClusterHealth
   
   

10. Check for Orphaned Applications:
    • Sometimes applications can become orphaned and not show up in management tools. Use the Get-ServiceFabricApplication cmdlet to list all applications and check for any that might be orphaned.
11. Use FabricClient API:
    • As a last resort, you can use the FabricClient API in a .NET application to try and remove the application programmatically.

Thanks @Prrudram-MSFT

I am anxious to hear if they have any suggestions.

I truly appreciate you outlining all of these options. Unfortunately, I have tried all of them and none have worked to actually remove the services or application.