Dynamic agent label with hw.arch.x86&&sw.os.linux&&ci.agent.dynamic doesn't work

[sophia-guo]

If no idle agent we'd like to trigger a dynamic agent for linux-x64 if specify label [hw.arch.x86&&sw.os.linux&&ci.agent.dynamic](https://ci.adoptium.net/label/hw.arch.x86&&sw.os.linux&&ci.agent.dynamic/). However no agent was triggered [hw.arch.x86&&sw.os.linux&&ci.agent.dynamic](https://ci.adoptium.net/view/Test_grinder/job/Grinder/8689/console) as expected. If the dynamic agents configuration has been changed?

[smlambert]

Believe it is unrelated to #4931 which is dockerAgents versus dynamicAgents, but assume it is more likely related to the Azure plugin being deprecated adoptium/infrastructure#3199

[sophia-guo]

adoptium/infrastructure#3199 mentioned Azure VM Agents plugin was left at version 825.v470cb_9e7361a_, which worked before? Feel like the configuration of Azure VM Agent Template has changed. Not sure as I don't have permission to see the configuration.

[karianna]

CC @sxa and @gdams - might need a closer look here

[sxa]

The ability to dynamically provision from Azure has been broken for quite some time so we have not been able to use it. 3199 will need some time on it in order to recover it. This was initially notices as part of adoptium/infrastructure#2988 (so dates back to March 2023) when the Alpine builds were dependent on it (we removed that dependency to resolve the problem)
Since the faulty plugin is being deprecated soon an alternative needs to be evaluated as per issue 3199 if the functionality needs to be reinstated for anything.

[sxa]

Also I'm not certain which version of the plugin we last used successfully. Updating it to the new version would be an option, but it would need analysis of the options and settings as per the warning in 3199.

I suggest we continue any further conversation in that issue.

[sxa]

Can I just check what the reason is for wanting this functionality enabled as it's not clear from this issue. We have previously had lots of agents available and we haven't moved any as part of the equinix migration yet. Are we seeing capacity issues somewhere or is something else driving this request?

[sxa]

And I guess a follow on question - could dynamic docker agents help with any problem here if we worked to enable them?