Update the project type for evented-pleg presubmit CI job

[sairameshv]

Observed some failure in the recently added CI job to run the e2e tests by enabling the evented-pleg feature.
The failure seems to be related to sshing into the FCOS node instance that is created to run the e2e tests.
Sample Failure log that is observed:

W0118 13:16:04.351] I0118 13:16:04.351159    6824 ssh.go:120] Running the command ssh, with args: [-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR -i /workspace/.ssh/google_compute_engine [email protected] -- sudo sh -c 'systemctl list-units  --type=service  --state=running | grep -e containerd -e crio']
W0118 13:17:09.651] E0118 13:17:09.650723    6824 ssh.go:123] failed to run SSH command: out: [email protected]: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
W0118 13:17:09.651] , err: exit status 255

Following are some of the jobs that use this arg --gcp-project-type=node-e2e-project and hence added this change that might fix the CI job failure.

• ci-cos-cgroupv1-containerd-node-e2e
• ci-cgroup-systemd-containerd-node-e2e
• ci-crio-cgroupv1-node-e2e-conformance
• ci-crio-cgroupv2-node-e2e-conformance, etc.

Signed-off-by: Sai Ramesh Vanka [email protected]

[k8s-ci-robot]

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

[sairameshv]

/cc @harche @mrunalp

[harche]

/ok-to-test

[harche]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrunalp, sairameshv

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:

• config/jobs/kubernetes/sig-node/OWNERS [mrunalp]

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

[k8s-ci-robot]

@sairameshv: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key sig-node-presubmit.yaml using file config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml

In response to this:

Observed some failure in the recently added CI job to run the e2e tests by enabling the evented-pleg feature.
The failure seems to be related to sshing into the FCOS node instance that is created to run the e2e tests.
Sample Failure log that is observed:

W0118 13:16:04.351] I0118 13:16:04.351159    6824 ssh.go:120] Running the command ssh, with args: [-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR -i /workspace/.ssh/google_compute_engine [email protected] -- sudo sh -c 'systemctl list-units  --type=service  --state=running | grep -e containerd -e crio']
W0118 13:17:09.651] E0118 13:17:09.650723    6824 ssh.go:123] failed to run SSH command: out: [email protected]: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
W0118 13:17:09.651] , err: exit status 255

Following are some of the jobs that use this arg --gcp-project-type=node-e2e-project and hence added this change that might fix the CI job failure.

• ci-cos-cgroupv1-containerd-node-e2e
• ci-cgroup-systemd-containerd-node-e2e
• ci-crio-cgroupv1-node-e2e-conformance
• ci-crio-cgroupv2-node-e2e-conformance, etc.

Signed-off-by: Sai Ramesh Vanka [email protected]

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.