409 Conflict, when deploying in Azure

[Hannu-Daniel]

When I deploy an application to the cloud to a cloud service, which already has an instance, I get the error message 409 Conflict. (This also happens, if there is just one instance in production and no instance in staging.)
In my mind, this should not happen. It should be possible to deploy to a cloud service, which only has instances running in production.

The stack trace from the eclipse log is:
!ENTRY WAEclipsePlugin 4 0 2013-10-18 10:16:53.303
!MESSAGE Error
!STACK 0
com.gigaspaces.azure.deploy.DeploymentException: Failed : HTTP error code : 409
Conflict
at com.gigaspaces.azure.deploy.DeploymentManager.deploy(DeploymentManager.java:239)
at com.gigaspaces.azure.wizards.WindowsAzureDeploymentJob.doTask(WindowsAzureDeploymentJob.java:133)
at com.gigaspaces.azure.wizards.WindowsAzureDeploymentJob.access$1(WindowsAzureDeploymentJob.java:131)
at com.gigaspaces.azure.wizards.WindowsAzureDeploymentJob$3.run(WindowsAzureDeploymentJob.java:121)
at java.lang.Thread.run(Unknown Source)
Caused by: com.gigaspaces.azure.rest.RestAPIConflictException: Failed : HTTP error code : 409
Conflict
at com.gigaspaces.azure.rest.WindowsAzureServiceImpl.validateResponse(WindowsAzureServiceImpl.java:109)
at com.gigaspaces.azure.rest.WindowsAzureServiceManagement.createDeployment(WindowsAzureServiceManagement.java:423)
at com.gigaspaces.azure.deploy.DeploymentManager.createDeployment(DeploymentManager.java:393)
at com.gigaspaces.azure.deploy.DeploymentManager.deploy(DeploymentManager.java:210)
... 4 more

[snallami]

I tried deploying to staging slot when there is existing deployment in production slot.
It worked for me without any issues.

I need more details from you to understand the issue you are facing.
If you are deploying to a slot (production or staging) and if that slot has existing deployment then 409 error is expected.
(We are planning new features which handles 409 conflicts errors in a better way - more details on this will be available publicly soon).

Can you please give me your exact repo steps? What is the service name and target environment you are selecting in eclipse publish wizard in both the cases?

[Hannu-Daniel]

Hi,

the exact steps I did was:

1. create an application in eclipse with a windows azure deployment project.
2. deploy this to a new cloud service (with new storage) - in staging environment
3. in the cloud service, swap the deployed from staging to production
4. deploy again to the same cloud service - to the staging environment (there aren't any instances now in the staging environment, because I swapped it to production) --> here I got the 409 conflict

is this the expected behavior?
if it is not the expected behavior, please tell me and I will provide information about the used cloud services.

[takekazuomi]

I got the 409 conflict too.

[snallami]

@Hannu-Daniel , Thanks for reporting with exact repo steps. We are now tracking the issue and will update the status of issue#3 once the fix is available for public.

[martinsawicki]

Try with the latest Eclipse plugin update (October release - v2.2.0) - there is now a checkbox in the publish wizard letting you override the existing deployment.