e2e: retry on "transport: missing content-type field" error #2651
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Madhu-1
approved these changes
Nov 18, 2021
|
/retest ci/centos/upgrade-tests-cephfs |
yati1998
approved these changes
Nov 18, 2021
|
/retest ci/centos/upgrade-tests-cephfs |
This did not get picked up the 1st time 🤔 |
|
@Mergifyio rebase |
✅ Branch has been successfully rebased |
nixpanic
force-pushed
the
e2e/retry-content-type
branch
from
852b7c3
to
849bf79
Compare
|
added DNM since #2658 needs to be merged first for the ci to work @Mergifyio refresh |
✅ Pull request refreshed |
|
@Mergifyio rebase |
✅ Branch has been successfully rebased |
nixpanic
force-pushed
the
e2e/retry-content-type
branch
from
849bf79
to
2a51329
Compare
|
@Mergifyio rebase |
nixpanic
force-pushed
the
e2e/retry-content-type
branch
from
2a51329
to
032b506
Compare
✅ Branch has been successfully rebased |
mergify
bot
added
ci/skip/e2e
nixpanic
removed
component/testing
mergify
bot
added
component/testing
nixpanic
removed
component/testing
mergify
bot
added
component/testing
nixpanic
removed
component/testing
The e2e sometimes fail getting objects like PVCs from the Kubernetes API
server, and log the following error:
Error getting pvc "rbd-6940" in namespace "rbd-694": rpc error: code = Unknown desc = OK: HTTP status code 200; transport: missing content-type field
By checking the error message, and initiating a retry on this failure,
CI jobs should fail less regulary.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
nixpanic
force-pushed
the
e2e/retry-content-type
branch
from
032b506
to
72e6ec5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The e2e sometimes fail getting objects like PVCs from the Kubernetes API
server, and log the following error:
By checking the error message, and initiating a retry on this failure,
CI jobs should fail less regulary.
See-also: #2622 (comment)
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)
/retest all: run this in case the CentOS CI failed to start/report any testprogress or results