You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
configvar CSI_PROW_E2E_VERSION_1_13 v1.14.0 "E2E version for Kubernetes 1.13.x"# we can't use the one from 1.13.x because it didn't have --storage.testdriver
209
+
# TOOO: remove versioned variables and make e2e version match k8s version
204
210
configvar CSI_PROW_E2E_VERSION_1_14 v1.14.0 "E2E version for Kubernetes 1.14.x"
205
211
configvar CSI_PROW_E2E_VERSION_1_15 v1.15.0 "E2E version for Kubernetes 1.15.x"
212
+
configvar CSI_PROW_E2E_VERSION_1_16 v1.16.0 "E2E version for Kubernetes 1.16.x"
206
213
# TODO: add new CSI_PROW_E2E_VERSION entry for future Kubernetes releases
207
214
configvar CSI_PROW_E2E_VERSION_LATEST master "E2E version for Kubernetes master"# testing against Kubernetes master is already tracking a moving target, so we might as well use a moving E2E version
208
215
configvar CSI_PROW_E2E_REPO_LATEST https://github.com/kubernetes/kubernetes "E2E repo for Kubernetes >= 1.13.x"# currently the same for all versions
@@ -292,11 +299,6 @@ regex_join () {
292
299
# alpha in previous Kubernetes releases. This was considered too
293
300
# error prone. Therefore we use E2E tests that match the Kubernetes
294
301
# version that is getting tested.
295
-
#
296
-
# However, for 1.13.x testing we have to use the E2E tests from 1.14
297
-
# because 1.13 didn't have --storage.testdriver yet, so for that (and only
298
-
# that version) we have to define alpha tests differently.
299
-
configvar CSI_PROW_E2E_ALPHA_1_13 '\[Feature: \[Testpattern:.Dynamic.PV..block.volmode.\] should.create.and.delete.block.persistent.volumes'"alpha tests for Kubernetes 1.13"# Raw block was an alpha feature in 1.13.
300
302
configvar CSI_PROW_E2E_ALPHA_LATEST '\[Feature:'"alpha tests for Kubernetes >= 1.14"# there's no need to update this, adding a new case for CSI_PROW_E2E for a new Kubernetes is enough
# Some tests are known to be unusable in a KinD cluster. For example,
@@ -723,22 +725,6 @@ install_sanity () (
723
725
run_with_go "${CSI_PROW_GO_VERSION_SANITY}" go test -c -o "${CSI_PROW_WORK}/csi-sanity""${CSI_PROW_SANITY_IMPORT_PATH}/cmd/csi-sanity"|| die "building csi-sanity failed"
724
726
)
725
727
726
-
# Whether the hostpath driver supports raw block devices depends on which version
727
-
# we are testing. It would be much nicer if we could determine that by querying the
728
-
# installed driver's capabilities instead of having to do a version check.
729
-
hostpath_supports_block () {
730
-
local result
731
-
result="$(docker exec csi-prow-control-plane docker image ls --format='{{.Repository}} {{.Tag}} {{.ID}}'| grep hostpath |whileread -r repo tag id;do
732
-
if [ "$tag"=="v1.0.1" ];then
733
-
# Old version because the revision label is missing: didn't have support yet.
734
-
echo"false"
735
-
return
736
-
fi
737
-
done)"
738
-
# If not set, then it must be a newer driver with support.
739
-
echo "${result:-true}"
740
-
}
741
-
742
728
# The default implementation of this function generates a external
743
729
# driver test configuration for the hostpath driver.
744
730
#
@@ -755,12 +741,14 @@ SnapshotClass:
755
741
DriverInfo:
756
742
Name: ${CSI_PROW_HOSTPATH_DRIVER_NAME}
757
743
Capabilities:
758
-
block: $(hostpath_supports_block)
744
+
block: true
759
745
persistence: true
760
746
dataSource: true
761
747
multipods: true
762
748
nodeExpansion: true
763
749
controllerExpansion: true
750
+
snapshotDataSource: true
751
+
singleNodeVolume: true
764
752
EOF
765
753
}
766
754
@@ -946,7 +934,7 @@ main () {
946
934
images=
947
935
if${CSI_PROW_BUILD_JOB};then
948
936
# A successful build is required for testing.
949
-
run_with_go "${CSI_PROW_GO_VERSION_BUILD}" make all || die "'make all' failed"
937
+
run_with_go "${CSI_PROW_GO_VERSION_BUILD}" make all "GOFLAGS_VENDOR=${GOFLAGS_VENDOR}"|| die "'make all' failed"
950
938
# We don't want test failures to prevent E2E testing below, because the failure
951
939
# might have been minor or unavoidable, for example when experimenting with
952
940
# changes in "release-tools" in a PR (that fails the "is release-tools unmodified"
@@ -956,13 +944,13 @@ main () {
956
944
warn "installing 'dep' failed, cannot test vendoring"
957
945
ret=1
958
946
fi
959
-
if! run_with_go "${CSI_PROW_GO_VERSION_BUILD}" make -k test2>&1| make_test_to_junit;then
947
+
if! run_with_go "${CSI_PROW_GO_VERSION_BUILD}" make -k test"GOFLAGS_VENDOR=${GOFLAGS_VENDOR}"2>&1| make_test_to_junit;then
960
948
warn "'make test' failed, proceeding anyway"
961
949
ret=1
962
950
fi
963
951
fi
964
952
# Required for E2E testing.
965
-
run_with_go "${CSI_PROW_GO_VERSION_BUILD}" make container || die "'make container' failed"
953
+
run_with_go "${CSI_PROW_GO_VERSION_BUILD}" make container "GOFLAGS_VENDOR=${GOFLAGS_VENDOR}"|| die "'make container' failed"
0 commit comments