Closed DevOpsAzurance closed 2 months ago
Hi @DevOpsAzurance thank you for your report! This repo is specific for the ADO agent and according to the description your issue is related to the VMSS agent extension. Could you please open an issue in Developer Community to get the right eyes on your issue?
I'm closing this one as external - feel free to ask any other questions or let us know if it's still relevant for you.
What happened?
We have been using VMSS Pools for the past 6 months. When we initially provisioned the integration between ADO and VMSS, the service account created for the integration took over the VMSS and installed two extensions:
After about 6 months of running fine it has started failing with:
Network is not an issue, as it is open outbound, but seems like the SAS token/key that was used when the CSE was installed is expired. Since that extension setting is protected, not a public setting, we have no idea what the blob uri is or the sas for it. We cannot create a new SAS token, since we don't know the storage account, nor have access to it, most likely it is an MS storage account. As such we would not be able to use a managed identity either as, it is not our storage account.
This seems to be an issue with the Microsoft.VisualStudio.Services.TeamServicesAgent extension that it depends on this private blob, versus a public one like the public settings in that extension.
Versions
Windows 2022
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 2022
Version controll system
Git
Relevant log output