Azure Resource Mover

Question

Azure Resource Mover

John Sparks 111

Hi All, I did some testing with Azure Resource mover and now how a couple of RGs that I cant remove. I also have two moves that I cannot discard (I assume this is why I cant remove the Resource Groups).

If I go into Resource Mover> Across Regions I see the two moves, both set to "prepare pending". I've tried removing them, and discarding the move, and I just get errors.

The Discard error for the first one shows as
Error Id MoveCollectionResolveRequired
Error message The operation has failed as dependency resolution is required for one or more move resources.
Possible Causes: One or more resources in the move collection has dependencies that are yet to be resolved.
Recommended Action: Resolve dependencies and retry the operation.
Error Id MoveCollectionDiscardOperationInvalidState
Error message
The resources: [
"/subscriptions/608df3f9-de3f-4e3e-8b52-0a42f937c3d6/resourceGroups/RG01-eastus/providers/Microsoft.Network/virtualNetworks/jdbvnet01",
"PreparePending"
] are not in a valid state to execute the Discard operation.
Possible Causes: To be able to execute Discard operation, the resources should be in a state 'Commit pending' as Discard is an optional step after you initiate the move.
Recommended Action: Ensure that the following operations - prepare, initiate move are completed before trying 'Discard'.

Thanks!

1 answer

Your answer

Answer 1

Prrudram-MSFT 27,971

Hello @John Sparks ,

Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.

I understand you have tried to discard the resources out of a resource collection made for test move scenario. If the current resource collection state is "Prepare Pending" and if you want to discard, you should be able to do so. However, here the VNet "jdbvnet01" is with validation failures which is going to cause blockers for any further action.

Error message
The resources: [
"/subscriptions/608df3f9-de3f-4e3e-8b52-0a42f937c3d6/resourceGroups/RG01-eastus/providers/Microsoft.Network/virtualNetworks/jdbvnet01", "PreparePending"] are not in a valid state to execute the Discard operation.

Try to fix the validation errors on the Vnet "jdbvnet01" or remove it from the move collection and then try discarding the move collection.

If you still see any issues, please tag me in your comment. I will help to debug further.

Hope this helps!
Please "Accept as Answer" and Upvote if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

John Sparks 111 Reputation points

2022-12-06T10:15:36.773+00:00

Hi Prrudram,

Thanks for your message.

Since doing the move I had deleted the "Jdbvnet01" Vnet and recreated it. Deleting the recreated Vnet allowed me to delete the move request for that resource. Looks like its maintaining resource links by name and not by ID...

I've now managed to delete the move requests and the RGs that Resource Mover created.

Now getting

"There is a transient error or the move collection may have been deleted. Refresh and retry. If the error persists, try adding the resources again." On the resource mover "across regions" page.
Prrudram-MSFT 27,971 Reputation points

2022-12-12T07:08:37.037+00:00

Hi @John Sparks ,

This is more of a temp error, it will usually go away upon a retry. Did you refresh the page/logout and log back in and still see that error? If the issue still exists, we better check on the browser network traces for clues as this error doesn't have any clues on why it fails.

Here is a reference link that has details on how to capture the browser network traces
Let me know what you see in traces, specially in network/console tab under dev tools in browser
John Sparks 111 Reputation points

2022-12-12T12:15:45.347+00:00

I’ve tried to delete the RG again but, although it says its deleting it, it doesn’t.

When I look at the RG there doesn’t appear to be anything in it, however when I got to delete the RG it shows this in it.

MoveCollection-uks-eus-eus2
Microsoft.Migrate/moveCollections
East US 2

Is this why it doesn’t get deleted?

I’ll run a browser network trace if this is not why.
Prrudram-MSFT 27,971 Reputation points

2022-12-15T09:17:49.057+00:00
@John Sparks ,
It appears the move collection is blocking the deletion of RG here. In case removal of move collection is failing from portal with the transient errors, you can try the PowerShell method as mentioned here Remove a collection (PowerShell) and if that succeeds, you can try the deletion of RG.
Let me know how that goes.

Remove-AzResourceMoverMoveCollection -ResourceGroupName "RG-MoveCollection-demoRMS" -MoveCollectionName "PS-centralus-westcentralus-demoRMS"
John Sparks 111 Reputation points

2022-12-15T09:45:18.433+00:00

Hi, Tried this and it failed as it believes there is something in the collection. I cant see anything

PS /home/john> Remove-AzResourceMoverMoveCollection -ResourceGroupName "ResourceMoverRG-uksouth-eastus-eus2" -MoveCollectionName "MoveCollection-uks-eus-eus2"
WARNING: Remove-AzResourceMoverMoveCollection_Delete is not found. The most similar Azure PowerShell command is:
Remove-AzResourceMoverMoveCollection
Remove-AzResourceMoverMoveCollection_Delete: Deletion of move collection is not allowed when there are move resources present in it.
Possible Causes: The move collection has move resources present in it.
Recommended Action: In Portal open 'Azure Resource Mover' > Across regions > Select SubscriptionId: 608df3f9-de3f-4e3e-8b52-0a42f937c3d6, Source Region: uksouth, Target Region: eastus > delete all the resources, and then retry deleting the Resource group.
For PowerShell please use remove resource cmdlet and delete all resources and then try deleting move collection or resource group. Please follow documentation https://go.microsoft.com/fwlink/?linkid=2145903.
Prrudram-MSFT 27,971 Reputation points

2022-12-22T06:52:11.14+00:00

@John Sparks ,

Try checking under the overview blade in "Move across region dashboard". Delete if there are recovery services vaults created as part of Move job.

Manually delete the move collection, and Site Recovery resources created for the VM move:

Review the resources in resource group ResourceMoverRG-<sourceregion>-<target-region>-<metadataRegionShortName>.
Check that the VM and all other source resources in the move collection have been moved/deleted. This ensures that there are no pending resources using them.

Delete these resources:
The move collection name is movecollection-<sourceregion>-<target-region>-<metadata-region>.
The cache storage account name is resmovecache<guid>
The vault name is ResourceMove-<sourceregion>-<target-region>-GUID.

If still blocks you, I would suggest filing a support case with Azure Technical Support.
John Sparks 111 Reputation points

2022-12-23T10:44:58.273+00:00

Thanks very much for the support, but unfortunately none of these answers fixed the issue. It was a test subscription as part of a larger project, so I've cancelled the subscription.

I havent got time at the moment to replicate the case but from my experience, the Azure Resource Mover leaves artifacts after a move that are difficult (impossible?) to remove. I wont be recommending using this until I've had time to try it again.

Thanks

Share via

Azure Resource Mover

1 answer

Your answer