-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to deploy database in e2e test: secret never got mounted #9775
Comments
The linked issue was closed, so I'm adding this so people can find it. Hit it again. https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_integration/3270 |
This is because identical volumes are mounted in serial per node, and since the same secret is used multiple times on the same node for different pods all of those pod starts are serialized. There appears to be a detach issues as well potentially (which may exacerbate the problem here). |
Issue is being worked and slated for 1.3 backport. |
think i hit what @deads2k referenced again here: |
Now resolved |
Post Rebase (kube 1.3.0) on our RHEL 7.2 CI machines some deployments are failing because they are unable to mount a secret occasionally.
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_integration/3091/
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_integration/3091/s3/download/test-end-to-end-docker/logs/container-origin.log
Opened kubernetes/kubernetes#28750
The text was updated successfully, but these errors were encountered: