Skip to content

Conversation

@nckturner
Copy link
Contributor

@nckturner nckturner commented Mar 2, 2022

What type of PR is this?

Uncomment only one, leave it on its own line:

/kind failing-test

What this PR does / why we need it:

Fixes failing e2e test.

  • Create test run directory earlier to avoid failure
  • Install e2e prereqs

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 2, 2022
@k8s-ci-robot k8s-ci-robot requested review from jaypipes and wongma7 March 2, 2022 23:02
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 2, 2022
@nckturner
Copy link
Contributor Author

/test pull-cloud-provider-aws-e2e

@nckturner nckturner force-pushed the make-e2e-work-prow branch from 362ff57 to b844034 Compare March 3, 2022 02:23
@nckturner
Copy link
Contributor Author

/test pull-cloud-provider-aws-e2e

@nckturner nckturner force-pushed the make-e2e-work-prow branch from b844034 to ff8521a Compare March 3, 2022 02:36
@nckturner
Copy link
Contributor Author

/test pull-cloud-provider-aws-e2e
/test pull-cloud-provider-aws-test

@nckturner nckturner changed the title Create test run directory earlier to avoid failure Get e2e tests working in prow Mar 3, 2022
* Create test run directory earlier to avoid failure
* Install e2e prereqs
@nckturner nckturner force-pushed the make-e2e-work-prow branch from ff8521a to b50bd5c Compare March 3, 2022 09:30
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 3, 2022

if [[ "${DOWN}" = "yes" ]]; then
kops delete cluster --name "${CLUSTER_NAME}" --yes
${test_run}/kops delete cluster --name "${CLUSTER_NAME}" --yes
Copy link

Choose a reason for hiding this comment

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

how did the binary get here? is kops also an e2e-tool?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good question, its downloaded by the kubetest2 kops deployer: https://github.com/kubernetes/kops/blob/master/tests/e2e/pkg/kops/download.go#L32-L55

Copy link

Choose a reason for hiding this comment

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

should we call kubetest2 --down (or whatever the right arguments are) then instead, so we don't have to care about that implementation detail?

@wongma7
Copy link

wongma7 commented Mar 3, 2022

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nckturner, wongma7

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

The pull request process is described here

Details 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

@k8s-ci-robot k8s-ci-robot merged commit 62d7c47 into kubernetes:master Mar 3, 2022
nckturner added a commit that referenced this pull request Mar 4, 2022
…-upstream-release-1.22

Automated cherry pick of #312: Fix e2e failures
k8s-ci-robot added a commit that referenced this pull request May 13, 2022
…f-#304-#312-upstream-release-1.20

Cherry pick E2E test changes and fix failing tagging controller test for 1.20
k8s-ci-robot added a commit that referenced this pull request May 13, 2022
…f-#304-#312-upstream-release-1.21

Cherry pick E2E test changes and fix failing tagging controller test for 1.21
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants