REQUEST: Repository maintenance on opentelemetry-operator

[pavolloffay]

Affected Repository

https://github.com/open-telemetry/opentelemetry-operator

Requested changes

GI GHA job for publishing operator bundle docker image failed https://github.com/open-telemetry/opentelemetry-operator/actions/runs/5807500252/job/15742453581#step:9:209

#8 exporting to image
#8 pushing layers 0.7s done
#8 ERROR: failed to push otel/opentelemetry-operator-bundle:0.82.0: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

otel/opentelemetry-operator-bundle is a new docker image and probably the dockerhub repository for image has to be created before it is pushed from GHA.

Purpose

Publish docker image otel/opentelemetry-operator-bundle from github action.

Expected Duration

forever

Repository Maintainers

• @open-telemetry/operator-maintainers

[pavolloffay]

@tigrannajaryan could you please help us here?

[tigrannajaryan]

@pavolloffay I created the repo and gave the bot user write permissions. Try now.

[pavolloffay]

Thanks the publish to dockerhub worked

https://hub.docker.com/r/otel/opentelemetry-operator-bundle/tags

But the publish to GHCR failed https://github.com/open-telemetry/opentelemetry-operator/actions/runs/5807500252/job/16143759304

#8 exporting to image
#8 pushing layers 0.6s done
#8 ERROR: failed to push ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle:0.82.0: unexpected status from HEAD request to https://ghcr.io/v2/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle/blobs/sha256:b442c2f2f9b50235eff522d1c61c63512787c59cd4b96bcdbec873afb9429e35: 403 Forbidden
------
 > exporting to image:
------
ERROR: failed to solve: failed to push ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle:0.82.0: unexpected status from HEAD request to https://ghcr.io/v2/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle/blobs/sha256:b442c2f2f9b50235eff522d1c61c63512787c59cd4b96bcdbec873afb9429e35: 403 Forbidden
Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle:0.82.0: unexpected status from HEAD request to https://ghcr.io/v2/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle/blobs/sha256:b442c2f2f9b50235eff522d1c61c63512787c59cd4b96bcdbec873afb9429e35: 403 Forbidden

Could you please create GHCR repo as well?

[pavolloffay]

@tigrannajaryan I have tried pushing locally but I don't have the auth

docker push ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle:0.82.0                                                                                                                                                                                                                  ploffay@fedora
The push refers to repository [ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator-bundle]
b2b1cc0d34fa: Preparing 
55a36813b856: Preparing 
bb242c50e1ed: Preparing 
unauthorized: unauthenticated: User cannot be authenticated with the token provided.

[tigrannajaryan]

@pavolloffay I am not sure what exactly needs to be done for GHCR. I have never created a repo for GHCR in the past.

[tigrannajaryan]

@open-telemetry/technical-committee anyone knows how GHCR works and what needs to be done here?

[trask]

@pavolloffay I don't recall needing any special permissions for repo-scoped GHCR: #164 (comment)

[jaronoff97]

@trask we're still observing this behavior, any updates here?

[pavolloffay]

here is another failed build https://github.com/open-telemetry/opentelemetry-operator/actions/runs/6172550151/job/16753034267#step:9:216

we (operator maintainers) cannot check the permissions in the repo settings

[trask]

@trask we're still observing this behavior, any updates here?

I'm not sure what's going on. It looks like other people have had similar issues: https://github.com/docker/build-push-action/issues?q=is%3Aissue+403+is%3Aclosed, I'd recommend looking over these to get ideas for what we can try / investigate next.

we (operator maintainers) cannot check the permissions in the repo settings

I'd recommend requesting elevated access to investigate this.

[tigrannajaryan]

@pavolloffay if there is anything specific that you want me to try I can do it. Otherwise as @trask said we can give you the necessary permissions temporarily if you need them to investigate yourself.

[pavolloffay]

Could you pleave give me admin rights for the next week and I will try to fix it and report back the findings.

[pavolloffay]

cc) @tigrannajaryan @trask

[pavolloffay]

cc) @arminru could you please help here?

[tigrannajaryan]

@pavolloffay you are an Admin now, sorry for the delay. Let me know when you are done so that I can remove the permission.

[pavolloffay]

Permissions can be removed. I haven't change any repo settings.

The publishing of image to GHCR was fixed by image name change (probably the old name was too long? ).

[tigrannajaryan]

@pavolloffay I removed your Admin rights. Closing the issue.