Getting a warning for `getCacheEntry` and `reserveCache`

Hey All,

We are running into a new issue that seemed to start today with the caching action. We are getting the following errors when using the action:

Run actions/cache@v2
/usr/bin/docker exec  555b7c657bc5a13a07b0b7b85f74edb58118f96a5bccb8b1ccb99a3c83a88b42 sh -c "cat /etc/*release | grep ^ID"
Warning: getCacheEntry failed: {"$id":"1","innerException":null,"message":"The user 'System:ServiceIdentity;DDDDDDDD-DDDD-DDDD-DDDD-DDDDDDDDDDDD' is not authorized to access this resource.","typeName":"Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, Microsoft.TeamFoundation.Framework.Server","typeKey":"UnauthorizedRequestException","errorCode":0,"eventId":3000}

and

Post job cleanup.
/usr/bin/docker exec  555b7c657bc5a13a07b0b7b85f74edb58118f96a5bccb8b1ccb99a3c83a88b42 sh -c "cat /etc/*release | grep ^ID"
Warning: reserveCache failed: {"$id":"1","innerException":null,"message":"The user 'System:ServiceIdentity;DDDDDDDD-DDDD-DDDD-DDDD-DDDDDDDDDDDD' is not authorized to access this resource.","typeName":"Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, Microsoft.TeamFoundation.Framework.Server","typeKey":"UnauthorizedRequestException","errorCode":0,"eventId":3000}

This causes an issue in the steps that follow, as the expected cache is not there.

We started seeing the issue today but have not changed anything in the code.

Did something change within the filesystem or the permissions the container has?

[dhadka]

@javs-perez @davidcalhoun Thanks for reporting. We are aware of the issue and are working on applying a fix. I’ll provide periodic updates in this issue.

[dhadka]

We verified the fix and are rolling it out to the public AC servers. Expect to see the issue resolved in the next few minutes.