This job view page is being replaced by Spyglass soon. Check out the new job view.
PRpacoxu: add --system-reserved support for swap
ResultFAILURE
Tests 13 failed / 837 succeeded
Started2022-05-03 08:16
Elapsed1h8m
Revision
Builder3430c708-cab9-11ec-848e-0a0ffdffe05b
Refs master:e7a2ce75
105271:520d2ad3
control_plane_node_os_imageubuntu-2004-focal-v20200423
infra-commitbdfbe71a3
job-versionv1.25.0-alpha.0.22+20b712cdede0d5
kubetest-version
repok8s.io/kubernetes
repo-commit20b712cdede0d57bc9bfab45a28df08a25c77e3a
repos{u'k8s.io/kubernetes': u'master:e7a2ce75e5df96ba6ea51d904bf2735397b3e203,105271:520d2ad3fb0a97368a2e549a18a1cdf9226bafc1', u'k8s.io/release': u'master'}
revisionv1.25.0-alpha.0.22+20b712cdede0d5
worker_node_os_imageubuntu-2004-focal-v20200423

Test Failures


Kubernetes e2e suite [sig-cli] Kubectl client Simple pod should return command exit codes execing into a container with a failing command 1m28s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-cli\]\sKubectl\sclient\sSimple\spod\sshould\sreturn\scommand\sexit\scodes\sexecing\sinto\sa\scontainer\swith\sa\sfailing\scommand$'
test/e2e/kubectl/kubectl.go:506
May  3 08:59:44.030: Expected
    <int>: 1
to equal
    <int>: 42
test/e2e/kubectl/kubectl.go:512
				
				Click to see stdout/stderrfrom junit_16.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Networking Granular Checks: Pods should function for node-pod communication: http [LinuxOnly] [NodeConformance] [Conformance] 5m9s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sNetworking\sGranular\sChecks\:\sPods\sshould\sfunction\sfor\snode\-pod\scommunication\:\shttp\s\[LinuxOnly\]\s\[NodeConformance\]\s\[Conformance\]$'
test/e2e/framework/framework.go:652
May  3 09:03:11.752: Error dialing HTTP node to pod failed to find expected endpoints, 
tries 39
Command curl -g -q -s --max-time 15 --connect-timeout 1 http://10.64.3.93:8083/hostName
retrieved map[]
expected map[netserver-1:{}]
vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_19.xml

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


Kubernetes e2e suite [sig-network] Networking Granular Checks: Services should function for service endpoints using hostNetwork 2m37s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sNetworking\sGranular\sChecks\:\sServices\sshould\sfunction\sfor\sservice\sendpoints\susing\shostNetwork$'
test/e2e/network/networking.go:474
May  3 08:59:51.692: failed dialing endpoint, did not find expected responses... 
Tries 39
Command curl -g -q -s 'http://10.64.3.102:9080/dial?request=hostname&protocol=http&host=10.0.38.220&port=80&tries=1'
retrieved map[]
expected map[e2e-c8a0630093-a7d53-minion-group-7bq2:{} e2e-c8a0630093-a7d53-minion-group-c5lb:{} e2e-c8a0630093-a7d53-minion-group-j0s7:{}]
vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_06.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-network] Proxy version v1 should proxy through a service and a pod [Conformance] 16m11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-network\]\sProxy\sversion\sv1\sshould\sproxy\sthrough\sa\sservice\sand\sa\spod\s\s\[Conformance\]$'
test/e2e/framework/framework.go:652
May  3 09:14:27.350: 14 (503; 5.204219062s): path /api/v1/namespaces/proxy-7039/pods/proxy-service-5tmvw-2lsvf:162/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 5.209345419s): path /api/v1/namespaces/proxy-7039/services/http:proxy-service-5tmvw:portname2/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 5.210709679s): path /api/v1/namespaces/proxy-7039/pods/proxy-service-5tmvw-2lsvf:160/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 30.136613973s): path /api/v1/namespaces/proxy-7039/services/proxy-service-5tmvw:portname1/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 44.90799072s): path /api/v1/namespaces/proxy-7039/pods/https:proxy-service-5tmvw-2lsvf:460/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 44.909640767s): path /api/v1/namespaces/proxy-7039/services/https:proxy-service-5tmvw:tlsportname1/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 44.915415373s): path /api/v1/namespaces/proxy-7039/pods/https:proxy-service-5tmvw-2lsvf:462/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 44.916752493s): path /api/v1/namespaces/proxy-7039/services/https:proxy-service-5tmvw:tlsportname2/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 54.341339075s): path /api/v1/namespaces/proxy-7039/pods/https:proxy-service-5tmvw-2lsvf:443/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 59.506313412s): path /api/v1/namespaces/proxy-7039/pods/proxy-service-5tmvw-2lsvf/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 59.507168827s): path /api/v1/namespaces/proxy-7039/services/http:proxy-service-5tmvw:portname1/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 15m38.582744935s): path /api/v1/namespaces/proxy-7039/pods/proxy-service-5tmvw-2lsvf:1080/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 15m41.531830898s): path /api/v1/namespaces/proxy-7039/pods/http:proxy-service-5tmvw-2lsvf:160/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 15m43.579109552s): path /api/v1/namespaces/proxy-7039/pods/http:proxy-service-5tmvw-2lsvf:1080/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 15m43.588027095s): path /api/v1/namespaces/proxy-7039/services/proxy-service-5tmvw:portname2/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
14 (503; 15m43.589425531s): path /api/v1/namespaces/proxy-7039/pods/http:proxy-service-5tmvw-2lsvf:162/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion: Continue: RemainingItemCount:<nil>} Status:Failure Message:the server is currently unable to handle the request Reason:ServiceUnavailable Details:&StatusDetails{Name:,Group:,Kind:,Causes:[]StatusCause{StatusCause{Type:UnexpectedServerResponse,Message:unknown,Field:,},},RetryAfterSeconds:0,UID:,} Code:503}
vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
				
				Click to see stdout/stderrfrom junit_30.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-node] NodeLease NodeLease the kubelet should report node status infrequently 2m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-node\]\sNodeLease\sNodeLease\sthe\skubelet\sshould\sreport\snode\sstatus\sinfrequently$'
