wleese
commented
11 months ago Looking at the log snippets I posted, specifically:
"requestMetadata": {
"callerIp": "gce-internal-ip",
"requestAttributes": {
"auth": {},
"time": "2023-11-13T10:45:45.816012913Z"
},
"destinationAttributes": {},
"callerSuppliedUserAgent": "google-api-go-client/0.5 gke-metadata-server,gzip(gfe)"
},.. in relation to jib-maven-plugin, I assume this is a transitive call triggered by jib authenticating, rather than a direct call, as evident from the callerSuppliedUserAgent. In other words, we have no clear record of the request jib-maven-plugin made.
Xander-Polishchuk
Wallman
mpeddada1
maxmil
svametcalf
Environment:
Description of the issue: Every once in a while pushing a container fails with:
This happens with multiple different applications, with no discernible pattern.
Full stack trace, with debug logging:
Retrying usually results in success.
No changes were made to the build setup, or any changes known about the underlying infrastructure (GitLab Runners).
Expected behavior:
Container is published.
Steps to reproduce:
The problem happens every once in awhile.
Additional Information:
Looking at the code:
It seems that for some reason
googleCredentials.getAccessToken();returnsnull. I don't know why, but at the very least it's probably a good idea to catch the NPE.We also have some logs of how the request for authentication / the access token, was made:
And the response, while I don't have the entire payload, we do have some metadata: