ResultFAILURE
Tests 11 failed / 29 succeeded
Started2019-11-27 07:46
Elapsed51m11s
Revision
Builderdfd50e3d-10e9-11ea-b3d3-b20db476995a
Refs master:1c5b6cb6
85621:657a3a32
infra-commit26aa74fc2
job-versionv1.18.0-alpha.0.1191+5975b80d569031-dirty
repok8s.io/kubernetes
repo-commit5975b80d569031dc570afedb2a4c6574e512446c
repos{u'k8s.io/kubernetes': u'master:1c5b6cb66e6ae85177e76d4fddf7d99473ab2aed,85621:657a3a3294e70685229282713361ecef6a366989'}
revisionv1.18.0-alpha.0.1191+5975b80d569031-dirty

Test Failures


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with different volume mode and retain data across pod recreation on the same node 10m52s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(block\svolmode\)\]\smultiVolume\s\[Slow\]\sshould\saccess\sto\stwo\svolumes\swith\sdifferent\svolume\smode\sand\sretain\sdata\sacross\spod\srecreation\son\sthe\ssame\snode$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:202
Nov 27 08:14:46.200: Unexpected error:
    <*errors.errorString | 0xc001a77c80>: {
        s: "pod \"security-context-e938331a-d129-4b9a-a5bf-9b96ef1c8b66\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-e938331a-d129-4b9a-a5bf-9b96ef1c8b66" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:360
				
				Click to see stdout/stderrfrom junit_05.xml

Find security-context-e938331a-d129-4b9a-a5bf-9b96ef1c8b66 mentions in log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node 11m25s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(block\svolmode\)\]\smultiVolume\s\[Slow\]\sshould\saccess\sto\stwo\svolumes\swith\sthe\ssame\svolume\smode\sand\sretain\sdata\sacross\spod\srecreation\son\sdifferent\snode$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:159
Nov 27 08:16:36.378: Unexpected error:
    <*errors.errorString | 0xc00220c5b0>: {
        s: "pod \"security-context-016b32da-aaa4-44f1-a348-74f4d3b72a70\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-016b32da-aaa4-44f1-a348-74f4d3b72a70" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:360
				
				Click to see stdout/stderrfrom junit_10.xml

Find security-context-016b32da-aaa4-44f1-a348-74f4d3b72a70 mentions in log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (block volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node 8m30s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(block\svolmode\)\]\smultiVolume\s\[Slow\]\sshould\saccess\sto\stwo\svolumes\swith\sthe\ssame\svolume\smode\sand\sretain\sdata\sacross\spod\srecreation\son\sthe\ssame\snode$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:129
Nov 27 08:25:55.811: Unexpected error:
    <*errors.errorString | 0xc000bc0ba0>: {
        s: "pod \"security-context-f28beafc-6fbc-40b2-9e9a-e8621c78402b\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-f28beafc-6fbc-40b2-9e9a-e8621c78402b" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:360
				
				Click to see stdout/stderrfrom junit_08.xml

Find security-context-f28beafc-6fbc-40b2-9e9a-e8621c78402b mentions in log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (default fs)] subPath should verify container cannot write to subpath readonly volumes [Slow] 8m38s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\]\ssubPath\sshould\sverify\scontainer\scannot\swrite\sto\ssubpath\sreadonly\svolumes\s\[Slow\]$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:417
Nov 27 08:12:38.079: while waiting for subpath failure
Unexpected error:
    <*errors.errorString | 0xc0032e70d0>: {
        s: "subpath container unexpectedly terminated",
    }
    subpath container unexpectedly terminated
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:740
				
				Click to see stdout/stderrfrom junit_07.xml

