-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Closed
Labels
kind/test-flakeCategorizes issue or PR as related to test flakes.Categorizes issue or PR as related to test flakes.priority/P0sig/master
Description
The above mentioned PR is hitting it consistently. There are 4 of the same type of failures in the attached log and all the failures are within a couple of seconds of each other.
It looks like the test creates a service account and then tries to create a pod before the API token for the service account is available. It looks like its waiting 10 seconds on that.
Relevant snippet from the logs:
Feb 14 21:17:26.058: INFO: >>> kubeConfig: /tmp/cluster-admin.kubeconfig
STEP: Building a namespace api object
Feb 14 21:17:30.411: INFO: About to run a Kube e2e test, ensuring namespace is privileged
Feb 14 21:17:30.595: INFO: No PodSecurityPolicies found; assuming PodSecurityPolicy is disabled.
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] Sysctls
/tmp/openshift/build-rpms/rpm/BUILD/origin-3.9.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/sysctl.go:56
[It] should support unsafe sysctls which are actually whitelisted [Suite:openshift/conformance/parallel] [Suite:k8s]
/tmp/openshift/build-rpms/rpm/BUILD/origin-3.9.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/sysctl.go:101
STEP: Creating a pod with the kernel.shm_rmid_forced sysctl
Feb 14 21:17:40.101: INFO: Unexpected error occurred: No API token found for service account "default", retry after the token is automatically created and added to the service account
Metadata
Metadata
Assignees
Labels
kind/test-flakeCategorizes issue or PR as related to test flakes.Categorizes issue or PR as related to test flakes.priority/P0sig/master