Skip to content
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

Wait for pod to be running in e2e test #11312

Closed
wants to merge 1 commit into from

Conversation

mfojtik
Copy link
Contributor

@mfojtik mfojtik commented Oct 11, 2016

Fixes: #11240

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 11, 2016

[test]

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 11, 2016

@ncdc @liggitt @Kargakis I don't think this fix the root problem here (the pods taking longer to start), but at least plumb the e2e.

@ncdc you mentioned that kubectl exec flakes rapidly in upstream... is that due to container create time increase and the the exec has low timeouts?

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to c6b5512

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 11, 2016

[test]

(aborted previous job because yum failure...)

@ncdc
Copy link
Contributor

ncdc commented Oct 11, 2016

No, the upstream exec flakes are happening because of what appears to be a
docker bug

On Tuesday, October 11, 2016, Michal Fojtik notifications@github.com
wrote:

@ncdc https://github.com/ncdc @liggitt https://github.com/liggitt
@Kargakis https://github.com/kargakis I don't think this fix the root
problem here (the pods taking longer to start), but at least plumb the e2e.

@ncdc https://github.com/ncdc you mentioned that kubectl exec flakes
rapidly in upstream... is that due to container create time increase and
the the exec has low timeouts?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11312 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABYmMSMUI7nmoHl7iyYuWUeh11F2heks5qy2CcgaJpZM4KTdnh
.

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 11, 2016

[test]

another yum flake

@0xmichalis
Copy link
Contributor

[test]

@0xmichalis
Copy link
Contributor

yum and #11094 [test]

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 12, 2016

[test]

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 12, 2016

flake: #8571

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 12, 2016

[test] flaked on #9624

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 13, 2016

[test]

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 13, 2016

removing merge... this PR does not help as the issue is the --attach timeout.

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 13, 2016

@Kargakis PTAL again... instead of relying on attach, we wait for the pod to succeed and then get the container logs (my hope is that will be more reliable...) @ncdc cc

@0xmichalis
Copy link
Contributor

Don't we want to test --attach?

@mfojtik
Copy link
Contributor Author

mfojtik commented Oct 13, 2016

@Kargakis I think we want to test that you can use the service account.

@0xmichalis
Copy link
Contributor

Fine by me, just make sure we have a test for --attach somewhere, otherwise open an issue.

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 98c0fd1

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10011/) (Base Commit: 50cc896)

@0xmichalis
Copy link
Contributor

Closing in favor of #11444

@0xmichalis 0xmichalis closed this Oct 19, 2016
@mfojtik mfojtik deleted the wait-for-running-pod branch September 5, 2018 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants