Skip to content

Build Azure community gallery image ID instead of looking it up - #4334

Open
peterschmidt85 wants to merge 1 commit into
masterfrom
issue_4333_azure_community_gallery_image_ref
Open

peterschmidt85 wants to merge 1 commit into
masterfrom
issue_4333_azure_community_gallery_image_ref

Conversation

@peterschmidt85

Copy link
Copy Markdown
Contributor

Since azure-mgmt-compute 38.2.0, looking up a community gallery image uses an API version that Azure rejects for locations/communityGalleries, so every Azure VM fails to provision on installs that resolved the newer SDK. dstack only did the lookup to read the image ID, which is deterministic.

  • Build the community gallery image ID directly, so Azure provisioning works with any azure-mgmt-compute version.
  • If the image is not available in the region, skip the offer with a clear warning instead of an exception traceback.

Fixes #4333.

🤖 Generated with Claude Code

azure-mgmt-compute 38.2.0+ looks up community gallery images with an
API version that Azure rejects for locations/communityGalleries, so
every Azure VM failed to provision on installs with the newer SDK.
The lookup was only used to read the image ID, which is deterministic.

If the image is not available in the location, VM creation fails with
GalleryImageNotFound, which is now reported as a ComputeError.

Fixes #4333

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Azure provisioning fails with azure-mgmt-compute 38.2.0+

1 participant