Поделиться через

blogtest333- Resolved

  • Статья

Final Update: Tuesday, 19 July 2016 10:39 UTC

We've confirmed that all systems are back to normal with no customer impact as of. Our logs show the incident started on and that during the hours that it took to resolve the issue X% of customers experienced.

  • Upon further investigation, the issue is observed to be permissions not synchronized between Agent Queue and Agent Pool between M100 and M101 deployment. 
  • Currently the impact is limited only in TFS Ring1 SUs which had M102 deployed.
  • Hotfix has been identified and active PR is available. We will do the deployment across all SU's to mitigate the issue.

We understand that customers rely on VS Team Services as a critical service and apologize for any impact this incident caused.

Sincerely,

test

  • The hot fix to resolve the issue has been successfully deployed to all SU's. The issue has been verified post deployment.
  • Team will be working on fixing the agent pool permission sync for all the agent pools created in M100 and M101.
  • Users should now be able to manually queue requests again the Agent pools created between M100 and M101 without any issues.

Customer Impact:

Users should be able to queue builds and should not see any failure with error "no agents could be found matching the capabilities".