Filter through log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on different node 10m40s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(filesystem\svolmode\)\]\smultiVolume\s\[Slow\]\sshould\saccess\sto\stwo\svolumes\swith\sthe\ssame\svolume\smode\sand\sretain\sdata\sacross\spod\srecreation\son\sdifferent\snode$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:159
Nov 27 08:12:38.910: Unexpected error:
    <*errors.errorString | 0xc000542f80>: {
        s: "pod \"security-context-3452d513-7d14-451b-8106-5788989242ff\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-3452d513-7d14-451b-8106-5788989242ff" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:360
				
				Click to see stdout/stderrfrom junit_08.xml

Find security-context-3452d513-7d14-451b-8106-5788989242ff mentions in log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should access to two volumes with the same volume mode and retain data across pod recreation on the same node 10m20s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(filesystem\svolmode\)\]\smultiVolume\s\[Slow\]\sshould\saccess\sto\stwo\svolumes\swith\sthe\ssame\svolume\smode\sand\sretain\sdata\sacross\spod\srecreation\son\sthe\ssame\snode$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:129
Nov 27 08:16:34.427: Unexpected error:
    <*errors.errorString | 0xc0026338c0>: {
        s: "pod \"security-context-7a8e8c90-258c-4dcd-ba87-4e66d33da4c7\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-7a8e8c90-258c-4dcd-ba87-4e66d33da4c7" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:360
				
				Click to see stdout/stderrfrom junit_02.xml

Find security-context-7a8e8c90-258c-4dcd-ba87-4e66d33da4c7 mentions in log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (filesystem volmode)] multiVolume [Slow] should concurrently access the single volume from pods on the same node 6m44s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(filesystem\svolmode\)\]\smultiVolume\s\[Slow\]\sshould\sconcurrently\saccess\sthe\ssingle\svolume\sfrom\spods\son\sthe\ssame\snode$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:293
Nov 27 08:24:20.599: while cleanup resource
Unexpected error:
    <errors.aggregate | len:1, cap:1>: [
        [
            {
                error: {
                    cause: {
                        s: "PersistentVolume pvc-2a8fca4a-92f2-4891-acf1-22f542d2a69f still exists within 5m0s",
                    },
                    msg: "Persistent Volume pvc-2a8fca4a-92f2-4891-acf1-22f542d2a69f not deleted by dynamic provisioner",
                },
                stack: [0x3995499, 0x39bb3f5, 0x39bd3c3, 0x7d30a8, 0x7d2cff, 0x7d21a4, 0x7d9105, 0x7d8961, 0x7de7df, 0x7de300, 0x7ddb47, 0x7e012b, 0x7e2c87, 0x7e29cd, 0x3abb0ba, 0x3abfcab, 0x516669, 0x462e51],
            },
        ],
    ]
    Persistent Volume pvc-2a8fca4a-92f2-4891-acf1-22f542d2a69f not deleted by dynamic provisioner: PersistentVolume pvc-2a8fca4a-92f2-4891-acf1-22f542d2a69f still exists within 5m0s
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/multivolume.go:120
				
				Click to see stdout/stderrfrom junit_05.xml

Filter through log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (xfs)][Slow] volumes should store data 17m51s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sDynamic\sPV\s\(xfs\)\]\[Slow\]\svolumes\sshould\sstore\sdata$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:150
Nov 27 08:19:25.782: Failed to create client pod: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:580
				
				Click to see stdout/stderrfrom junit_03.xml

Filter through log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Inline-volume (xfs)][Slow] volumes should store data 14m10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sInline\-volume\s\(xfs\)\]\[Slow\]\svolumes\sshould\sstore\sdata$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:150
Nov 27 08:19:26.019: Failed to create client pod: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:580
				
				Click to see stdout/stderrfrom junit_09.xml

Filter through log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Pre-provisioned PV (xfs)][Slow] volumes should store data 18m49s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\sazure\-disk\]\s\[Testpattern\:\sPre\-provisioned\sPV\s\(xfs\)\]\[Slow\]\svolumes\sshould\sstore\sdata$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:150
Nov 27 08:21:34.157: Failed to create client pod: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/volume/fixtures.go:580
				
				Click to see stdout/stderrfrom junit_06.xml

Filter through log files


Test 23m6s

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

Filter through log files


Show 29 Passed Tests

Show 4787 Skipped Tests