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

Make PV tests work on kubemark clusters #803

Open
mm4tt opened this issue Sep 18, 2019 · 11 comments
Open

Make PV tests work on kubemark clusters #803

mm4tt opened this issue Sep 18, 2019 · 11 comments
Assignees
@RafalKorepta
Labels
area/clusterloader good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@mm4tt
Copy link
Contributor

mm4tt commented Sep 18, 2019 •
edited
Loading

Enabling PVs in the load test failed the kubemark presubmit because scheduler failed to schedule pods with PVs

Unable to schedule test-y6u59n-1/small-statefulset-0-0: no fit: 0/101 nodes are available: 1 node(s) were unschedulable, 100 node(s) had volume node affinity conflict.; waiting

In order to make it work on kubemark we'll most likely have to change a few places in the code (or ensure they already work this way) so they're faking operations related to attaching and mounting PDs in kubemark

  • Attach Detach Controller
  • HollowKubelet
  • Scheduler
  • ?

Ref. #704
@mm4tt mm4tt changed the title Make PV test work on kubemark clusters Make PV tests work on kubemark clusters Sep 18, 2019
@wojtek-t wojtek-t added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. area/clusterloader labels Sep 18, 2019
mm4tt added a commit to mm4tt/test-infra that referenced this issue Sep 18, 2019
@mm4tt
Disable PVs in kubemark tests.
9383c57 
Ref. kubernetes/perf-tests#803
@mm4tt mm4tt mentioned this issue Sep 18, 2019
Merged
@mm4tt
Copy link
Contributor Author

mm4tt commented Sep 18, 2019

/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@mm4tt:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Sep 18, 2019
@jukie
Copy link

jukie commented Oct 3, 2019

I'd like to pick this up, where would I begin?

@mm4tt
Copy link
Contributor Author

mm4tt commented Oct 3, 2019

Hey, @jukie, that's great to hear!

This one is a bit more complicated, I'll need to think about it more and come up with a more concrete list of steps. Unfortunately, I won't have time to do it until ~mid next week.
In the meantime, feel free to pick another issue from the help wanted list. I think #595 is relatively simple and will get you through all the prep work required to start contributing to kubernetes (forking repos, signing CLA, etc.).

@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.

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 Jan 1, 2020
@wojtek-t
Copy link
Member

wojtek-t commented Jan 2, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2020
@mm4tt mm4tt mentioned this issue Mar 17, 2020
Merged
This was referenced Mar 18, 2020
Merged
Merged
@maniSbindra maniSbindra mentioned this issue Mar 27, 2020
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.

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 Apr 1, 2020
@mm4tt
Copy link
Contributor Author

mm4tt commented Apr 1, 2020

/remove-lifecycle stale

We still want to do it...

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 1, 2020
@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.

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 Jun 30, 2020
@wojtek-t
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 30, 2020
@RafalKorepta
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RafalKorepta RafalKorepta

Labels
area/clusterloader good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mm4tt @jukie @wojtek-t @k8s-ci-robot @RafalKorepta @fejta-bot