-
Notifications
You must be signed in to change notification settings - Fork 113
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
e2e: Stick to a stable OCP version #727
Conversation
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 9683337432Details
💛 - Coveralls |
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 9694174743Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Signed-off-by: Andrea Panattoni <[email protected]>
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 9694858457Details
💛 - Coveralls |
Thanks for your PR,
To skip the vendors CIs use one of:
|
/hold Still seeing errors like:
|
Pull Request Test Coverage Report for Build 9871400678Details
💛 - Coveralls |
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks for your PR,
To skip the vendors CIs use one of:
|
In OCP 4.16, dockercfg secret moved from the form of "serviceaccount:xyz" to "<token>:xyz". Use bash left trim operator (`${<variable>#<prefix>}`) to make it explicit. Signed-off-by: Andrea Panattoni <[email protected]>
Thanks for your PR,
To skip the vendors CIs use one of:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
A number of jobs in the OCP end-to-end lane are failing due to a failure in the operator deployment.
Logs show an error during the pull of the image from the internal registry:
job-logs.txt
Sticking to a stable version of OCP can mitigate the risk of flaky lanes.
cc @SchSeba