I suggest you ...

Start production/staging swapping if a machine is busy. Azure should support the swapping, especially in a worst-case scenario.

In a worst-case scenario, e.g. a workerrole is permanently on recycling (state busy), is it impossible to swap back to the previous release or to swap a new release from another stage (staging).

Two weeks ago, we had the problem that one workerrole was permanently recycling, because an database update for the next release. To publish the next release, we installed the new one on staging environment. Staging rans pretty well.
At this moment is the normal way is swap the releases production with staging. But this failed with error: The VIP swap operation failed. Detailed error message: VipSwap failed due to error in Fabric:[FaultType:UpdateInProgressFault Message:VIP swapping is not allowed during tenant updates].

This behavior of Azure is not helpful. The solution was to delete production and swap after that. In a production environment is it not acceptable to kill the production environment.

Kind regards

Tino Marx

4 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Tino Marx shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base