Build VM step fails with "A capture_name_prefix, managed_image_resource_group_name or shared_image_gallery_destination must be specified"

[System-Admins-ath]

It get the following error trying to build a windows2022 runner

I'm using the latest commit.

Any ideas?

[cengelenVW]

It could be caused by the same change in actions/runner-images as #59 and #60

[System-Admins-ath]

It could be caused by the same change in actions/runner-images as #59 and #60

Thanks! Yeah I see that the capture_name_prefix is not appended. So all I need to do is wait? :)

[erik-de-bont]

@YannickRe , @System-Admins-ath and @cengelenVW

I am currently working to update the repo so that the build vm will work again. The actions/runner-images repo has changed their image-build script so that packer will generate a managed image in stead of a vhd. The vhd option used non-managed azure disks to create, which Microsoft is not supporting anymore.

In the current pipeline the vhd will be converted to a managed image, which then can be migrated to a Gallery VM or directly attached to a scaleset. So in the new situation the convertion task to a managed image of the pipeline is now obsolete, since a managed image will be build straight away by packer in stead of a vhd.

I am already able in my fork to generate images again (as managed image), and already modified the code to place the VM in the gallery. Testing will take some time, since generating images takes time.

[erik-de-bont]

I have changed the code and got it to work again in my fork. I have create pull request .https://github.com/YannickRe/azuredevops-buildagents/pull/62 to merge the new code into the repo

[Kockieee]

Great job! When will the pull request be completed because i also need this to work again :)

[YannickRe]

It has been merged in #63