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

adding --ssh-key and --ssh-user for kubetest2 #105637

Merged
merged 9 commits into from
Oct 26, 2021

Conversation

Namanl2001
Copy link
Member

Signed-off-by: Namanl2001 namanlakhwani@gmail.com

This PR is part of the CI migration from kubetest to kubetest2
https://github.com/kubernetes/enhancements/tree/master/keps/sig-testing/2464-kubetest2-ci-migration

--ssh-key and --ssh-user are not present for kubetest2, which is leading to this error: failed to run SSH command: out: Warning: Identity file /root/.ssh/google_compute_engine not accessible: No such file or directory :
ref: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/92316/pull-kubernetes-node-e2e-kubetest2/1446852497472753664#1:build-log.txt%3A114

Using these args in kubetest2 via kubernetes-sigs/kubetest2#169

Signed-off-by: Namanl2001 <namanlakhwani@gmail.com>
@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 12, 2021
@k8s-ci-robot
Copy link
Contributor

@Namanl2001: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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
Copy link
Contributor

Welcome @Namanl2001!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 12, 2021
@k8s-ci-robot
Copy link
Contributor

Hi @Namanl2001. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Oct 12, 2021
@Namanl2001
Copy link
Member Author

cc: @amwat @dims

@amwat
Copy link
Contributor

amwat commented Oct 12, 2021

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 12, 2021
@amwat
Copy link
Contributor

amwat commented Oct 12, 2021

/sig node
/sig testing
/kind feature
/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. kind/feature Categorizes issue or PR as related to a new feature. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Oct 12, 2021
@@ -47,6 +47,8 @@ timeout_arg=""
system_spec_name=${SYSTEM_SPEC_NAME:-}
extra_envs=${EXTRA_ENVS:-}
runtime_config=${RUNTIME_CONFIG:-}
ssh_user=${SSH_USER:-}
ssh_key=${SSH_KEY:-}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these would most likely be empty when not run with kubetest2 (i.e. directly make)
maybe add something like:
ssh_key=${SSH_KEY:-${GCE_SSH_PRIVATE_KEY_FILE:-${USER}/.ssh/google_compute_engine}}

Signed-off-by: Namanl2001 <namanlakhwani@gmail.com>
@amwat
Copy link
Contributor

amwat commented Oct 12, 2021

/test pull-kubernetes-node-e2e-kubetest2

@Namanl2001
Copy link
Member Author

non kubetest2 jobs passes after adding quotes for SSH_USER let's try same with SSH_KEY

Signed-off-by: Namanl2001 <namanlakhwani@gmail.com>
@Namanl2001
Copy link
Member Author

/test pull-kubernetes-node-e2e-kubetest2
/test pull-kubernetes-node-e2e-containerd-kubetest2

@amwat
Copy link
Contributor

amwat commented Oct 19, 2021

Oh I meant there might be an issue with how we are passing the args, not sure

https://github.com/kubernetes/test-infra/blob/183ddb6f2b5b38e8bf1dc43a9da4da5d911f832a/config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml#L136

https://github.com/kubernetes/test-infra/blob/183ddb6f2b5b38e8bf1dc43a9da4da5d911f832a/config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml#L268

The bash command is trying to run seems to be off https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/105637/pull-kubernetes-node-e2e-kubetest2/1450522436058484736#1:build-log.txt%3A293

[Serial]"

seems like we are somehow unquoting the skip flags and it's dropping everything before the pipe |
let's try using double quotes for the focus and skip regex.

Signed-off-by: Namanl2001 <namanlakhwani@gmail.com>
@Namanl2001
Copy link
Member Author

reverted previous commit change: c6e0564
As it makes pull-kubernetes-e2e-gce-ubuntu-containerd to fail

@amwat
Copy link
Contributor

amwat commented Oct 19, 2021

/test pull-kubernetes-node-e2e-kubetest2
/test pull-kubernetes-node-e2e-containerd-kubetest2

@amwat
Copy link
Contributor

amwat commented Oct 19, 2021

looks like more quoting errors 😅

... ./ginkgo  -nodes=8  -focus=""\[NodeConformance\]""  -skip=""\[Flaky\]|\[Slow\]|\[Serial\]"" ...

the makefile seems to be adding it's own quotes

if [[ ${focus} != "" ]]; then
ginkgoflags="${ginkgoflags} -focus=\"${focus}\" "
fi
if [[ ${skip} != "" ]]; then
ginkgoflags="${ginkgoflags} -skip=\"${skip}\" "
fi

so we probably need to just pass it raw without any quotes

@Namanl2001
Copy link
Member Author

so we probably need to just pass it raw without any quotes

let's try this too 🤞

@Namanl2001
Copy link
Member Author

/test pull-kubernetes-node-e2e-kubetest2
/test pull-kubernetes-node-e2e-containerd-kubetest2

@Namanl2001
Copy link
Member Author

for the failure of /test pull-kubernetes-node-e2e-kubetest2 I think we should also remove quotes from --test-args

@amwat
Copy link
Contributor

amwat commented Oct 20, 2021

pull-kubernetes-node-e2e-containerd-kubetest2 successful run is awesome to see!

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/105637/pull-kubernetes-node-e2e-containerd-kubetest2/1450804977088860160

for the failure of /test pull-kubernetes-node-e2e-kubetest2 I think we should also remove quotes from --test-args

yeah, either that or quote the entire thing including --test-args similar to the containerd job
https://github.com/kubernetes/test-infra/blob/68b4c3bc47288a4314cf8dc46656be2d3ac6e784/config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml#L268

@Namanl2001
Copy link
Member Author

/test pull-kubernetes-node-e2e-kubetest2

@Namanl2001
Copy link
Member Author

🤩 Awesome to see green kubetest2 jobs. just testing the remaining ones

/test pull-kubernetes-node-e2e-containerd-features-kubetest2
/test pull-kubernetes-node-e2e-alpha-kubetest2
/test pull-kubernetes-node-kubelet-serial-kubetest2
/test pull-kubernetes-node-kubelet-serial-containerd-kubetest2

@Namanl2001
Copy link
Member Author

@amwat all tests should pass after the changes in this PR, right?

/retest

@amwat
Copy link
Contributor

amwat commented Oct 26, 2021

looking at the failures, seems like they are not related to ssh.
I would go ahead with this PR since that's what it's targetting

Stabilizing the other jobs might be involved and could need follow ups.

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 26, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amwat, dims, Namanl2001

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@amwat
Copy link
Contributor

amwat commented Oct 26, 2021

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 26, 2021
@k8s-ci-robot
Copy link
Contributor

@Namanl2001: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubernetes-node-e2e-containerd-features-kubetest2 d721796 link false /test pull-kubernetes-node-e2e-containerd-features-kubetest2
pull-kubernetes-node-e2e-alpha-kubetest2 d721796 link false /test pull-kubernetes-node-e2e-alpha-kubetest2
pull-kubernetes-node-kubelet-serial-containerd-kubetest2 d721796 link false /test pull-kubernetes-node-kubelet-serial-containerd-kubetest2
pull-kubernetes-node-kubelet-serial-kubetest2 d721796 link false /test pull-kubernetes-node-kubelet-serial-kubetest2

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot merged commit 7c715db into kubernetes:master Oct 26, 2021
SIG Node CI/Test Board automation moved this from PRs Waiting on Author to Done Oct 26, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.23 milestone Oct 26, 2021
@Namanl2001 Namanl2001 deleted the ssh branch October 27, 2021 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
Archived in project
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

5 participants