OCPBUGS-18948: CRD Compatibility Validation

[dtfranz]

Correct CRD validation to validate CRs against each version of the updated CRD.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 242f63f

[openshift-ci-robot]

@dtfranz: This pull request references Jira Issue OCPBUGS-18948, which is invalid:

• expected the bug to target the "4.15.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Correct CRD validation to validate CRs against each version of the updated CRD.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 242f63f

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.

[dtfranz]

/jira refresh

[openshift-ci-robot]

@dtfranz: This pull request references Jira Issue OCPBUGS-18948, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

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.

[eggfoobar]

/retest-required

[tmshort]

This should wait for the automated sync... and everything else that's happening to fix testing.

[dtfranz]

This should wait for the automated sync... and everything else that's happening to fix testing.

Gotcha, I figured since the periodic job was failing then doing it manually would be the right move, but if you don't think so I can close this.

[openshift-ci]

@dtfranz: 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/e2e-gcp-olm-flaky	4f9113e	link	false	/test e2e-gcp-olm-flaky

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

[tmshort]

/retest

[tmshort]

/test e2e-gcp-olm

[tmshort]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtfranz, tmshort

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:

• DOWNSTREAM_OWNERS [tmshort]

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

[openshift-ci-robot]

@dtfranz: Jira Issue OCPBUGS-18948: All pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#592

Jira Issue OCPBUGS-18948 has been moved to the MODIFIED state.

In response to this:

Correct CRD validation to validate CRs against each version of the updated CRD.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 242f63f

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.