Queries around scalet set

Question

We use uniform orchestration mode scale set as self hosted agent for azure pipelines

1. Why it is showing No? at what scenario it shows NO? below highlighted

2. at what scenario these goes unhealthy status
3. what needs to be done to keep same instances with name always so that azure pipeline would pick same instance and would be easy for trouble shooting

Answer 1

@sns

I just reproed the same issue for you:

Latest Model goes to NO status immediately once you connect your Azure Devops pipeline to this particular VMSS.

In general scenarios , if any changes are done at the VMSS config end and if those are not propagated to the instance level - that's where the Latest Model will show as NO - which also indicates that those instances needs to have the latest changes which are applied on the VMSS level.

To make to YES , you need to select the instances & click on Upgrade !!

Couple of options which I was thinking to use the same instances with name:

-> In the Azure Devops pipeline , you can unselect the option of "Automatically tear down virtual machines after every use " , so that those VMSS instances will not get deleted !

-> Try to use the VMSS with Flexible more

Will continue to do more research for you , but you can start with those options for now...

Regards,

Shiva.