test crd schema checker

[gibizer]

• [make][pre-commit]Check CRD schema to avoid update issues
• DNM:test make crd-schema-check

[softwarefactory-project-zuul]

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/openstack-k8s-operators/openstack-operator for 1202,7fe2b7c0f261d044999b80766f2de701bf3f9531

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gibizer
Once this PR has been reviewed and has the lgtm label, please assign bshephar for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[gibizer]

/hold this is just a test PR to show that the new make crd-schema-check make target included in the pre-commit job catches non backwards compatible CRD changes.

[gibizer]

The pre-commit check should have caught the CRD change but it did not. The make target catches is for me locally so something is with the CI job.

[gibizer]

I see the issue when the pre-commit runs in the CI the proposed commit already placed on the main branch of he repo:

    Merge commit '5975d9fde9b40d1a1a93fc53d469d3321fa25f91'

So the schema diff between the proposed commit and main is always empty in CI. I can try to be more specific using origin/main instead of main...

[openshift-ci]

@gibizer: 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/precommit-check	ce9cdc7	link	true	/test precommit-check

Full PR test history. Your PR dashboard.

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.