Operator CI is broken reporting docker login failures
See original GitHub issueDescribe the bug
The Operator CI workflow is reporting login failures while running docker login
.
Version
17.0.1
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
A few examples:
- https://github.com/keycloak/keycloak/runs/5890690824?check_suite_focus=true
- https://github.com/keycloak/keycloak/runs/5892142025?check_suite_focus=true
- https://github.com/keycloak/keycloak/runs/5887096987?check_suite_focus=true
Anything else?
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Troubleshooting CI/CD - GitLab Docs
GitLab provides several tools to help make troubleshooting your pipelines easier. This guide also lists common issues and possible solutions.
Read more >Overview | Docker Documentation
This page contains information on: How to diagnose and troubleshoot Docker Desktop issues; Check the logs; Find workarounds for common problems ...
Read more >Troubleshooting Operator issues - OpenShift Documentation
An install plan for a subscription has failed. Default OpenShift Container Platform cluster Operators are managed by the Cluster Version Operator (CVO) and...
Read more >cicd - gitlab job failed - image pull failed - Stack Overflow
After some trial and errors, me and our team figured out the issue is due to the runner failed to use service account...
Read more >Docker Log Collection Troubleshooting Guide - Datadog Docs
Status: no errors · The required port (10516) for sending logs to Datadog is being blocked. · Your container is using a different...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For visibility: I’m working to have a fix on top by EOD.
I’d suggest we revert the breaking change and reintroduce it with ok-to-test in a separate PR. Alternative solution would be to run OLM tests only nightly. Or somehow avoid using Quay whatsoever. WDYT, @andreaTP?