OCPCLOUD-3324: Update to new manifests-gen

[mdbooth]

Update to use new manifests-gen

TODO:

• Merge OCPCLOUD-3327: Rewrite manifests-gen to support upgrade safety cluster-capi-operator#434

[openshift-ci-robot]

@mdbooth: This pull request references OCPCLOUD-3324 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Update to use new manifests-gen

TODO:

• Merge OCPCLOUD-3327: Rewrite manifests-gen to support upgrade safety cluster-capi-operator#434

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 openshift-eng/jira-lifecycle-plugin repository.

[mdbooth]

/hold

[openshift-ci-robot]

@mdbooth: This pull request references OCPCLOUD-3324 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Update to use new manifests-gen

TODO:

• Merge OCPCLOUD-3327: Rewrite manifests-gen to support upgrade safety cluster-capi-operator#434

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 openshift-eng/jira-lifecycle-plugin repository.

[theobarberbany]

/test e2e-azure

[JoelSpeed]

/lgtm

[openshift-ci]

@mdbooth: The following test 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/regression-clusterinfra-azure-ipi-techpreview-capi	517c1e5	link	false	/test regression-clusterinfra-azure-ipi-techpreview-capi

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

[theobarberbany]

/unhold

[theobarberbany]

I0218 21:54:33.071547       1 providerimages.go:153] "looking for provider manifests in container images"
I0218 21:54:51.908502       1 providerimages.go:190] "found provider manifests in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:9ff1850446c0d9b0b0f953a201d2e256b7743d1a4e7e432aa08fcf33f08e14b4" provider="cluster-api" type="core" version="v1.11.3" profile="default" ocpPlatform=""
I0218 21:54:51.908542       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:1e05ca1e5022213b7132adbfcd82bbd59dd8d95f7d5ac218476ca1c994b7bc7a"
I0218 21:54:51.908553       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:8fabc3998b621982e6b766e7c1ae2f444368182db333c9dffdb8b39669f80499"
I0218 21:54:51.908561       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:7a3d9c5faf3957c939cc516bedb7cd3976070572f6db56a0b7546d602b72eced"
I0218 21:54:51.908569       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:39d9078721e3a6bc02988500467d95f29423dc0e7cb534858f95d9547aa98ada"
I0218 21:54:51.908576       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:c444fd9abb154d315e222e4c3198eac1c71f534f4e940c020e843b237ce1dc34"
I0218 21:54:51.908583       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:b737e0cf2f1174f28af611949013c2a469118c2bd70640f6943788889cdd8ce5"
I0218 21:54:51.908589       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:5145ad458905a014f98dd8e0fa62224bdcc83bfdbd86aa0ed7ca21d5ef2c262f"
I0218 21:54:51.908596       1 providerimages.go:187] "no provider manifests found in container image" image="quay-proxy.ci.openshift.org/openshift/ci@sha256:36365a6d0cccb4f5e48fe832ae15de32e2f5b1099e21acbf33e08f8fd8e4871f"
I0218 21:54:51.908606       1 providerimages.go:190] "found provider manifests in container image" image="registry.build04.ci.openshift.org/ci-op-jsf4xl5l/stable@sha256:5ca4bc0619643c75c89d7c86d04901ff9532901bbfecfb3187aca56517fa8db7" provider="cluster-api-provider-azure" type="infrastructure" version="v1.22.0" profile="default" ocpPlatform="Azure"
I0218 21:54:51.908621       1 providerimages.go:202] "finished looking for provider manifests in container images"

Looking good

[theobarberbany]

/approve
/unhold
/verified by e2es

[openshift-ci-robot]

@theobarberbany: This PR has been marked as verified by e2es.

Details

In response to this:

/approve
/unhold
/verified by e2es

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 openshift-eng/jira-lifecycle-plugin repository.

[theobarberbany]

/label acknowledge-critical-fixes-only

[JoelSpeed]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, theobarberbany

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:

• OWNERS [JoelSpeed]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment