This job view page is being replaced by Spyglass soon. Check out the new job view.
PRtedyu: Don't try to create VolumeSpec immediately after underlying PVC is being deleted
ResultFAILURE
Tests 8 failed / 752 succeeded
Started2020-01-14 19:06
Elapsed57m26s
Revision
Buildergke-prow-default-pool-cf4891d4-7178
Refs master:dd772834
86670:d1369e67
pode7805d36-3700-11ea-81e0-fe95fa936759
infra-commit6d2c48318
job-versionv1.18.0-alpha.1.681+21399fab7a1c0d
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
pode7805d36-3700-11ea-81e0-fe95fa936759
repok8s.io/kubernetes
repo-commit21399fab7a1c0dcbe841f388939dbcf65fb6bdb2
repos{u'k8s.io/kubernetes': u'master:dd77283426bd3249004472efcbb3257744448161,86670:d1369e678296716114690199a05e29a5fbd59bf0', u'k8s.io/release': u'master'}
revisionv1.18.0-alpha.1.681+21399fab7a1c0d

Test Failures


Kubernetes e2e suite [sig-apps] DisruptionController should block an eviction until the PDB is updated to allow it 22s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDisruptionController\sshould\sblock\san\seviction\suntil\sthe\sPDB\sis\supdated\sto\sallow\sit$'
test/e2e/apps/disruption.go:202
Jan 14 19:48:06.113: Unexpected error:
    <*errors.StatusError | 0xc0007b4960>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "Cannot evict pod as it would violate the pod's disruption budget.",
            Reason: "TooManyRequests",
            Details: {
                Name: "",
                Group: "",
                Kind: "",
                UID: "",
                Causes: [
                    {
                        Type: "DisruptionBudget",
                        Message: "The disruption budget foo needs 2 healthy pods and has 2 currently",
                        Field: "",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 429,
        },
    }
    Cannot evict pod as it would violate the pod's disruption budget.
occurred
test/e2e/apps/disruption.go:227
				
				Click to see stdout/stderrfrom junit_08.xml

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


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: block] One pod requesting one prebound PVC should be able to mount volume and read from pod1 2m42s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sblock\]\sOne\spod\srequesting\sone\sprebound\sPVC\sshould\sbe\sable\sto\smount\svolume\sand\sread\sfrom\spod1$'
test/e2e/storage/persistent_volumes-local.go:210
Jan 14 19:30:57.999: Unexpected error:
    <*errors.errorString | 0xc00286c3a0>: {
        s: "pod \"security-context-0180beec-f115-40d3-9c73-2ff9e0fa824d\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-0180beec-f115-40d3-9c73-2ff9e0fa824d" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:213
				
				Click to see stdout/stderrfrom junit_10.xml

Find security-context-0180beec-f115-40d3-9c73-2ff9e0fa824d mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: blockfswithformat] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2 2m53s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sblockfswithformat\]\sTwo\spods\smounting\sa\slocal\svolume\sat\sthe\ssame\stime\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:244
Jan 14 19:23:10.108: Unexpected error:
    <*errors.errorString | 0xc001a15e90>: {
        s: "pod \"security-context-4e9e309a-50ac-4d53-a61e-5a3d6d7f305a\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-4e9e309a-50ac-4d53-a61e-5a3d6d7f305a" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:710
				
				Click to see stdout/stderrfrom junit_18.xml

Find security-context-4e9e309a-50ac-4d53-a61e-5a3d6d7f305a mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: blockfswithformat] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2 2m35s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sblockfswithformat\]\sTwo\spods\smounting\sa\slocal\svolume\sone\safter\sthe\sother\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:250
Jan 14 19:47:54.135: Unexpected error:
    <*errors.errorString | 0xc00272e930>: {
        s: "pod \"security-context-fee3da40-79b7-4657-94b0-cc4668a70fdc\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-fee3da40-79b7-4657-94b0-cc4668a70fdc" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:747
				
				Click to see stdout/stderrfrom junit_14.xml

Find security-context-fee3da40-79b7-4657-94b0-cc4668a70fdc mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir-bindmounted] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2 2m23s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sdir\-bindmounted\]\sTwo\spods\smounting\sa\slocal\svolume\sat\sthe\ssame\stime\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:244
Jan 14 19:48:49.650: Unexpected error:
    <*errors.errorString | 0xc001936580>: {
        s: "pod \"security-context-d81bfa82-16e2-40e0-a5bd-21b54de4ec4e\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-d81bfa82-16e2-40e0-a5bd-21b54de4ec4e" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:710
				
				Click to see stdout/stderrfrom junit_25.xml

Find security-context-d81bfa82-16e2-40e0-a5bd-21b54de4ec4e mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir-link-bindmounted] One pod requesting one prebound PVC should be able to mount volume and write from pod1 2m49s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sdir\-link\-bindmounted\]\sOne\spod\srequesting\sone\sprebound\sPVC\sshould\sbe\sable\sto\smount\svolume\sand\swrite\sfrom\spod1$'
test/e2e/storage/persistent_volumes-local.go:210
Jan 14 19:30:19.505: Unexpected error:
    <*errors.errorString | 0xc0021a3dd0>: {
        s: "pod \"security-context-950b4ea2-a566-43e3-ad43-3363aeff2c03\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-950b4ea2-a566-43e3-ad43-3363aeff2c03" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:213
				
				Click to see stdout/stderrfrom junit_16.xml

Find security-context-950b4ea2-a566-43e3-ad43-3363aeff2c03 mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir-link] Two pods mounting a local volume one after the other should be able to write from pod1 and read from pod2 2m26s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sdir\-link\]\sTwo\spods\smounting\sa\slocal\svolume\sone\safter\sthe\sother\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
test/e2e/storage/persistent_volumes-local.go:250
Jan 14 19:35:41.569: Unexpected error:
    <*errors.errorString | 0xc00299edc0>: {
        s: "pod \"security-context-9709893f-fdc4-46b5-acaa-84590061f66a\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-9709893f-fdc4-46b5-acaa-84590061f66a" is not Running: timed out waiting for the condition
occurred
test/e2e/storage/persistent_volumes-local.go:747
				
				Click to see stdout/stderrfrom junit_14.xml

Find security-context-9709893f-fdc4-46b5-acaa-84590061f66a mentions in log files | View test history on testgrid


Test 33m14s

error during ./hack/ginkgo-e2e.sh --ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 752 Passed Tests

Show 4099 Skipped Tests