E2E test failing with error from step CreateNPMCluster

[SRodi]

2025/01/13 09:04:07 creating cluster "runner-e2e-netobs-1736759038" in resource group "runner-e2e-netobs-1736759038"...
    runner.go:38: 
        	Error Trace:	/home/runner/work/retina/retina/test/e2e/framework/types/runner.go:38
        	            				/home/runner/work/retina/retina/test/e2e/retina_e2e_test.go:58
        	Error:      	Received unexpected error:
        	            	did not expect error from step CreateNPMCluster but got error: failed to finish the create cluster request: PUT https://management.azure.com/subscriptions/***/resourceGroups/runner-e2e-netobs-1736759038/providers/Microsoft.ContainerService/managedClusters/runner-e2e-netobs-1736759038
        	            	--------------------------------------------------------------------------------
        	            	RESPONSE 409: 409 Conflict
        	            	ERROR CODE: EtagMismatch
        	            	--------------------------------------------------------------------------------
        	            	{
        	            	  "code": "EtagMismatch",
        	            	  "details": [
        	            	    {
        	            	      "code": "Unspecified",
        	            	      "message": "rpc error: code = FailedPrecondition desc = Etag mismatched"
        	            	    }
        	            	  ],
        	            	  "message": "Operation is not allowed: Another operation is in progress",
        	            	  "subcode": "PutManagedClusterAndComponents_FailedPrecondition"
        	            	}
        	            	--------------------------------------------------------------------------------
        	Test:       	TestE2ERetina
--- FAIL: TestE2ERetina (17.93s)
FAIL
FAIL	github.com/microsoft/retina/test/e2e	17.954s
FAIL
Error: Process completed with exit code 1.

Link to execution: https://github.com/microsoft/retina/actions/runs/12743698406/job/35514489856

[ritwikranjan]

The issue doesn't seem to be persistent. I was not able to reproduce it either locally or through the workflow. During my research i got the impression that the issue is linked to the azure sdk however i don't understand why the error is a 4xx rather than 5xx. Anyways, i couldn't find any issue with client side configuration. We can keep an eye out for this error and see if it occurs again or get frequent.