-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
none driver: setting CNI times out the tests #8601
Labels
area/cni
CNI support
kind/bug
Categorizes issue or PR as related to a bug.
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Comments
This was referenced Jun 30, 2020
medyagh
added
the
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
label
Jul 7, 2020
medyagh
changed the title
CNI test times out on none driver
determine if CNI should be allowed on None Driver
Jul 7, 2020
medyagh
changed the title
determine if CNI should be allowed on None Driver
none driver: setting CNI times out the tests
Jul 7, 2020
here is example log file from the timed out none test:
|
medyagh
added
the
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
label
Jul 7, 2020
Fixed by #8664 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/cni
CNI support
kind/bug
Categorizes issue or PR as related to a bug.
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
after this PR #8545 was merged the none driver been timing out. and we ended up up skipping it in none driver, we should figure out if it is not usable for none driver, then not allow the user to set it.
The text was updated successfully, but these errors were encountered: