[release-4.14] OCPBUGS-90614: Fix JSON annotation parsing to prevent OperatorHub crash

[openshift-cherrypick-robot]

This is an automated cherry-pick of #16588

/assign cardil

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6da15b14-314d-4681-97d3-5aef82ed64e5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

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]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-88027 has been cloned as Jira Issue OCPBUGS-90614. Will retitle bug to link to clone.
/retitle [release-4.14] OCPBUGS-90614: Fix JSON annotation parsing to prevent OperatorHub crash

Details

In response to this:

This is an automated cherry-pick of #16588

/assign cardil

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-90614, which is invalid:

• expected dependent Jira Issue OCPBUGS-88027 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
• expected dependent Jira Issue OCPBUGS-88027 to target a version in 4.15.0, 4.15.z, but it targets "4.16.z" instead

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.

Details

In response to this:

This is an automated cherry-pick of #16588

/assign cardil

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.

[cardil]

/jira refresh

[cardil]

/retest

[openshift-ci-robot]

@cardil: This pull request references Jira Issue OCPBUGS-90614, which is invalid:

• expected dependent Jira Issue OCPBUGS-88027 to target a version in 4.15.0, 4.15.z, but it targets "4.16.z" instead

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.

Details

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

[cardil]

This backport is stuck on the jira-lifecycle-plugin's sequential-backport-chain check.

OCPBUGS-90614 targets 4.14.z, but its "is blocked by" link points to OCPBUGS-88027, which targets 4.16.z — two versions away, not the adjacent 4.15.z the check expects. No 4.15.z clone of OCPBUGS-88027 exists, because release-4.15 is a non-EUS release currently in CVE-only maintenance, so this defect isn't being backported there. There's nothing to link to and nothing to backport further.

/assign @germanparente
Could you apply jira/skip-dependent-bug-check here?

/assign @cajieh
Once that clears, this will still need approved / lgtm / backport-risk-assessed / verified — could you take a look?

[cardil]

Related #16660

[germanparente]

@cardil I think that cherry pick is jumping from 4.16 to 4.14 to 4.12 and not considering needed silent releases. I can skip but this has to be fixed in all the releases.

[germanparente]

/label jira/skip-dependent-bug-check

[openshift-ci-robot]

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

4 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template

Details

In response to this:

This is an automated cherry-pick of #16588

/assign cardil

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.

[cardil]

/retest

[cardil]

@germanparente: I think that cherry pick is jumping from 4.16 to 4.14 to 4.12 and not considering needed silent releases. I can skip but this has to be fixed in all the releases.

Oh, really? I thought I should skip 4.15 and 4.13 as EoL. But you say otherwise, so I just file cherry pick to those missing releases as well.

[cardil]

@germanparente Just wanted to clarify — exact dates, per Red Hat's official life-cycle dates: 4.13 has been EOL since 2024-11-17, 4.15 since 2025-08-27. 4.12 and 4.14 are still in EUS phase.

I'm filing those cherry-picks, but are you sure that's the right thing to do?

[cardil]

/jira refresh

[openshift-ci-robot]

@cardil: This pull request references Jira Issue OCPBUGS-90614, which is valid.

4 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template

Details

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

[germanparente]

@cardil yes, we fix 4.13 and 4.15 releases since they are silent and we use to do EUS-to-EUS upgrade, like for example from 4.14 to 4.16, we need to upgrade the masters to 4.15 first and only temporarily. So, we fix all the cve's also in 4.15 and we deliver the release silently.

[cajieh]

/test e2e-gcp-console

[cajieh]

/test e2e-gcp-console

[cajieh]

/test e2e-gcp-console

[cajieh]

/retest

[openshift-ci]

@openshift-cherrypick-robot: 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-console	68375c6	link	true	/test e2e-gcp-console

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.