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.

Sign up for GitHub

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

Jump to bottom

Flaky test: Opaque resources should schedule pods that initially do not fit after enough opaque integer resources are freed #42597

Closed
dchen1107 opened this issue Mar 6, 2017 · 9 comments
Closed

Flaky test: Opaque resources should schedule pods that initially do not fit after enough opaque integer resources are freed #42597

dchen1107 opened this issue Mar 6, 2017 · 9 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@dchen1107
Copy link
Member

The test failed in both ci-kubernetes-e2e-gci-gce and ci-kubernetes-e2e-kops-aws:

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-kops-aws/5096
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce/5059

This blocks the submit-queue.
@dchen1107 dchen1107 added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Mar 6, 2017
@dchen1107
Copy link
Member Author

The culprit pr is #41870 which introduces new set of tests and merged recently.

@dchen1107 dchen1107 mentioned this issue Mar 6, 2017
Merged
2 tasks
@dchen1107
Copy link
Member Author

The breakage caused by pr:#41870 actually breaks two required test suites: ci-kubernetes-e2e-gci-gce & /ci-kubernetes-e2e-kops-aws. Should we revert this for now? @kubernetes/release-team

@dchen1107 dchen1107 added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Mar 6, 2017
This was referenced Mar 6, 2017
Merged
Closed
@dchen1107
Copy link
Member Author

Another failure is https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-kops-aws/5097

@dchen1107
Copy link
Member Author

one more: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-etcd3/6586

@ConnorDoyle
Copy link
Contributor

The fix to OIR and corresponding e2e were submitted as separate commits; do you mind reverting only e402c5d ?

@ConnorDoyle
Copy link
Contributor

cc @timothysc

@dashpole dashpole mentioned this issue Mar 6, 2017
Merged
@j3ffml j3ffml mentioned this issue Mar 7, 2017
Merged
k8s-github-robot pushed a commit that referenced this issue Mar 7, 2017
Merge pull request #42598 from kubernetes/revert-41870-test-out-of-oir
8e52bec 
Automatic merge from submit-queue (batch tested with PRs 42080, 41653, 42598, 42555)

Revert "Pods pending due to insufficient OIR should get scheduled once sufficient OIR becomes available."

Reverts #41870 for stopping bleeding edge: #42597

cc/ @ConnorDoyle @kubernetes/release-team 

Connor if there is a pending pr to fix the issue, please point it out to me. We can close this one, otherwise, I would like to revert the pr first. You can resubmit the fix. Thanks!
@derekwaynecarr derekwaynecarr mentioned this issue Mar 7, 2017
Merged
@wongma7 wongma7 mentioned this issue Aug 25, 2017
Merged
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 21, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 20, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ConnorDoyle @dchen1107 @k8s-ci-robot @fejta-bot