search

kubernetes / test-infra

Test infrastructure for the Kubernetes project.
Apache License 2.0
3.82k stars 2.63k forks source link

Migrate current NPD CI Build job to k8s-infra-prow-build #32893

Closed DigitalVeer closed 2 months ago

DigitalVeer commented 2 months ago

This PR seeks to replicate the 403 error first encountered by @wangzhen127, as detailed here: https://github.com/kubernetes/test-infra/pull/32222#issuecomment-1988772136

By reproducing this error, we aim to identify and address any underlying issues as we continue transitioning NPD CI jobs to community clusters. This is related to NPD jobs failing during migration, see: https://github.com/kubernetes/kubernetes/issues/119211

linux-foundation-easycla[bot] commented 2 months ago

CLA Signed

The committers listed above are authorized under a signed CLA.

k8s-ci-robot commented 2 months ago

Welcome @DigitalVeer!

It looks like this is your first PR to kubernetes/test-infra 🎉. 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/test-infra 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. :smiley:

k8s-ci-robot commented 2 months ago

Hi @DigitalVeer. 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
wangzhen127 commented 2 months ago

/assign @wangzhen127

DigitalVeer commented 2 months ago

Can you update your description with why we are doing this now?

Updated.

wangzhen127 commented 2 months ago

/lgtm

dims commented 2 months ago

/ok-to-test /approve /lgtm

k8s-ci-robot commented 2 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DigitalVeer, dims

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/node-problem-detector/OWNERS](https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/node-problem-detector/OWNERS)~~ [dims] 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 commented 2 months ago

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

In response to [this](https://github.com/kubernetes/test-infra/pull/32893): >This PR seeks to replicate the 403 error first encountered by @wangzhen127, as detailed here: https://github.com/kubernetes/test-infra/pull/32222#issuecomment-1988772136 > >By reproducing this error, we aim to identify and address any underlying issues as we continue transitioning NPD CI jobs to community clusters. This is related to NPD jobs failing during migration, see: https://github.com/kubernetes/kubernetes/issues/119211 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.