Pass conformance test #589

k82cn · 2019-02-14T11:13:34Z

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

Description:

Test kube-batch against conformance test after #588 and #520

asifdxtreme · 2019-04-11T06:27:08Z

cc @shivramsrivastava

k82cn · 2019-04-22T01:13:03Z

/sig scheduling

shivramsrivastava · 2019-04-24T11:28:30Z

There are about 239 conformance test cases in k8s.

Challenges to run these tests against kube-batch/volcano are as follows:

With the PR #596 in place we can now run these tests, but have the following challenge.

We need to disable default-scheduler. If we had an option to run kube-batch/volcano as a
default scheduler usign some flag, would be really nice to have feature.
This way we dont need to updated pods in the test case with the kube-batch/volcano 'scheduler-name'.

Will update more as i progress.

k82cn · 2019-04-24T12:01:00Z

@shivramsrivastava , would you remove the 200+ test case about? that's a really large comments to trace.

k82cn · 2019-04-24T12:03:09Z

We need to disable default-scheduler. If we had an option to run kube-batch/volcano as a
default scheduler usign some flag, would be really nice to have feature.

please refer to kube-batch's parameter:

      --scheduler-name string            volcano will handle pods whose .spec.SchedulerName is same as scheduler-name (default "kube-batch")

shivramsrivastava · 2019-04-24T13:03:41Z

