Cache: 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?
javs-perez
All 12 comments
Thank you! I just started seeing this and thought it was something I did wrong. Also getting this exact same issue over here, even on projects that were working fine before, where I haven't touched the workflow config.
davidcalhoun
on 26 Oct 2020
@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
on 26 Oct 2020
@dhadka thank you!
javs-perez
on 26 Oct 2020
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.
dhadka
on 26 Oct 2020
Should be resolved for everyone now.
dhadka
on 26 Oct 2020
@dhadka Thank you for the fast work! Confirmed that it's working great from here now.
davidcalhoun
on 26 Oct 2020
Seeing a separate but I presume related issue:
{"$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}
jamierumbelow
on 26 Oct 2020
@jamierumbelow When did that workflow run? We haven't seen this error in our telemetry since about 17:09 UTC (about an hour and a half ago).
dhadka
on 26 Oct 2020
@dhadka About two hours ago. Let me rerun...
jamierumbelow
on 26 Oct 2020
Yep, that fixed it. Thanks!
jamierumbelow
on 26 Oct 2020
Works for us as well! Thank you.
tovbinm
on 27 Oct 2020
This worked for us, closing the issue. Thank you @dhadka!
javs-perez
on 27 Oct 2020
Related issues
hugovk
路
6Comments
FacetGraph
路
3Comments
gladhorn
路
4Comments
jcornaz
路
4Comments
ConorSheehan1
路
4Comments
Most helpful comment
@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.