This job view page is being replaced by Spyglass soon. Check out the new job view.
PRperithompson: Check Kubelet is running with correct Windows Permissions
ResultFAILURE
Tests 7 failed / 681 succeeded
Started2021-03-10 11:17
Elapsed43m1s
Revision46738b7f482fb663f12b0d15dbacb621c13762fd
Refs 96616

Test Failures


Kubernetes e2e suite [sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should deny crd creation [Conformance] 5m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-api\-machinery\]\sAdmissionWebhook\s\[Privileged\:ClusterAdmin\]\sshould\sdeny\scrd\screation\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:86
Mar 10 11:46:03.505: waiting for the deployment status valid%!(EXTRA string=k8s.gcr.io/e2e-test-images/agnhost:2.28, string=sample-webhook-deployment, string=webhook-3748)
Unexpected error:
    <*errors.errorString | 0xc0035fca90>: {
        s: "error waiting for deployment \"sample-webhook-deployment\" status to match expectation: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:\"Available\", Status:\"False\", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, Reason:\"MinimumReplicasUnavailable\", Message:\"Deployment does not have minimum availability.\"}, v1.DeploymentCondition{Type:\"Progressing\", Status:\"True\", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, Reason:\"ReplicaSetUpdated\", Message:\"ReplicaSet \\\"sample-webhook-deployment-8977db\\\" is progressing.\"}}, CollisionCount:(*int32)(nil)}",
    }
    error waiting for deployment "sample-webhook-deployment" status to match expectation: deployment status: v1.DeploymentStatus{ObservedGeneration:1, Replicas:1, UpdatedReplicas:1, ReadyReplicas:0, AvailableReplicas:0, UnavailableReplicas:1, Conditions:[]v1.DeploymentCondition{v1.DeploymentCondition{Type:"Available", Status:"False", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, Reason:"MinimumReplicasUnavailable", Message:"Deployment does not have minimum availability."}, v1.DeploymentCondition{Type:"Progressing", Status:"True", LastUpdateTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, LastTransitionTime:v1.Time{Time:time.Time{wall:0x0, ext:63750973261, loc:(*time.Location)(0x99945c0)}}, Reason:"ReplicaSetUpdated", Message:"ReplicaSet \"sample-webhook-deployment-8977db\" is progressing."}}, CollisionCount:(*int32)(nil)}
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/apimachinery/webhook.go:845
				
				Click to see stdout/stderrfrom junit_10.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Networking Granular Checks: Services should function for client IP based session affinity: http [LinuxOnly] 5m43s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sNetworking\sGranular\sChecks\:\sServices\sshould\sfunction\sfor\sclient\sIP\sbased\ssession\saffinity\:\shttp\s\[LinuxOnly\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/network/networking.go:416
Mar 10 11:46:08.388: Unexpected error:
    <*errors.errorString | 0xc00024c250>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/network/utils.go:695
				
				Click to see stdout/stderrfrom junit_12.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should be able to up and down services 6m13s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sbe\sable\sto\sup\sand\sdown\sservices$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1015
Mar 10 11:46:04.979: failed to create new exec pod in namespace: services-9203
Unexpected error:
    <*errors.errorString | 0xc00024c250>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pod/resource.go:497
				
				Click to see stdout/stderrfrom junit_06.xml

Find in mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI mock volume storage capacity exhausted, late binding, no topology 6m28s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\smock\svolume\sstorage\scapacity\sexhausted\,\slate\sbinding\,\sno\stopology$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:958
Mar 10 11:46:06.546: failed to start pod
Unexpected error:
    <*errors.errorString | 0xc00024c250>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/csi_mock_volume.go:1011
				
				Click to see stdout/stderrfrom junit_20.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Downward API volume should provide container's cpu request [NodeConformance] [Conformance] 5m7s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sDownward\sAPI\svolume\sshould\sprovide\scontainer\'s\scpu\srequest\s\[NodeConformance\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Mar 10 11:46:06.514: Unexpected error:
    <*errors.errorString | 0xc0037c0c40>: {
        s: "expected pod \"downwardapi-volume-72ae69e7-83f9-4776-baaf-eead31543271\" success: Gave up after waiting 5m0s for pod \"downwardapi-volume-72ae69e7-83f9-4776-baaf-eead31543271\" to be \"Succeeded or Failed\"",
    }
    expected pod "downwardapi-volume-72ae69e7-83f9-4776-baaf-eead31543271" success: Gave up after waiting 5m0s for pod "downwardapi-volume-72ae69e7-83f9-4776-baaf-eead31543271" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_02.xml

Find downwardapi-volume-72ae69e7-83f9-4776-baaf-eead31543271 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] EmptyDir volumes should support (root,0777,default) [LinuxOnly] [NodeConformance] [Conformance] 5m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sEmptyDir\svolumes\sshould\ssupport\s\(root\,0777\,default\)\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Mar 10 11:46:07.166: Unexpected error:
    <*errors.errorString | 0xc00329d0b0>: {
        s: "expected pod \"pod-18dfbe17-fb90-41a1-828e-fca610b67bbb\" success: Gave up after waiting 5m0s for pod \"pod-18dfbe17-fb90-41a1-828e-fca610b67bbb\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-18dfbe17-fb90-41a1-828e-fca610b67bbb" success: Gave up after waiting 5m0s for pod "pod-18dfbe17-fb90-41a1-828e-fca610b67bbb" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_09.xml

Find pod-18dfbe17-fb90-41a1-828e-fca610b67bbb mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Subpath Atomic writer volumes should support subpaths with configmap pod with mountPath of existing file [LinuxOnly] [Conformance] 5m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sSubpath\sAtomic\swriter\svolumes\sshould\ssupport\ssubpaths\swith\sconfigmap\spod\swith\smountPath\sof\sexisting\sfile\s\[LinuxOnly\]\s\[Conformance\]$'
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Mar 10 11:46:06.494: Unexpected error:
    <*errors.errorString | 0xc002c46a90>: {
        s: "expected pod \"pod-subpath-test-configmap-tc56\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-configmap-tc56\" to be \"Succeeded or Failed\"",
    }
    expected pod "pod-subpath-test-configmap-tc56" success: Gave up after waiting 5m0s for pod "pod-subpath-test-configmap-tc56" to be "Succeeded or Failed"
occurred
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:742
				
				Click to see stdout/stderrfrom junit_05.xml

Find pod-subpath-test-configmap-tc56 mentions in log files | View test history on testgrid


Show 681 Passed Tests

Show 5056 Skipped Tests