Skip to content

Update OpenStack spec dependencies#6382

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
shiftstack:bump_capo
Dec 5, 2022
Merged

Update OpenStack spec dependencies#6382
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
shiftstack:bump_capo

Conversation

@pierreprinetti
Copy link
Copy Markdown
Contributor

@pierreprinetti pierreprinetti commented Sep 21, 2022

The the OpenStack providerSpec for Machine has been moved to openshift/api.

Implements OSASINFRA-2981

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 21, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 21, 2022

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

openshift/api was bumped with 1dd74ca

@pierreprinetti pierreprinetti marked this pull request as ready for review October 2, 2022 13:08
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 2, 2022
@openshift-ci openshift-ci Bot requested review from MaysaMacedo and mdbooth October 2, 2022 13:09
@MaysaMacedo
Copy link
Copy Markdown
Contributor

@pierreprinetti seems you need to run go mod vendor to update the vendor folder

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 4, 2022
@pierreprinetti pierreprinetti changed the title Update cluster-api-provider-openstack to v0.6.3 Update OpenStack spec dependencies Oct 4, 2022
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 4, 2022
@pierreprinetti pierreprinetti force-pushed the bump_capo branch 2 times, most recently from 2370c06 to 91c45e6 Compare October 4, 2022 12:03
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/hold
this needs further work
/uncc mdbooth MaysaMacedo

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 4, 2022
@pierreprinetti pierreprinetti force-pushed the bump_capo branch 6 times, most recently from 5585140 to f9dfbc4 Compare October 5, 2022 08:17
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

Should be ready now.
/cc mdbooth MaysaMacedo mandre

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/hold cancel

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/retest-required

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

@patrickdillon Any chance we can override ci/prow/e2e-vsphere-ovn?
The vsphere run gives good results, except for the tests that are permafailing everywhere.

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 30, 2022
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD ac9b99e and 2 for PR HEAD f8bf57d in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 4a4e34f and 1 for PR HEAD f8bf57d in total

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD a6bde70 and 0 for PR HEAD f8bf57d in total

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/skip

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/hold

Revision f8bf57d was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 1, 2022
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 1, 2022
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0f7f0a6 and 2 for PR HEAD f8bf57d in total

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD c45c58e and 1 for PR HEAD f8bf57d in total

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD a2ed5c0 and 0 for PR HEAD f8bf57d in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/hold

Revision f8bf57d was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 3, 2022
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/retest-required
/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 4, 2022
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 5, 2022

@pierreprinetti: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-azure-ovn-resourcegroup f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-azure-ovn-resourcegroup
ci/prow/e2e-azure-ovn-shared-vpc f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-azure-ovn-shared-vpc
ci/prow/e2e-aws-ovn-proxy f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-aws-ovn-proxy
ci/prow/e2e-aws-ovn-single-node f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-aws-ovn-single-node
ci/prow/e2e-gcp-ovn-shared-vpc f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-gcp-ovn-shared-vpc
ci/prow/e2e-aws-ovn-shared-vpc f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-aws-ovn-shared-vpc
ci/prow/e2e-aws-ovn-imdsv2 f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-aws-ovn-imdsv2
ci/prow/e2e-aws-ovn-fips f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-aws-ovn-fips
ci/prow/e2e-azurestack f9dfbc4fcfac95719481a909da084fb2ee3422af link false /test e2e-azurestack
ci/prow/e2e-openstack-parallel d3dc96aaa01f559a6d188d9d6920debe03b62bbd link false /test e2e-openstack-parallel
ci/prow/e2e-openstack-sdn-parallel f8bf57d link false /test e2e-openstack-sdn-parallel
ci/prow/e2e-libvirt f8bf57d link false /test e2e-libvirt
ci/prow/e2e-metal-ipi-sdn f8bf57d link false /test e2e-metal-ipi-sdn
ci/prow/e2e-agent-sno f8bf57d link false /test e2e-agent-sno
ci/prow/e2e-openstack-proxy f8bf57d link false /test e2e-openstack-proxy
ci/prow/e2e-openstack f8bf57d link false /test e2e-openstack
ci/prow/e2e-aws-ovn-disruptive f8bf57d link false /test e2e-aws-ovn-disruptive

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 46ebfdf into openshift:master Dec 5, 2022
@pierreprinetti pierreprinetti deleted the bump_capo branch December 5, 2022 09:09
2uasimojo added a commit to 2uasimojo/hive that referenced this pull request Sep 18, 2023
Since the recent revendor (openshift#2052 / 26a0b81), OpenstackProviderSpec
(embedded in MachineSets under OpenStack) stopped being able to
unmarshal. This is because its schema moved from
github.com/openshift/cluster-api-provider-openstack to
github.com/openshift/api/machine/v1alpha1 and the revendor picked up
this move from the installer code: see
openshift/installer#6382

This commit moves our references accordingly to match that upstream
code.

Quirk 1: Strangely, this one type is in o/api/machine v1alpha1 even
though everything else in o/api/machine is in v1beta1.

Quirk 2: o/api/machine v1alpha1's registration methods don't actually
register the OpenstackProviderSpec type. (Why??) So we have to register
it explicitly, as the installer does.

This more or less reverts the prior attempt at openshift#2114 / 1f1ec2c, which
turned out to be completely redundant (the added registration call ended
up in the same place as the one on the previous line).

HIVE-2308
2uasimojo added a commit to 2uasimojo/hive that referenced this pull request Sep 26, 2023
Since the recent revendor (openshift#2052 / 26a0b81), OpenstackProviderSpec
(embedded in MachineSets under OpenStack) stopped being able to
unmarshal. This is because its schema moved from
github.com/openshift/cluster-api-provider-openstack to
github.com/openshift/api/machine/v1alpha1 and the revendor picked up
this move from the installer code: see
openshift/installer#6382

This commit moves our references accordingly to match that upstream
code.

Quirk 1: Strangely, this one type is in o/api/machine v1alpha1 even
though everything else in o/api/machine is in v1beta1.

Quirk 2: o/api/machine v1alpha1's registration methods don't actually
register the OpenstackProviderSpec type. (Why??) So we have to register
it explicitly, as the installer does.

This more or less reverts the prior attempt at openshift#2114 / 1f1ec2c, which
turned out to be completely redundant (the added registration call ended
up in the same place as the one on the previous line).

HIVE-2308

(cherry picked from commit 43376d8)
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants