OCPCLOUD-2214,OCPBUGS-17287,OCPBUGS-21642: Bump capi/capi providers/k8s 1.27#132
Conversation
|
@damdo: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
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. |
|
/hold |
|
@damdo: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
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. |
|
@damdo: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
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. |
7559d9c to
8a4550c
Compare
ran: // see https://github.com/kubernetes/client-go/issues/1269#issuecomment-1613565035 - go get k8s.io/kube-openapi@2546d827e515dca59571ec245eef2302e11018e1 && go mod tidy // we need to use a commit hash rather than a point release because // a new 1.5.0 release is not out yet, but 1.4.0 doesn't work with controller-runtime v0.15.z // this will need to change to v1.5.0 once it is released. - go get sigs.k8s.io/cluster-api-provider-gcp@f1ea13261b0f929beca8c65d932046003caa652d && go mod tidy - go mod vendor -
|
/test unit lint vendor images |
|
/test unit lint vendor images |
efa0804 to
9736988
Compare
|
/test unit lint vendor images |
|
@damdo: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
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. |
9736988 to
2e43620
Compare
|
@damdo: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. DetailsIn response to this:
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. |
|
/test all |
|
@JoelSpeed: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. This pull request references Jira Issue OCPBUGS-17287, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/retest-required |
|
With a cluster bot cluster built with: Cluster API Provider GCP manual E2Es passed: |
|
@damdo: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. This pull request references Jira Issue OCPBUGS-17287, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/retest |
|
@damdo: This pull request references OCPCLOUD-2214 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.15.0" version, but no target version was set. This pull request references Jira Issue OCPBUGS-17287, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. This pull request references Jira Issue OCPBUGS-21642, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
3200a6f to
c988723
Compare
31aa314 to
ec21471
Compare
|
@damdo: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/lgtm /hold I would like to see a cluster-bot test to verify that this does indeed work with the paired PR as expected. If we can get green results from cluster bot then I think a green button merge to merge them simultaneously should be safe |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Cluster bot proof in:
|
|
/override ci/prow/e2e-aws-ovn-techpreview |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-ovn-techpreview DetailsIn response to this:
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. |
|
@damdo: Jira Issue OCPBUGS-17287: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-17287 has been moved to the MODIFIED state. Jira Issue OCPBUGS-21642: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-21642 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-ovn-techpreview DetailsIn response to this:
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. |
|
Fix included in accepted release 4.15.0-0.nightly-2023-10-24-230302 |
…dating-webhook-configuration The resource was renamed to cluster-capi-operator in 1096d5c (manifests: rename validatingwebhookconfiguration to a more meaningful name, 2023-10-12, openshift#132), and that's a much more specific name for the cluster-scoped resource. However, clusters upating from 4.15.0-ec.1 with the old name should not have two similar-but-not-quite-matching versions of the webhook configuration, or updates can stick with cluster-api ClusterOperator going Degraded=True on SyncingFailed with [1]: Failed to resync for operator: 4.15.0-ec.2 because &{%!e(string=unable to reconcile CoreProvider: unable to create or update CoreProvider: Internal error occurred: failed calling webhook "vcoreprovider.operator.cluster.x-k8s.io": failed to call webhook: the server could not find the requested resource)} This commit adds a deletion manifest [2] to ask the cluster-version operator to remove the resource, to avoid leaking the old resource into new clusters. [1]: https://issues.redhat.com/browse/OCPBUGS-23467 [2]: https://github.com/openshift/enhancements/blob/8a11b7085c69b078690d50958f541d2a817d85df/dev-guide/cluster-version-operator/dev/object-deletion.md
Done:
Warning
This PR needs to be "GREEN BUTTON MERGED" at the same time as the cluster-api-operator PR, as the new code of that operator references a new CRD (deployed by this repo), so to avoid breaking the payload we need to merge them together. (We are planning to fix this, see enhancement)
Todo:
As part of this process we are also merging Rebase PRs on the CAPI provider forks.
I will track here E2E tests ran from this branch/PR against the rebase PRs in the various CAPI provider repos forks.
I will track here E2E tests ran from this branch/PR against the rebase PRs in the various CAPI provider repos forks (details for E2E runs below).
mastertesting) - test-run