test/e2e/common/node/node_lease.go:114
May  3 08:59:18.653: Expected
    <v1.ConditionStatus>: Unknown
to equal
    <v1.ConditionStatus>: True
test/e2e/common/node/node_lease.go:193
				
				Click to see stdout/stderrfrom junit_14.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] volumes should store data 4m25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sCSI\sVolumes\s\[Driver\:\scsi\-hostpath\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\]\svolumes\sshould\sstore\sdata$'
test/e2e/storage/testsuites/volumes.go:161
May  3 08:59:25.135: "test -b /opt/0" should fail with exit code 1, but failed with error message "error dialing backend: dial timeout, backstop"
stdout: 
stderr: 
Unexpected error:
    <*errors.StatusError | 0xc002bd32c0>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "error dialing backend: dial timeout, backstop",
            Reason: "",
            Details: nil,
            Code: 500,
        },
    }
    error dialing backend: dial timeout, backstop
occurred
test/e2e/framework/volume/fixtures.go:750
				
				Click to see stdout/stderrfrom junit_20.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] Dynamic Provisioning GlusterDynamicProvisioner should create and delete persistent volumes [fast] 7m38s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sDynamic\sProvisioning\sGlusterDynamicProvisioner\sshould\screate\sand\sdelete\spersistent\svolumes\s\[fast\]$'
test/e2e/storage/volume_provisioning.go:712
May  3 09:05:55.290: Unexpected error:
    <*errors.errorString | 0xc0026cdc20>: {
        s: "PersistentVolumeClaims [pvc-7kc97] not all in phase Bound within 5m0s",
    }
    PersistentVolumeClaims [pvc-7kc97] not all in phase Bound within 5m0s
occurred
test/e2e/storage/testsuites/provisioning.go:669
				
				Click to see stdout/stderrfrom junit_27.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should be able to unmount after the subpath directory is deleted [LinuxOnly] 2m10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\slocal\]\[LocalVolumeType\:\sdir\-bindmounted\]\s\[Testpattern\:\sPre\-provisioned\sPV\s\(default\sfs\)\]\ssubPath\sshould\sbe\sable\sto\sunmount\safter\sthe\ssubpath\sdirectory\sis\sdeleted\s\[LinuxOnly\]$'
test/e2e/storage/testsuites/subpath.go:447
May  3 08:59:27.490: Unexpected error:
    <*errors.StatusError | 0xc003957360>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "error dialing backend: dial timeout, backstop",
            Reason: "",
            Details: nil,
            Code: 500,
        },
    }
    error dialing backend: dial timeout, backstop
occurred
test/e2e/storage/utils/local.go:251
				
				Click to see stdout/stderrfrom junit_13.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir] [Testpattern: Pre-provisioned PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource 1m53s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\slocal\]\[LocalVolumeType\:\sdir\]\s\[Testpattern\:\sPre\-provisioned\sPV\s\(default\sfs\)\]\ssubPath\sshould\ssupport\sexisting\sdirectories\swhen\sreadOnly\sspecified\sin\sthe\svolumeSource$'
test/e2e/storage/testsuites/subpath.go:397
May  3 08:59:41.465: Unexpected error:
    <*errors.StatusError | 0xc003b0f680>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "error dialing backend: dial timeout, backstop",
            Reason: "",
            Details: nil,
            Code: 500,
        },
    }
    error dialing backend: dial timeout, backstop
occurred
test/e2e/storage/utils/local.go:211
				
				Click to see stdout/stderrfrom junit_17.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly directory specified in the volumeMount 2m46s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\slocal\]\[LocalVolumeType\:\sdir\]\s\[Testpattern\:\sPre\-provisioned\sPV\s\(default\sfs\)\]\ssubPath\sshould\ssupport\sreadOnly\sdirectory\sspecified\sin\sthe\svolumeMount$'
test/e2e/storage/testsuites/subpath.go:367
May  3 09:00:56.814: Unexpected error:
    <exec.CodeExitError>: {
        Err: {
            s: "command terminated with exit code 1",
        },
        Code: 1,
    }
    command terminated with exit code 1
occurred
test/e2e/storage/utils/local.go:211