Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[issue] - 02-templates.html - poi-map-app image push fails to internal registry #7

Open
eformat opened this issue Apr 26, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@eformat
Copy link

eformat commented Apr 26, 2023

first pipeline run (post backatage app creation) fails with

�[36mINFO�[0m[0327] Adding exposed port: 8080/tcp                
�[36mINFO�[0m[0327] CMD ["/bin/sh",  "-c",  "envsubst < /usr/share/nginx/html/assets/env.template.js > /usr/share/nginx/html/assets/env.js && exec nginx -g 'daemon off;'"] 
�[36mINFO�[0m[0327] Pushing image to image-registry.openshift-image-registry.svc:5000/eformat/poi-map-app:latest 
error pushing image: failed to push to destination image-registry.openshift-image-registry.svc:5000/eformat/poi-map-app:latest: HEAD https://image-registry.openshift-image-registry.svc:5000/v2/eformat/poi-map-app/blobs/sha256:91f8b0f1d49131295d9a6ca3e9762af47ebb8a9d4d2b44ac5f7f76d2a389190c: unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)

Screenshot from 2023-04-27 08-15-33

@eformat
Copy link
Author

eformat commented Apr 26, 2023

reran the pipeline .. and it worked .. so flake ??

poi-map-app-pipeline-233l3b-build-and-push-pod step-build-and-push INFO[0142] Pushing image to image-registry.openshift-image-registry.svc:5000/eformat/poi-map-app:latest 
poi-map-app-pipeline-233l3b-build-and-push-pod step-build-and-push INFO[0143] Pushed image to 1 destinations 

@joshix
Copy link
Collaborator

joshix commented Apr 27, 2023

in two tests of the three components, I wasn't able to reproduce this pipeline image push failure.

One possible difference is that I used an existing GH->Backstage->OpenShift authn to test in just a new project/ns, jxrht-gh2 and jxrht-gh2-2, respectively.

We can watch for repeats in other new accounts, and I can create a new GH id to re-test.

@joshix
Copy link
Collaborator

joshix commented Apr 27, 2023

Reproduced this 401 from container reg on brand-new users first frontend pipeline run at push to reg step; Rosa1 cluster; user/ns jxrht-gh2. Succeeded on manual re-run of pipeline run from OCP web console -> PipelineRuns -> PipelineRun details.

@joshix joshix added the bug Something isn't working label May 3, 2023
@ryanj
Copy link
Contributor

ryanj commented May 3, 2023

I'm currently stuck on this issue. I've re-run the pipeline 5 times in the ryanj2 project, and it fails each time.

I would love to track down a cause or a fix for this issue before the workshop

@joshix
Copy link
Collaborator

joshix commented May 3, 2023

repro'd ryanj's trouble user jxrht-gh2 project jxrht-gh2-3 cluster ROSA2 pipeline poi-map-app-pipeline

@ryanj
Copy link
Contributor

ryanj commented May 3, 2023

This pipeline build failure comes up 100% of the time when testing these templates using clusters from demo.redhat.com. I have not been able to consistently reproduce it on a ROSA cluster until today.

I really hope this does not come up as an issue during our workshop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants