diff --git a/ci-operator/step-registry/baremetalds/devscripts/setup/baremetalds-devscripts-setup-commands.sh b/ci-operator/step-registry/baremetalds/devscripts/setup/baremetalds-devscripts-setup-commands.sh index c3009fc8813a2..32cd77f2e2d96 100644 --- a/ci-operator/step-registry/baremetalds/devscripts/setup/baremetalds-devscripts-setup-commands.sh +++ b/ci-operator/step-registry/baremetalds/devscripts/setup/baremetalds-devscripts-setup-commands.sh @@ -105,6 +105,7 @@ source ocp_install_env.sh echo "export DS_OPENSHIFT_VERSION=\$(openshift_version)" >> /tmp/ds-vars.conf echo "export DS_REGISTRY=\$LOCAL_REGISTRY_DNS_NAME:\$LOCAL_REGISTRY_PORT" >> /tmp/ds-vars.conf echo "export DS_WORKING_DIR=\$WORKING_DIR" >> /tmp/ds-vars.conf +echo "export DS_IP_STACK=\$IP_STACK" >> /tmp/ds-vars.conf EOF scp "${SSHOPTS[@]}" "root@${IP}:/tmp/ds-vars.conf" "${SHARED_DIR}/" diff --git a/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-commands.sh b/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-commands.sh index 3b67c4cceff93..93901e77c61b1 100644 --- a/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-commands.sh +++ b/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-commands.sh @@ -23,7 +23,7 @@ function copy_test_binaries() { function mirror_test_images() { echo "### Mirroring test images" - DEVSCRIPTS_TEST_IMAGE_REPO=${DS_REGISTRY}/localimages/local-test-image + DEVSCRIPTS_TEST_IMAGE_REPO=${DS_REGISTRY}/localimages/local-test-image # shellcheck disable=SC2087 ssh "${SSHOPTS[@]}" "root@${IP}" bash - << EOF openshift-tests images --to-repository ${DEVSCRIPTS_TEST_IMAGE_REPO} > /tmp/mirror @@ -34,7 +34,7 @@ EOF function use_minimal_test_list() { echo "### Skipping test images mirroring, fall back to minimal tests list" - + TEST_ARGS="--file /tmp/tests" TEST_SKIPS="" echo "${TEST_MINIMAL_LIST}" > /tmp/tests @@ -47,12 +47,21 @@ packet) # shellcheck source=/dev/null source "${SHARED_DIR}/ds-vars.conf" copy_test_binaries - export TEST_PROVIDER=\"\" + + # Currently all v6 deployments are disconnected, so we have to tell + # openshift-tests to exclude those tests that require internet + # access. + if [[ "${DS_IP_STACK}" != "v6" ]]; + then + export TEST_PROVIDER='\{\"type\":\"baremetal\"\}' + else + export TEST_PROVIDER='\{\"type\":\"baremetal\",\"disconnected\":true\}' + fi echo "### Checking release version" # Mirroring test images is supported only for versions greater than or equal to 4.7 if printf '%s\n%s' "4.8" "${DS_OPENSHIFT_VERSION}" | sort -C -V; then - mirror_test_images + mirror_test_images else use_minimal_test_list fi @@ -65,7 +74,7 @@ function upgrade() { ssh "${SSHOPTS[@]}" "root@${IP}" \ openshift-tests run-upgrade all \ --to-image "${OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE}" \ - --provider "${TEST_PROVIDER}" \ + --provider "${TEST_PROVIDER:-}" \ -o "/tmp/artifacts/e2e.log" \ --junit-dir "/tmp/artifacts/junit" set +x @@ -81,11 +90,11 @@ function suite() { fi scp "${SSHOPTS[@]}" /tmp/tests "root@${IP}:/tmp/tests" - + set -x ssh "${SSHOPTS[@]}" "root@${IP}" \ openshift-tests run "${TEST_SUITE}" "${TEST_ARGS:-}" \ - --provider "${TEST_PROVIDER}" \ + --provider "${TEST_PROVIDER:-}" \ -o "/tmp/artifacts/e2e.log" \ --junit-dir "/tmp/artifacts/junit" set +x diff --git a/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-ref.yaml b/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-ref.yaml index 7575b89c27cf0..a299b60b80204 100644 --- a/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-ref.yaml +++ b/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-ref.yaml @@ -46,32 +46,11 @@ ref: \[sig-api-machinery\] CustomResourcePublishOpenAPI \[Privileged:ClusterAdmin\] works for CRD with validation schema \[sig-api-machinery\]\[Feature:APIServer\]\[Late\] kube-apiserver terminates within graceful termination period \[sig-api-machinery\]\[Feature:APIServer\]\[Late\] kubelet terminates kube-apiserver gracefully - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs should adhere to Three Laws of Controllers - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs adoption will orphan all RCs and adopt them back when recreated - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs generation should deploy based on a status version bump - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs keep the deployer pod invariant valid should deal with cancellation after deployer pod succeeded - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs paused should disable actions on deployments - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs rolled back should rollback to an older deployment - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs should respect image stream tag reference policy resolve the image pull spec - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs viewing rollout history should print the rollout history - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs when changing image change trigger should successfully trigger from an updated image - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs when run iteratively should only deploy the last deployment - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs when tagging images should successfully tag the deployed image - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with custom deployments should run the custom deployment steps - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with enhanced status should include various info in status - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with env in params referencing the configmap should expand the config map key to a value - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with failing hook should get all logs from retried hooks - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with minimum ready seconds set should not transition the deployment to Complete before satisfied \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with multiple image change triggers should run a successful deployment with a trigger used by different containers \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with multiple image change triggers should run a successful deployment with multiple triggers - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with revision history limits should never persist more old deployments than acceptable after being observed by the controller - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs with test deployments should run a deployment to completion and then scale to zero - \[sig-apps\]\[Feature:DeploymentConfig\] deploymentconfigs won't deploy RC with unresolved images when patched with empty image - \[sig-apps\]\[Feature:Jobs\] Users should be able to create and run a job in a user project \[sig-arch\] Managed cluster should ensure control plane pods do not run in best-effort QoS \[sig-arch\] Managed cluster should have no crashlooping pods in core namespaces over four minutes \[sig-arch\] Managed cluster should only include cluster daemonsets that have maxUnavailable update of 10 or 33 percent - \[sig-arch\]\[Early\] Managed cluster should start all core operators \[sig-auth\] \[Feature:NodeAuthenticator\] The kubelet can delegate ServiceAccount tokens to the API server \[sig-auth\] \[Feature:NodeAuthenticator\] The kubelet's main port 10250 should reject requests with no credentials \[sig-auth\]\[Feature:HTPasswdAuth\] HTPasswd IDP should successfully configure htpasswd and be responsive @@ -90,79 +69,26 @@ ref: \[sig-auth\]\[Feature:OAuthServer\] \[Token Expiration\] Using a OAuth client with a non-default token max age to generate tokens that expire shortly works as expected when using a code authorization flow \[sig-auth\]\[Feature:OAuthServer\] \[Token Expiration\] Using a OAuth client with a non-default token max age to generate tokens that expire shortly works as expected when using a token authorization flow \[sig-auth\]\[Feature:SCC\]\[Early\] should not have pod creation failures during install - \[sig-auth\]\[Feature:SecurityContextConstraints\] TestPodDefaultCapabilities - \[sig-builds\]\[Feature:Builds\] Multi-stage image builds should succeed - \[sig-builds\]\[Feature:Builds\] Optimized image builds should succeed - \[sig-builds\]\[Feature:Builds\] build can reference a cluster service with a build being created from new-build should be able to run a build that references a cluster service - \[sig-builds\]\[Feature:Builds\] build have source revision metadata started build should contain source revision information - \[sig-builds\]\[Feature:Builds\] build with empty source started build should build even with an empty source in build config - \[sig-builds\]\[Feature:Builds\] build without output image building from templates should create an image from a S2i template without an output image reference defined - \[sig-builds\]\[Feature:Builds\] build without output image building from templates should create an image from a docker template without an output image reference defined - \[sig-builds\]\[Feature:Builds\] clone repository using git:// protocol should clone using git:// if no proxy is configured - \[sig-builds\]\[Feature:Builds\] custom build with buildah being created from new-build should complete build with custom builder image - \[sig-builds\]\[Feature:Builds\] imagechangetriggers imagechangetriggers should trigger builds of all types - \[sig-builds\]\[Feature:Builds\] oc new-app should fail with a --name longer than 58 characters - \[sig-builds\]\[Feature:Builds\] oc new-app should succeed with a --name of 58 characters - \[sig-builds\]\[Feature:Builds\] oc new-app should succeed with an imagestream - \[sig-builds\]\[Feature:Builds\] prune builds based on settings in the buildconfig buildconfigs should have a default history limit set when created via the group api - \[sig-builds\]\[Feature:Builds\] prune builds based on settings in the buildconfig should prune builds after a buildConfig change - \[sig-builds\]\[Feature:Builds\] prune builds based on settings in the buildconfig should prune canceled builds based on the failedBuildsHistoryLimit setting - \[sig-builds\]\[Feature:Builds\] prune builds based on settings in the buildconfig should prune completed builds based on the successfulBuildsHistoryLimit setting - \[sig-builds\]\[Feature:Builds\] prune builds based on settings in the buildconfig should prune errored builds based on the failedBuildsHistoryLimit setting - \[sig-builds\]\[Feature:Builds\] prune builds based on settings in the buildconfig should prune failed builds based on the failedBuildsHistoryLimit setting \[sig-builds\]\[Feature:Builds\] result image should have proper labels set Docker build from a template should create a image from .* template with proper Docker labels \[sig-builds\]\[Feature:Builds\] result image should have proper labels set S2I build from a template should create a image from .* template with proper Docker labels - \[sig-builds\]\[Feature:Builds\] s2i build with a quota Building from a template should create an s2i build with a quota and run it - \[sig-builds\]\[Feature:Builds\] s2i build with a root user image should create a root build and pass with a privileged SCC - \[sig-builds\]\[Feature:Builds\] verify /run filesystem contents are writeable using a simple Docker Strategy Build - \[sig-builds\]\[Feature:Builds\] verify /run filesystem contents do not have unexpected content using a simple Docker Strategy Build - \[sig-builds\]\[Feature:Builds\]\[pullsecret\] docker build using a pull secret Building from a template should create a docker build that pulls using a secret run it - \[sig-builds\]\[Feature:Builds\]\[timing\] capture build stages and durations should record build stages and durations for docker - \[sig-builds\]\[Feature:Builds\]\[timing\] capture build stages and durations should record build stages and durations for s2i - \[sig-builds\]\[Feature:Builds\]\[valueFrom\] process valueFrom in build strategy environment variables should fail resolving unresolvable valueFrom in docker build environment variable references - \[sig-builds\]\[Feature:Builds\]\[valueFrom\] process valueFrom in build strategy environment variables should fail resolving unresolvable valueFrom in sti build environment variable references - \[sig-builds\]\[Feature:Builds\]\[valueFrom\] process valueFrom in build strategy environment variables should successfully resolve valueFrom in docker build environment variables - \[sig-builds\]\[Feature:Builds\]\[valueFrom\] process valueFrom in build strategy environment variables should successfully resolve valueFrom in s2i build environment variables - \[sig-cli\] CLI can run inside of a busybox container \[sig-cli\] oc adm must-gather runs successfully \[sig-cli\] oc adm must-gather runs successfully for audit logs \[sig-cli\] oc adm must-gather runs successfully with options - \[sig-cli\] oc debug deployment configs from a build \[sig-cli\] oc debug does not require a real resource on the server \[sig-cli\] oc debug ensure it works with image streams \[sig-cli\] oc explain should contain proper fields description for special types \[sig-cli\] oc explain should contain proper spec+status for CRDs \[sig-cli\] oc observe works as expected \[sig-cli\] oc rsh rsh specific flags should work well when access to a remote shell - \[sig-cli\] oc rsh specific flags should work well when access to a remote shell - \[sig-cluster-lifecycle\] Pods cannot access the /config/master API endpoint \[sig-devex\] check registry.redhat.io is available and samples operator can import sample imagestreams run sample related validations \[sig-devex\]\[Feature:Templates\] templateinstance readiness test should report failed soon after an annotated objects has failed \[sig-devex\]\[Feature:Templates\] templateinstance readiness test should report ready soon after all annotated objects are ready - \[sig-imageregistry\]\[Feature:ImageAppend\] Image append should create images by appending them - \[sig-imageregistry\]\[Feature:ImageExtract\] Image extract should extract content from an image - \[sig-imageregistry\]\[Feature:ImageInfo\] Image info should display information about images - \[sig-imageregistry\]\[Feature:ImageLayers\] Image layer subresource should return layers from tagged images \[sig-imageregistry\]\[Feature:ImageLookup\] Image policy should perform lookup when the Deployment gets the resolve-names annotation later \[sig-imageregistry\]\[Feature:ImageLookup\] Image policy should perform lookup when the object has the resolve-names annotation \[sig-imageregistry\]\[Feature:ImageLookup\] Image policy should update standard Kube object image fields when local names are on - \[sig-imageregistry\]\[Feature:ImageTriggers\] Annotation trigger reconciles after the image is overwritten - \[sig-imageregistry\]\[Feature:Image\] oc tag should change image reference for internal images \[sig-imageregistry\]\[Feature:Image\] oc tag should preserve image reference for external images - \[sig-imageregistry\]\[Feature:Image\] oc tag should work when only imagestreams api is available - \[sig-instrumentation\] Prometheus when installed on the cluster should have a AlertmanagerReceiversNotConfigured alert in firing state - \[sig-instrumentation\] Prometheus when installed on the cluster should have important platform topology metrics - \[sig-instrumentation\] Prometheus when installed on the cluster should have non-Pod host cAdvisor metrics - \[sig-instrumentation\] Prometheus when installed on the cluster should provide ingress metrics - \[sig-instrumentation\] Prometheus when installed on the cluster should provide named network metrics - \[sig-instrumentation\] Prometheus when installed on the cluster should start and expose a secured proxy and unsecured metrics - \[sig-instrumentation\] Prometheus when installed on the cluster shouldn't have failing rules evaluation \[sig-instrumentation\] Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured - \[sig-instrumentation\]\[Late\] Alerts should have a Watchdog alert in firing state the entire cluster run - \[sig-instrumentation\]\[Late\] Alerts shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured \[sig-instrumentation\]\[Late\] Alerts shouldn't report any alerts in firing or pending state apart from Watchdog and AlertmanagerReceiversNotConfigured and have no gaps in Watchdog firing - \[sig-instrumentation\]\[sig-builds\]\[Feature:Builds\] Prometheus when installed on the cluster should start and expose a secured proxy and verify build metrics - \[sig-network-edge\]\[Conformance\]\[Area:Networking\]\[Feature:Router\] The HAProxy router should be able to connect to a service that is idled because a GET on the route will unidle it \[sig-network\] Conntrack should be able to preserve UDP traffic when server pod cycles for a ClusterIP service \[sig-network\] Conntrack should be able to preserve UDP traffic when server pod cycles for a NodePort service \[sig-network\] DNS should provide /etc/hosts entries for the cluster @@ -173,62 +99,6 @@ ref: \[sig-network\] DNS should provide DNS for the cluster \[sig-network\] DNS should resolve DNS of partial qualified names for services \[sig-network\] DNS should resolve DNS of partial qualified names for the cluster - \[sig-network\] Internal connectivity for TCP and UDP on ports 9000-9999 is allowed - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should allow egress access on one named port - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should allow egress access to server in CIDR block - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should allow ingress access from namespace on one named port - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should allow ingress access from updated namespace - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should allow ingress access from updated pod - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should allow ingress access on one named port - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should deny ingress access to updated pod - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce egress policy allowing traffic to a server in a different namespace based on PodSelector and NamespaceSelector - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce except clause while egress access to server in CIDR block - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce multiple egress policies with egress allow-all policy taking precedence - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce multiple ingress policies with ingress allow-all policy taking precedence - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce multiple, stacked policies with overlapping podSelectors - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policies to check ingress and egress policies can be controlled independently based on PodSelector - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy based on NamespaceSelector with MatchExpressions - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy based on PodSelector and NamespaceSelector - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy based on PodSelector or NamespaceSelector - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy based on PodSelector with MatchExpressions - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy based on Ports - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy to allow traffic from pods within server namespace based on PodSelector - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy to allow traffic only from a different namespace, based on NamespaceSelector - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce policy to allow traffic only from a pod in a different namespace based on PodSelector and NamespaceSelector - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should enforce updated policy - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should not allow access by TCP when a policy specifies only SCTP - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should stop enforcing policies after they are deleted - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should support a 'default-deny-all' policy - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should support a 'default-deny-ingress' policy - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should support allow-all policy - \[sig-network\] NetworkPolicy \[LinuxOnly\] NetworkPolicy between server and client should work with Ingress,Egress specified together - \[sig-network\] Networking Granular Checks: Services should function for client IP based session affinity: udp - \[sig-network\] Networking should provide Internet connection for containers - \[sig-network\] Services should be able to switch session affinity for NodePort service - \[sig-network\] Services should be able to switch session affinity for service with type clusterIP - \[sig-network\] Services should have session affinity timeout work for NodePort service - \[sig-network\] Services should have session affinity timeout work for service with type clusterIP - \[sig-network\] Services should have session affinity work for NodePort service - \[sig-network\] Services should have session affinity work for service with type clusterIP - \[sig-network\] services basic functionality should allow connections to another pod on a different node via a service IP - \[sig-network\] services basic functionality should allow connections to another pod on the same node via a service IP - \[sig-network\] services when using a plugin that does not isolate namespaces by default should allow connections to pods in different namespaces on different nodes via service IPs - \[sig-network\] services when using a plugin that does not isolate namespaces by default should allow connections to pods in different namespaces on the same node via service IPs - \[sig-network\]\[Feature:Router\] The HAProxy router should enable openshift-monitoring to pull metrics - \[sig-network\]\[Feature:Router\] The HAProxy router should expose a health check on the metrics port - \[sig-network\]\[Feature:Router\] The HAProxy router should expose prometheus metrics for a route - \[sig-network\]\[Feature:Router\] The HAProxy router should expose the profiling endpoints - \[sig-network\]\[Feature:Router\] The HAProxy router should override the route host for overridden domains with a custom value - \[sig-network\]\[Feature:Router\] The HAProxy router should override the route host with a custom value - \[sig-network\]\[Feature:Router\] The HAProxy router should respond with 503 to unrecognized hosts - \[sig-network\]\[Feature:Router\] The HAProxy router should run even if it has no access to update status - \[sig-network\]\[Feature:Router\] The HAProxy router should serve a route that points to two services and respect weights - \[sig-network\]\[Feature:Router\] The HAProxy router should serve routes that were created from an ingress - \[sig-network\]\[Feature:Router\] The HAProxy router should serve the correct routes when scoped to a single namespace and label set - \[sig-network\]\[Feature:Router\] The HAProxy router should support reencrypt to services backed by a serving certificate automatically - \[sig-network\]\[endpoints\] admission TestEndpointAdmission - \[sig-node\] Managed cluster should report ready nodes the entire duration of the test run \[sig-operator\] an end user can use OLM can subscribe to the operator \[sig-storage\] GCP Volumes GlusterFS should be mountable \[sig-storage\] In-tree Volumes \[Driver: gluster\] \[Testpattern: Inline-volume (default fs)\] subPath should be able to unmount after the subpath directory is deleted @@ -262,9 +132,6 @@ ref: \[sig-storage\] In-tree Volumes \[Driver: nfs\] \[Testpattern: Dynamic PV (default fs)\] volumes should allow exec of files on the volume \[sig-storage\] In-tree Volumes \[Driver: nfs\] \[Testpattern: Dynamic PV (default fs)\] volumes should store data \[sig-storage\] In-tree Volumes \[Driver: nfs\] \[Testpattern: Pre-provisioned PV (default fs)\] subPath should support existing directory - \[sig-storage\]\[Late\] Metrics should report short attach times - \[sig-storage\]\[Late\] Metrics should report short mount times - \[sig-network\] Networking Granular Checks: Services should function for client IP based session affinity: http documentation: Regular expression (POSIX basic regular expression) of tests to skip. Note that the current list it's just a temporary measure for the baremetal platform. - name: TEST_UPGRADE_OPTIONS default: "abort-at=100"