-
Notifications
You must be signed in to change notification settings - Fork 115
Kubernetes node e2e tests #109
Comments
Related with hyperhq/hyperd#572. Update: PR hyperhq/hyperstart#283 fixed user problem. |
latest node e2e result:
|
With kubernetes/kubernetes#40804 and latest hyperd, there are still 3 failed test cases:
|
Filed hyperhq/hyperd#577 for |
Four more network related issues. |
I run node e2e test in my local environment twice, this is the best result:
The first one will be fixed by #145 , so ideally, we have only one case fail. |
@Crazykev Whith version of kubernetes are you running? kubernetes master? |
@feiskyer Yep, a brand new kubernetes master with
|
Only one conformance tests failed with latest master now, which should be fixed after #161. |
All conformance tests passed now. Closing it. |
Node e2e test (conformance) results of latest frakti on master branch + hyperd 0.8.0.1 + Kubernetes v160-beta.4.
The test command is:
The node e2e result is:
In the 9 failed issues:
6 issues related mound volume with specified mode, which seems buggy in hyperd.
1 issue is know issue of hyperd hyperhq/hyperd#564
2 issues still have no clear root cause found
cc @feiskyer
The text was updated successfully, but these errors were encountered: