Skip to content

Conversation

@lentzi90
Copy link
Contributor

@lentzi90 lentzi90 commented Mar 9, 2022

What this PR does / why we need it:

The e2e tests are broken for release-0.5. Probably due to the organization change for cert-manager. By bumping the CAPI version this should be fixed.
Ref. slack discussion.

Special notes for your reviewer:

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
  2. This is my first PR to CAPO, please tell me if there is anything I missed.

TODOs:

  • squashed commits
  • if necessary:
    • includes documentation
    • adds unit tests

/hold

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Mar 9, 2022
@netlify
Copy link

netlify bot commented Mar 9, 2022

✔️ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

🔨 Explore the source changes: 41c1d6d

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/62288b5e3ef0fd000860bb3a

😎 Browse the preview: https://deploy-preview-1169--kubernetes-sigs-cluster-api-openstack.netlify.app

@k8s-ci-robot
Copy link
Contributor

Welcome @lentzi90!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-openstack 🎉. 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-sigs/cluster-api-provider-openstack 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 the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 9, 2022
@k8s-ci-robot
Copy link
Contributor

Hi @lentzi90. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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 size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 9, 2022
@lentzi90 lentzi90 force-pushed the lentzi90/fix-release-0.5-tests branch from 74c4dcf to b74fb5f Compare March 9, 2022 07:00
@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 9, 2022
@chrischdi
Copy link
Member

/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 Mar 9, 2022
@lentzi90 lentzi90 force-pushed the lentzi90/fix-release-0.5-tests branch from b74fb5f to 46093c6 Compare March 9, 2022 08:38
@lentzi90 lentzi90 changed the title 🐛 Bump CAPI test framework 🐛 Bump CAPI version to fix cert-manager URL Mar 9, 2022
@chrischdi
Copy link
Member

chrischdi commented Mar 9, 2022

Original fix was this one: https://github.com/kubernetes-sigs/cluster-api/pull/6050/files

Fix on capo main was this one: #1136

So I was wrong with the requirement to bump sigs.k8s.io/cluster-api/test , sigs.k8s.io/cluster-api needs to be updated but this is also done in your PR 👍

@lentzi90
Copy link
Contributor Author

lentzi90 commented Mar 9, 2022

Original fix was this one: https://github.com/kubernetes-sigs/cluster-api/pull/6050/files

So I was wrong with the requirement to bump sigs.k8s.io/cluster-api/test , sigs.k8s.io/cluster-api needs to be updated but this is also done in your PR +1

Yeah I realized when the test failed that I needed to also update CAPI, not just the test. I guess this is because the error is coming from clusterctl, which is in CAPI (not part of the test package). Hoping it will pass this time 🤞
Do you want me to remove the bump for CAPI/test or is it better to bump both so they are at the same version?

@chrischdi
Copy link
Member

I think they should be in sync so lets see how the test goes now 👍

Forgot to add prior to this: thank you for tackling this and the contribution 🎉

@lentzi90
Copy link
Contributor Author

lentzi90 commented Mar 9, 2022

Hmm now I'm a bit lost. Still the same error. 🤔

@mdbooth
Copy link
Contributor

mdbooth commented Mar 9, 2022

See #1133 which I kind of abandoned when it seemed we weren't going to use it. You'll need to bump the versions in test/e2e/data/e2e_conf.yaml too at a minimum.

@lentzi90 lentzi90 force-pushed the lentzi90/fix-release-0.5-tests branch from 46093c6 to f43d67e Compare March 9, 2022 10:15
@mdbooth
Copy link
Contributor

mdbooth commented Mar 9, 2022

Although you might need to bump them to 1.0.5 rather than 1.0.4, which my older patch did. Note that my PR wasn't working yet.

@mdbooth mdbooth mentioned this pull request Mar 9, 2022
@lentzi90 lentzi90 force-pushed the lentzi90/fix-release-0.5-tests branch from f43d67e to acf98d3 Compare March 9, 2022 10:20
@lentzi90
Copy link
Contributor Author

lentzi90 commented Mar 9, 2022

Thanks @mdbooth ! I realized there was a replace in the go.mod that still had the old version also. Now hopefully everything is updated.

@chrischdi
Copy link
Member

Yes, the old test did still ues the old version, visible in the logs via: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-openstack/1169/pull-cluster-api-provider-openstack-e2e-test/1501477514122366976#1:build-log.txt%3A1485:

...
go: downloading k8s.io/utils v0.0.0-20210930125809-cb0fa318a74b
go: downloading sigs.k8s.io/cluster-api v1.0.1-0.20211028151834-d72fd59c8483
go: downloading sigs.k8s.io/cluster-api/test v1.0.5
go: downloading sigs.k8s.io/controller-runtime v0.10.3
go: downloading github.com/gogo/protobuf v1.3.2
...

🤞

@lentzi90 lentzi90 force-pushed the lentzi90/fix-release-0.5-tests branch from acf98d3 to 41c1d6d Compare March 9, 2022 11:11
@lentzi90
Copy link
Contributor Author

lentzi90 commented Mar 9, 2022

Missed some references in the Makefile also.

@chrischdi
Copy link
Member

Green tests 🎉

/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 9, 2022
@mdbooth
Copy link
Contributor

mdbooth commented Mar 9, 2022

We should probably fix OWNERS in the 0.5 branch if we're going to keep maintaining it.

/assign @jichenjc

Copy link
Contributor

@seanschneeweiss seanschneeweiss left a comment

Choose a reason for hiding this comment

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

/lgtm

@lentzi90
Copy link
Contributor Author

lentzi90 commented Mar 9, 2022

/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 Mar 9, 2022
@sbueringer
Copy link
Member

lending an approve until the other PR is merged :)
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90, mdbooth, sbueringer

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

@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 9, 2022
@k8s-ci-robot k8s-ci-robot merged commit 455c285 into kubernetes-sigs:release-0.5 Mar 9, 2022
@lentzi90 lentzi90 deleted the lentzi90/fix-release-0.5-tests branch March 9, 2022 18:48
@jichenjc
Copy link
Contributor

We should probably fix OWNERS in the 0.5 branch if we're going to keep maintaining it.

do you mind add corresponding approvers through PR then we can update it ? Thanks @mdbooth

@sbueringer
Copy link
Member

@jichenjc I think that was done in: #1170

@jichenjc
Copy link
Contributor

@sbueringer thanks :)

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. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. 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.

7 participants