-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in v2.59.0 in az sig image-version create with cross-resource group image version creation #28700
Comments
Thank you for opening this issue, we will look into it. |
I have also come across this issue today while trying to create a VM image, it was working until I upgraded my CLI version today. $vmId = az vm get-instance-view -g resourcegroup -n image --query id az sig image-version create --resource-group resourcegroup --gallery-name gallery --gallery-image-definition definition --gallery-image-version 1.0.0 --managed-image $vmId Returns: (InvalidParameter) The gallery image version source id: removed must be specified in 'galleryImageVersion.properties.storageProfile.source.virtualMachineId'. |
Recently ran into this problem and had to change the --managed-image $vmid parameter to --virtual-machine $vmid this worked for me on 2.59 version of Cli |
Thanks @SimbasPride ! I confirm that using It would be helpful to improve the error message. |
This seems to also be causing issues with building images in Packer across subscriptions - hashicorp/packer-plugin-azure#403 Could be more of an issue with an API change within Azure? |
@SimbasPride that did the trick, thanks! |
EDIT: I was actually on 2.58.0. Updated and this workaround works perfectly. |
It appears there's been a regression in version 2.59.0 of the Azure CLI, where az sig image-version create fails when being passed the --managed-image flag, see the related failing CI run,[1] and the reported issue on the azure-cli project.[2] Because of this we are not able to create new versions for any of our VM templates. To fix this we can apply the workaround from the linked issue and pass the VM ID inside the `--virtual-machine` argument. [1] https://github.com/ubuntu/adsys/actions/runs/8677801641/job/23793927248 [2] Azure/azure-cli#28700
It appears there's been a regression in version 2.59.0 of the Azure CLI, where az sig image-version create fails when being passed the --managed-image flag, see the related [failing CI run](https://github.com/ubuntu/adsys/actions/runs/8677801641/job/23793927248 ), and the [reported issue](Azure/azure-cli#28700) on the azure-cli project. Because of this we are not able to create new versions for any of our VM templates. To fix this we can apply the workaround from the linked issue and pass the VM ID inside the `--virtual-machine` argument. I've tested this locally and successfully created a new image version with the change. Partly fixes UDENG-2528
Describe the bug
@Jing-song I'm getting a new error and I suspect this is due to #28627. The use case is that I create a temporary VM in a temporary resource group (rsc_tmp). I then create an image version in my permanent resource group (rsc_imgs).
Related command
Errors
Issue script & Debug output
N/A
Expected behavior
Used to work in v2.58.0. I confirmed by downgrading from v2.59.0 to v2.58.0 and the command succeeded again.
Environment Summary
azure 2.59.0
macOS
Additional context
No response
The text was updated successfully, but these errors were encountered: