Fix bug conflicts when containers start simultaneously#3092
Merged
Conversation
The e2e containers' names of single mode and cluster mode would conflict when they start up simultaneously in Jenkins job.
kezhenxu94
added
bug
Member
Author
|
The e2e cluster test Jenkins jobs failed occasionally due to two main reasons, one of which is container name conflicts, which should be fixed by this patch, the other reason is timing out, and is under investigation |
Member
|
/run e2e |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Please answer these questions before submitting pull request
The e2e containers' names of single mode and cluster mode
would conflict when they start up simultaneously in Jenkins job.