This job view page is being replaced by Spyglass soon. Check out the new job view.
PRmgdevstack: Promote e2e "verifying service's sessionAffinity for ClusterIP and NodePort services" to Conformance
ResultFAILURE
Tests 15 failed / 228 succeeded
Started2019-08-29 17:27
Elapsed2h47m
Revision
Buildergke-prow-ssd-pool-1a225945-m2ml
Refs master:47214d67
76443:fc84ff19
pod2177016f-ca82-11e9-8e62-42f740094b73
infra-commit993ea44b3
job-versionv1.17.0-alpha.0.902+aa9485ba95edce-dirty
pod2177016f-ca82-11e9-8e62-42f740094b73
repok8s.io/kubernetes
repo-commitaa9485ba95edcee80d8774cc68656568d36ab7df
repos{u'k8s.io/kubernetes': u'master:47214d672d8fd6b7db4fee0c9176e79a418fab04,76443:fc84ff19464f8fb45653d491acb2e10db0dbacf9', u'k8s.io/release': u'master'}
revisionv1.17.0-alpha.0.902+aa9485ba95edce-dirty

Test Failures


Kubernetes e2e suite [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance] 10m56s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sGuestbook\sapplication\sshould\screate\sand\sstop\sa\sworking\sapplication\s\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:23:50.772: Frontend service did not start serving content in 600 seconds.
test/e2e/kubectl/kubectl.go:2149
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-cli] Kubectl client Guestbook application should create and stop a working application [Conformance] 11m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sGuestbook\sapplication\sshould\screate\sand\sstop\sa\sworking\sapplication\s\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:34:39.785: Frontend service did not start serving content in 600 seconds.
test/e2e/kubectl/kubectl.go:2149
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should be able to switch session affinity for NodePort service [Conformance] 2m14s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sbe\sable\sto\sswitch\ssession\saffinity\sfor\sNodePort\sservice\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:45:54.181: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should be able to switch session affinity for NodePort service [Conformance] 2m28s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sbe\sable\sto\sswitch\ssession\saffinity\sfor\sNodePort\sservice\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:43:38.767: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_02.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should be able to switch session affinity for service with type clusterIP [Conformance] 2m15s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sbe\sable\sto\sswitch\ssession\saffinity\sfor\sservice\swith\stype\sclusterIP\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:41:05.248: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should be able to switch session affinity for service with type clusterIP [Conformance] 2m25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\sbe\sable\sto\sswitch\ssession\saffinity\sfor\sservice\swith\stype\sclusterIP\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:43:27.273: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should have session affinity work for NodePort service [Conformance] 2m17s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\shave\ssession\saffinity\swork\sfor\sNodePort\sservice\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:36:40.104: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should have session affinity work for NodePort service [Conformance] 2m22s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\shave\ssession\saffinity\swork\sfor\sNodePort\sservice\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 19:38:58.387: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should have session affinity work for service with type clusterIP [Conformance] 2m7s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\shave\ssession\saffinity\swork\sfor\sservice\swith\stype\sclusterIP\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 18:55:17.828: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Services should have session affinity work for service with type clusterIP [Conformance] 2m17s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sServices\sshould\shave\ssession\saffinity\swork\sfor\sservice\swith\stype\sclusterIP\s\[Conformance\]$'
test/e2e/framework/framework.go:698
Aug 29 18:53:00.420: Affinity should hold but didn't.
test/e2e/framework/service/affinity_checker.go:55
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-windows] [Feature:Windows] SecurityContext RunAsUserName should be able create pods and run containers with a given username 21s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\s\[Feature\:Windows\]\sSecurityContext\sRunAsUserName\sshould\sbe\sable\screate\spods\sand\srun\scontainers\swith\sa\sgiven\susername$'
test/e2e/windows/security_context.go:36
Aug 29 19:05:41.307: Error creating Pod
Unexpected error:
    <*errors.StatusError | 0xc001631b80>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "Pod \"run-as-username-aa402404-a73e-4695-9919-c51a8c9ca9ca\" is invalid: [spec.containers[0].securityContext.windowsOptions.runAsUserName: Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters, spec.securityContext.windowsOptions.runAsUserName: Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters]",
            Reason: "Invalid",
            Details: {
                Name: "run-as-username-aa402404-a73e-4695-9919-c51a8c9ca9ca",
                Group: "",
                Kind: "Pod",
                UID: "",
                Causes: [
                    {
                        Type: "FieldValueInvalid",
                        Message: "Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters",
                        Field: "spec.containers[0].securityContext.windowsOptions.runAsUserName",
                    },
                    {
                        Type: "FieldValueInvalid",
                        Message: "Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters",
                        Field: "spec.securityContext.windowsOptions.runAsUserName",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 422,
        },
    }
    Pod "run-as-username-aa402404-a73e-4695-9919-c51a8c9ca9ca" is invalid: [spec.containers[0].securityContext.windowsOptions.runAsUserName: Invalid value: "ContainerAdministrator": runAsUserName's User length must be under 21 characters, spec.securityContext.windowsOptions.runAsUserName: Invalid value: "ContainerAdministrator": runAsUserName's User length must be under 21 characters]
occurred
test/e2e/framework/pods.go:80
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-windows] [Feature:Windows] SecurityContext RunAsUserName should be able create pods and run containers with a given username 5m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-windows\]\s\[Feature\:Windows\]\sSecurityContext\sRunAsUserName\sshould\sbe\sable\screate\spods\sand\srun\scontainers\swith\sa\sgiven\susername$'
test/e2e/windows/security_context.go:36
Aug 29 19:05:19.361: Error creating Pod
Unexpected error:
    <*errors.StatusError | 0xc001e948c0>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "Pod \"run-as-username-e41ad832-9c26-4608-bb19-dc82137ecb06\" is invalid: [spec.containers[0].securityContext.windowsOptions.runAsUserName: Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters, spec.securityContext.windowsOptions.runAsUserName: Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters]",
            Reason: "Invalid",
            Details: {
                Name: "run-as-username-e41ad832-9c26-4608-bb19-dc82137ecb06",
                Group: "",
                Kind: "Pod",
                UID: "",
                Causes: [
                    {
                        Type: "FieldValueInvalid",
                        Message: "Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters",
                        Field: "spec.containers[0].securityContext.windowsOptions.runAsUserName",
                    },
                    {
                        Type: "FieldValueInvalid",
                        Message: "Invalid value: \"ContainerAdministrator\": runAsUserName's User length must be under 21 characters",
                        Field: "spec.securityContext.windowsOptions.runAsUserName",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 422,
        },
    }
    Pod "run-as-username-e41ad832-9c26-4608-bb19-dc82137ecb06" is invalid: [spec.containers[0].securityContext.windowsOptions.runAsUserName: Invalid value: "ContainerAdministrator": runAsUserName's User length must be under 21 characters, spec.securityContext.windowsOptions.runAsUserName: Invalid value: "ContainerAdministrator": runAsUserName's User length must be under 21 characters]
occurred
test/e2e/framework/pods.go:80