@k82cn i have cut the lengthy comment.
Thanks, by setting the `flag '--scheduler-name' to 'default-scheduler'
i am able to schedule the pods.

shivramsrivastava · 2019-04-25T03:18:24Z

Summarizing 5 Failures:

[Fail] [k8s.io] KubeletManagedEtcHosts [It] should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/exec_util.go:101

[Fail] [sig-api-machinery] Aggregator [It] Should be able to support the 1.10 Sample API Server using the current Aggregator [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/apimachinery/aggregator.go:389

[Fail] [sig-scheduling] SchedulerPredicates [Serial] [It] validates resource limits of pods that are allowed to run  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:714

[Fail] [sig-scheduling] SchedulerPredicates [Serial] [It] validates that NodeSelector is respected if not matching  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:714

[Fail] [k8s.io] [sig-node] Events [It] should be sent by kubelets and the scheduler about pods scheduling and running  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/node/events.go:95

Ran 236 of 4082 Specs in 9400.328 seconds
FAIL! -- 231 Passed | 5 Failed | 0 Pending | 3846 Skipped
--- FAIL: TestE2E (9400.41s)
FAIL

Will look into these failure.
Looks good, with only five failures out of 236 test cases.

shivramsrivastava · 2019-04-25T03:20:45Z

These below two test cases are failing because of events not being sent from kube-batch.
These test cases use events to verify the test case result.
In these case either the pods success event or failure event is not sent to the api-server.

[Fail] [sig-scheduling] SchedulerPredicates [Serial] [It] validates resource limits of pods that are allowed to run  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:714

[Fail] [sig-scheduling] SchedulerPredicates [Serial] [It] validates that NodeSelector is respected if not matching  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:714

shivramsrivastava · 2019-05-02T10:09:05Z

The above two test case failure are addressed by the PR #839

shivramsrivastava · 2019-05-06T11:25:43Z

After the fix #839 this below conformance test is also passing.

$ ./e2e.test --provider=local --ginkgo.focus="should test kubelet managed /etc/hosts file" --kubeconfig=/home/root1/.kube/config 2>&1  | tee resource_limit_e2e_conformance.log
I0506 16:52:23.588895   22507 e2e.go:240] Starting e2e run "1333191c-e575-404d-9ac9-1e7edb84b5cf" on Ginkgo node 1
Running Suite: Kubernetes e2e suite
===================================
Random Seed: 1557141742 - Will randomize all specs
Will run 1 of 3962 specs

May  6 16:52:23.680: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:23.682: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
May  6 16:52:23.694: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
May  6 16:52:23.719: INFO: 13 / 13 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
May  6 16:52:23.719: INFO: expected 2 pod replicas in namespace 'kube-system', 2 are Running and Ready.
May  6 16:52:23.719: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start
May  6 16:52:23.725: INFO: 4 / 4 pods ready in namespace 'kube-system' in daemonset 'kube-proxy' (0 seconds elapsed)
May  6 16:52:23.725: INFO: 4 / 4 pods ready in namespace 'kube-system' in daemonset 'weave-net' (0 seconds elapsed)
May  6 16:52:23.725: INFO: e2e test version: v1.15.0-alpha.1.748+ea5be337dd0158
May  6 16:52:23.726: INFO: kube-apiserver version: v1.13.4
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[k8s.io] KubeletManagedEtcHosts 
  should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]
  /home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:696
[BeforeEach] [k8s.io] KubeletManagedEtcHosts
  /home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:149
STEP: Creating a kubernetes client
May  6 16:52:23.727: INFO: >>> kubeConfig: /home/root1/.kube/config
STEP: Building a namespace api object, basename e2e-kubelet-etc-hosts
May  6 16:52:23.756: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[It] should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]
  /home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:696
STEP: Setting up the test
STEP: Creating hostNetwork=false pod
STEP: Creating hostNetwork=true pod
STEP: Running the test
STEP: Verifying /etc/hosts of container is kubelet-managed for pod with hostNetwork=false
May  6 16:52:31.781: INFO: ExecWithOptions {Command:[cat /etc/hosts] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-pod ContainerName:busybox-1 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:31.781: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:31.882: INFO: Exec stderr: ""
May  6 16:52:31.882: INFO: ExecWithOptions {Command:[cat /etc/hosts-original] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-pod ContainerName:busybox-1 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:31.882: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:31.957: INFO: Exec stderr: ""
May  6 16:52:31.958: INFO: ExecWithOptions {Command:[cat /etc/hosts] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-pod ContainerName:busybox-2 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:31.958: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.037: INFO: Exec stderr: ""
May  6 16:52:32.038: INFO: ExecWithOptions {Command:[cat /etc/hosts-original] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-pod ContainerName:busybox-2 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:32.038: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.116: INFO: Exec stderr: ""
STEP: Verifying /etc/hosts of container is not kubelet-managed since container specifies /etc/hosts mount
May  6 16:52:32.116: INFO: ExecWithOptions {Command:[cat /etc/hosts] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-pod ContainerName:busybox-3 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:32.116: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.190: INFO: Exec stderr: ""
May  6 16:52:32.190: INFO: ExecWithOptions {Command:[cat /etc/hosts-original] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-pod ContainerName:busybox-3 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:32.190: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.279: INFO: Exec stderr: ""
STEP: Verifying /etc/hosts content of container is not kubelet-managed for pod with hostNetwork=true
May  6 16:52:32.279: INFO: ExecWithOptions {Command:[cat /etc/hosts] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-host-network-pod ContainerName:busybox-1 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:32.279: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.361: INFO: Exec stderr: ""
May  6 16:52:32.361: INFO: ExecWithOptions {Command:[cat /etc/hosts-original] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-host-network-pod ContainerName:busybox-1 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:32.361: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.439: INFO: Exec stderr: ""
May  6 16:52:32.439: INFO: ExecWithOptions {Command:[cat /etc/hosts] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-host-network-pod ContainerName:busybox-2 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:32.439: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.517: INFO: Exec stderr: ""
May  6 16:52:32.517: INFO: ExecWithOptions {Command:[cat /etc/hosts-original] Namespace:e2e-kubelet-etc-hosts-1456 PodName:test-host-network-pod ContainerName:busybox-2 Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false}
May  6 16:52:32.517: INFO: >>> kubeConfig: /home/root1/.kube/config
May  6 16:52:32.590: INFO: Exec stderr: ""
[AfterEach] [k8s.io] KubeletManagedEtcHosts
  /home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:150
May  6 16:52:32.590: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "e2e-kubelet-etc-hosts-1456" for this suite.
May  6 16:53:16.605: INFO: Waiting up to 30s for server preferred namespaced resources to be successfully discovered
May  6 16:53:16.665: INFO: namespace e2e-kubelet-etc-hosts-1456 deletion completed in 44.072077505s

• [SLOW TEST:52.939 seconds]
[k8s.io] KubeletManagedEtcHosts
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:691
  should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance]
  /home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:696
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSMay  6 16:53:16.686: INFO: Running AfterSuite actions on all nodes
May  6 16:53:16.686: INFO: Running AfterSuite actions on node 1

Ran 1 of 3962 Specs in 53.010 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 3961 Skipped
PASS

shivramsrivastava · 2019-05-06T11:38:06Z

So out of the five test case failures below four are passing after the fix in #843 #839.


[k8s.io] KubeletManagedEtcHosts [It] should test kubelet managed /etc/hosts file [LinuxOnly] [NodeConformance] [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/exec_util.go:101

[sig-scheduling] SchedulerPredicates [Serial] [It] validates resource limits of pods that are allowed to run  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:714

[sig-scheduling] SchedulerPredicates [Serial] [It] validates that NodeSelector is respected if not matching  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:714

[k8s.io] [sig-node] Events [It] should be sent by kubelets and the scheduler about pods scheduling and running  [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/node/events.go:95

But the below test case fails with both 'default-scheduler' as well as 'kube-batch'

[Fail] [sig-api-machinery] Aggregator [It] Should be able to support the 1.10 Sample API Server using the current Aggregator [Conformance] 
/home/root1/kubebapath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/apimachinery/aggregator.go:389

shivramsrivastava · 2019-05-15T17:18:49Z

Closing this issue since there is only one test case which is failing, mentioned above and the same is repeatedly failing with the default scheduler as well. Creating another issue for reporting the results.
refer #852

shivramsrivastava · 2019-05-15T17:19:37Z

/assign

k8s-ci-robot · 2019-05-15T17:19:39Z

@shivramsrivastava: GitHub didn't allow me to assign the following users: shivramsrivastava.

Note that only kubernetes-sigs members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot · 2019-05-15T17:52:37Z

@shivramsrivastava: What do you call an old snowman? Water.

In response to this:

/joke

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

shivramsrivastava · 2019-05-15T17:53:48Z

@asifdxtreme, @k82cn i am not able to close this issue.

k82cn · 2019-05-16T00:23:58Z

/close

Thanks for your contribution !

k8s-ci-robot · 2019-05-16T00:24:00Z

@k82cn: Closing this issue.

In response to this:

/close

Thanks for your contribution !

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 14, 2019

k82cn added this to the v0.4 milestone Feb 14, 2019

k82cn modified the milestones: v0.4, v0.5 Mar 12, 2019

k8s-ci-robot added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Apr 22, 2019

shivramsrivastava mentioned this issue May 2, 2019

Fixed the Pod failure event reason string for the k8s conformance tes… #839

Merged

shivramsrivastava mentioned this issue May 6, 2019

Need to address the event source properly when the '--scheduler-name' option is used. #842

Closed

k8s-ci-robot closed this as completed May 16, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Pass conformance test #589

Pass conformance test #589

k82cn commented Feb 14, 2019

asifdxtreme commented Apr 11, 2019

k82cn commented Apr 22, 2019

shivramsrivastava commented Apr 24, 2019 •

edited

Loading

k82cn commented Apr 24, 2019 •

edited

Loading

k82cn commented Apr 24, 2019

shivramsrivastava commented Apr 24, 2019 •

edited

Loading

shivramsrivastava commented Apr 25, 2019

shivramsrivastava commented Apr 25, 2019

shivramsrivastava commented May 2, 2019

shivramsrivastava commented May 6, 2019

shivramsrivastava commented May 6, 2019

shivramsrivastava commented May 15, 2019

shivramsrivastava commented May 15, 2019

k8s-ci-robot commented May 15, 2019

k8s-ci-robot commented May 15, 2019

shivramsrivastava commented May 15, 2019

k82cn commented May 16, 2019

k8s-ci-robot commented May 16, 2019

Pass conformance test #589

Pass conformance test #589

Comments

k82cn commented Feb 14, 2019

asifdxtreme commented Apr 11, 2019

k82cn commented Apr 22, 2019

shivramsrivastava commented Apr 24, 2019 • edited Loading

k82cn commented Apr 24, 2019 • edited Loading

k82cn commented Apr 24, 2019

shivramsrivastava commented Apr 24, 2019 • edited Loading

shivramsrivastava commented Apr 25, 2019

shivramsrivastava commented Apr 25, 2019

shivramsrivastava commented May 2, 2019

shivramsrivastava commented May 6, 2019

shivramsrivastava commented May 6, 2019

shivramsrivastava commented May 15, 2019

shivramsrivastava commented May 15, 2019

k8s-ci-robot commented May 15, 2019

k8s-ci-robot commented May 15, 2019

shivramsrivastava commented May 15, 2019

k82cn commented May 16, 2019

k8s-ci-robot commented May 16, 2019

shivramsrivastava commented Apr 24, 2019 •

edited

Loading

k82cn commented Apr 24, 2019 •

edited

Loading

shivramsrivastava commented Apr 24, 2019 •

edited

Loading