Batch Explorer pool creation dialog does not show available custom images

[doug-case]

Describe the bug I have several images in region 'X' of my Azure subscription, as well as a Batch Service in the same region. Several weeks ago, I was able to create a new pool as a custom image and select an existing image.

To Reproduce Steps to reproduce the behavior:

1. Create a generalized image from a virtual machine
2. Ensure there is a batch service in the same region
3. Open Batch Explorer and try to create a new pool, selecting "Custom Image."

Expected behavior The Image dropdown in the custom image area should list the images that are found in the same region.

Screenshots

Logs(Click profile > View Logs > app.log, client.log) none

Version (please complete the following information):

• OS: Windows 10
• Batch Explorer: 2.7.0-stable.418

[bgklein]

Hi Doug, Batch's latest APIs no longer support custom image in favor of Shared Image Galleries. Due to this is v2.7.0 custom image support was dropped from BatchExplorer as it targets the latest versions.

You can download an older version of BatchExplorer which targets the old API's (specifically https://github.com/Azure/BatchExplorer/releases/tag/v2.6.0-stable.407) and turn off auto-update in the settings for a temporary mitigation. In the long term customers are being advised to migrate to Shared Image Galleries for better scale and performance.

[doug-case]

Thank you very much for the quick response, Brandon! Hope you and yours are doing well in this challenging time. -Doug

On Mon, Jun 15, 2020 at 2:45 PM Brandon Klein [email protected] wrote:

Hi Doug, Batch's latest APIs no longer support custom image in favor of Shared Image Galleries. Due to this is v2.7.0 custom image support was dropped from BatchExplorer as it targets the latest versions.

You can download an older version of BatchExplorer which targets the old API's (specifically https://github.com/Azure/BatchExplorer/releases/tag/v2.6.0-stable.407) and turn off auto-update in the settings for a temporary mitigation. In the long term customers are being advised to migrate to Shared Image Galleries for better scale and performance.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/BatchExplorer/issues/2189#issuecomment-644379651, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALVJ4NUPASKBDVHSF27HJDLRW2B7DANCNFSM4N6U6FMA .

-- Doug Case Senior Software Engineer | Royal Jay https://royaljay.com/

[czawlytko]

I am having the same issue on version 2.11.0-stable.541 but with a Azure Compute Gallery image. Should I convert to SIG?

edit: I'm seeing now Shared Image Galleries are now Azure Compute Galleries.