Closed camaier closed 3 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv.
@bilaakpan-ms, @avirishuv, could you take a look whether it is expected behavior?
I also noticed this. This is very dangerous behaviour. I almost lost a VM when I recreated it from snapshot. Existing snapshot was there with the same name and I didn't get any error/warning when I took a snapshot.
cc @Vaibhav-Agar who is going to take a look at this.
Just to update - the dev team has been looped in to implement a fix. I will try to provide an update soon on an ETA.
The Dev team is working on the fix. It is currently out for review.
The fix has been merged, and will be released to customers in the next PS release, on 12/29.
The fix has been released as part of the Azure Powershell 5.3.0 release.
Description
When trying to use the create to make a snapshot if you try to use the same name the CLI sometimes errors whereas the PowerShell never errors and it should. You cannot overwrite a snapshot because it's a read only so if someone tries to update a snapshot by running a new create or even an update there should be an error stating they can't update and/or create the snapshot because the name already exists.
Steps to reproduce
Environment data
Module versions
Debug output
Error output