You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You may be right, thanks for correction, @ahmedabu98
2024-04-24T12:03:53.0963029Z Please verify that you have permissions to write to the parent directory..
2024-04-24T12:03:53.0964903Z The configuration directory may not be writable. To learn more, see https://cloud.google.com/sdk/docs/configurations#creating_a_configuration
2024-04-24T12:03:53.0968080Z ERROR: (gcloud.auth.docker-helper) Could not create directory [/var/lib/kubelet/pods/573a1844-124b-4e12-bb0f-0325d0f3c3aa/volumes/kubernetes.io~empty-dir/gcloud]: Permission denied.
2024-04-24T12:03:53.0969612Z
2024-04-24T12:03:53.0970063Z Please verify that you have permissions to write to the parent directory.
2024-04-24T12:03:53.3953756Z #29 pushing layers 1.4s done
2024-04-24T12:03:53.3956208Z #29 ERROR: failed to push us.gcr.io/apache-beam-testing/github-actions/beam_python3.8_sdk:2.57.0-SNAPSHOT: error getting credentials - err: exit status 1, out: ``
2024-04-24T12:03:53.8953735Z ------
cc: @damccorm - do you remember if this suite never worked or the above error is an artifact of GHA migration?
We can reclassify this as part part of ARM backlog work.
@volatilemolotov could you put up a PR to make that change? Definitely seems like it is getting further.
@svetakvsundhar do you know what scope is missing? Given the normal postcommit python isn't failing, it might just be an issue with your service account specifically?
Activity
chamikaramj commentedon Apr 23, 2024
@tvalentyn do we have a good owner for this ?
ahmedabu98 commentedon Apr 24, 2024
I actually can't find a single green run since this test suite was created (back in September)
tvalentyn commentedon Apr 24, 2024
You may be right, thanks for correction, @ahmedabu98
cc: @damccorm - do you remember if this suite never worked or the above error is an artifact of GHA migration?
We can reclassify this as part part of ARM backlog work.
damccorm commentedon Apr 24, 2024
This was working last month - https://github.com/apache/beam/actions/workflows/beam_PostCommit_Python_Arm.yml?query=is%3Asuccess+branch%3Amaster+event%3Aschedule
damccorm commentedon Apr 24, 2024
Looks like it went flaky then permared around then
ahmedabu98 commentedon Apr 24, 2024
Ahh my apologies, I was looking at it through a
is:failurefiltervolatilemolotov commentedon Apr 25, 2024
So by removing
https://github.com/apache/beam/blob/master/.github/workflows/beam_PostCommit_Python_Arm.yml#L113
I get the test to move along but its still failing on my fork due to some permission with the Healthcare api.
Oauth scope is wrong or something:
https://github.com/volatilemolotov/beam/actions/runs/8820257015/job/24213449686#step:13:13113
damccorm commentedon Apr 25, 2024
@volatilemolotov could you put up a PR to make that change? Definitely seems like it is getting further.
@svetakvsundhar do you know what scope is missing? Given the normal postcommit python isn't failing, it might just be an issue with your service account specifically?
120 remaining items
github-actions commentedon Aug 22, 2026
Reopening since the workflow is still flaky
Amar3tto commentedon Aug 24, 2026
Stabilized
github-actions commentedon Sep 5, 2026
Reopening since the workflow is still flaky
github-actions commentedon Sep 23, 2026
Reopening since the workflow is still flaky
aIbrahiim commentedon Sep 25, 2026
The workflow is currently failing consistently on two integration tests because the CI service account is missing a couple of GCP IAM permissions:
Log:
google.api_core.exceptions.PermissionDenied: 403
Permission aiplatform.models.upload denied on resource
//aiplatform.googleapis.com/projects/apache-beam-testing/locations/us-central1
cc: @damccorm @Abacn @shunping
Abacn commentedon Sep 25, 2026
ack, fixing