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

Conformance tests for s390x architecture #67721

Closed
dims opened this issue Aug 22, 2018 · 40 comments
Closed

Conformance tests for s390x architecture #67721

dims opened this issue Aug 22, 2018 · 40 comments
Labels
area/conformance Issues or PRs related to kubernetes conformance tests lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@dims
Copy link
Member

dims commented Aug 22, 2018 •
edited
Loading

Similar to https://k8s-testgrid.appspot.com/sig-node-ppc64le#conformance we need to run tests against s390x based k8s installations

/cc @shahidhs-ibm @gajju26 @alicefr @cwsolee @estesp
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 22, 2018
@dims
Copy link
Member Author

dims commented Aug 22, 2018

older issue - #39229
related to - #38067

@dims
Copy link
Member Author

dims commented Aug 22, 2018

/sig testing

@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 22, 2018
@alicefr
Copy link

alicefr commented Aug 23, 2018

hi, what are the requirements?

@dims
Copy link
Member Author

dims commented Aug 23, 2018

@alicefr pretty simple first step is to run the end-to-end tests for conformance and report problems if any:

https://github.com/kubernetes/community/blob/master/contributors/devel/e2e-tests.md#conformance-tests

@alicefr
Copy link

alicefr commented Aug 23, 2018

sorry, my question should have sounded more like "do you need any help?" :)

@cwsolee
Copy link

cwsolee commented Aug 23, 2018

I'll take a look at it to c what it takes to do the same for s390x.

@dims
Copy link
Member Author

dims commented Aug 23, 2018

@alicefr sorry a little background ... if you see #38067 we did a bunch of work to switch over images in the e2e tests to be multi-arch. @mkumatag got pc64le working first. So now we are basically getting in touch with folks who were trying this before (looking through old issues/prs) and trying to see if they can try this again. The end goal is to make sure we have CI(s) for all architectures so we have a good signal for the release team that things are working not just on intel but on all platforms.

@mkumatag
Copy link
Member

Not all the images are built for s390x platform because of qemu emulation issue what we faced, so I first recommend go check the missing images and make sure we build them first on s390x and proceed further.

@dims
Copy link
Member Author

dims commented Aug 24, 2018

+1 @mkumatag

@cwsolee please see the output.txt here for what we have currently (generated today) - https://gist.github.com/dims/067c6723588a585a7a00b22e41b86f34

@cwsolee
Copy link

cwsolee commented Aug 24, 2018

I read some history, 2 questions/observation:
(1) Do we absolutely need buy google space to show result or as long as we've knew test is good it's good enough?
(2) Looks like problem on building images are all related to qemu emulation, it's not something that my team has skills, we build on z directly. @alicefr. can u c whether your team has anyone that could help out on this?

@dims
Copy link
Member Author

dims commented Aug 24, 2018

@cwsolee for 1) it's not a must. it will help figure out when we end up with a change which may break your CI and as a good signal for the release team to know that they can proceed with a release when things are green.

@cwsolee
Copy link

cwsolee commented Aug 24, 2018

Thanks, good to know, the real blocker is qemu issues then.

@dims
Copy link
Member Author

dims commented Sep 12, 2018

cc @jichenjc

@dims
Copy link
Member Author

dims commented Sep 24, 2018

@jichenc @cwsolee @estesp How can we help get this off the ground?

@cwsolee
Copy link

cwsolee commented Sep 25, 2018

We did chat a bit internally and @alicefr is trying to get some help, no good news yet.

@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 Dec 24, 2018
@dims
Copy link
Member Author

dims commented Jan 9, 2019

/area conformance

@k8s-ci-robot k8s-ci-robot added the area/conformance Issues or PRs related to kubernetes conformance tests label Jan 9, 2019
@dims
Copy link
Member Author

dims commented Jan 9, 2019

@jeffdyoung ping! got your name from @bradtopol Any help with this would be great!

@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

@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 Feb 8, 2019
@jeffdyoung
Copy link
Contributor

@dims Can you give me what would be required? Currently, I can get Fedora-29 2cpu/2GB RAM LPARs. Is this enough, and how many nodes do you usually test with?

@dims
Copy link
Member Author

dims commented Feb 18, 2019

@jeffdyoung need at least 2 nodes. i am not quite sure about the CPU/RAM requirements though.

@jeffdyoung jeffdyoung mentioned this issue Mar 13, 2019
Merged
@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 14, 2019
@timothysc timothysc added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Apr 23, 2019
@liudalibj liudalibj mentioned this issue May 13, 2019
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 Jul 22, 2019
@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

@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 Aug 21, 2019
@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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

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

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.

@dims
Copy link
Member Author

dims commented Jan 23, 2020

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Jan 23, 2020
@k8s-ci-robot
Copy link
Contributor

@dims: Reopened this issue.

In response to this:

/reopen

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.

@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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

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

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.

@dims
Copy link
Member Author

dims commented Aug 1, 2020

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Aug 1, 2020
@k8s-ci-robot
Copy link
Contributor

@dims: Reopened this issue.

In response to this:

/reopen

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.

@dims dims mentioned this issue Aug 1, 2020
Closed
@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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/conformance Issues or PRs related to kubernetes conformance tests lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@dims @timothysc @cwsolee @mkumatag @k8s-ci-robot @alicefr @fejta-bot @jeffdyoung