Deleting an agent raises an exception instead of telling the user agent cannot be deleted.

[Rinaldo DiGiorgio]

I try to file bugs but I can't seem to get access to Jira

I am using Azure from AWS for the mesos project. I launch windows builds at Azure since Microsoft is good at that and AWS is feature poor in that area.

When  there is an issue with an agent,  I cannot delete the agent. I get the following exception stack trace. The agent eventually goes away so maybe it is not that important. I have seen similar issues with the mesos plugin. The Azure plugin also goes into a spinning cursor condition if you click on the log file link on the agent's page.  Perhaps one should know that that a spinning cursor  may mean no data has arrived for the log file. I would have put some type of message in there like waiting for communication port ...

A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.

Stack trace

java.io.IOException: Error occurred while deleting node, jenkins will try to clean up node automatically after some time.  
 Root cause: com.microsoft.windowsazure.exception.ServiceException: ConflictError: Windows Azure is currently performing an operation with x-ms-requestid 14618d684fa1a3f3ab5f66eac252fd93 on this deployment that requires exclusive access.