OCPBUGS-62722: (cherry-pick) Fix truncate large error messages and unhandle changes for crd upgrade safety in status conditions

[camilamacedo86]

Description

ClusterExtension upgrade could fail due to oversized CRD validation status updates

When upgrading a ClusterExtension, CRD validation status updates could exceed the Kubernetes 32 KB limit, causing the update to fail with the error “Too long: may not be more than 32768 bytes.” This prevented the ClusterExtension status from being updated, leaving no status conditions or information about why the upgrade did not occur.

This issue occurred when the crddiff library returned a large JSON diff for unhandled CRD changes.

The problem has been resolved by truncating and summarising the diff output for unhandled scenarios, instead of including the full JSON diff. This ensures status updates remain within size limits and users receive clear, actionable error messages.

Cherry-picks

• Cherry-pick of: 0c6b003
• Cherry-pick of: 525f497

More info

To address the fix verified for 4.21 to 4.20 ( version where the bug was reported initially).
More info: https://issues.redhat.com/browse/OCPBUGS-59518?focusedId=28188598&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28188598

[openshift-ci-robot]

@camilamacedo86: This pull request references Jira Issue OCPBUGS-62722, which is invalid:

• expected the bug to target the "4.20.0" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-59518 to target a version in 4.21.0, 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:

• Cherry-pick of: 0c6b003
• Cherry-pick of: 525f497

To address the fix verified for 4.21 to 4.20 ( version where the bug was reported initially).
More info: https://issues.redhat.com/browse/OCPBUGS-59518?focusedId=28188598&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28188598

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.

[camilamacedo86]

/jira refresh

[openshift-ci-robot]

@camilamacedo86: This pull request references Jira Issue OCPBUGS-62722, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-59518 to target a version in 4.21.0, 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.

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.

[openshift-ci-robot]

@camilamacedo86: This pull request references Jira Issue OCPBUGS-62722, which is invalid:

• expected dependent Jira Issue OCPBUGS-59518 to target a version in 4.21.0, 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.

In response to this:

Description

When upgrading a ClusterExtension, CRD validation status updates could exceed the Kubernetes 32 KB limit, causing the update to fail with the error “Too long: may not be more than 32768 bytes.” This prevented the ClusterExtension status from being updated, leaving no status conditions or information about why the upgrade did not occur.

This issue occurred when the crddiff library returned a large JSON diff for unhandled CRD changes.

The problem has been resolved by truncating and summarising the diff output for unhandled scenarios, instead of including the full JSON diff. This ensures status updates remain within size limits and users receive clear, actionable error messages.

Cherry-picks

• Cherry-pick of: 0c6b003
• Cherry-pick of: 525f497

More info

To address the fix verified for 4.21 to 4.20 ( version where the bug was reported initially).
More info: https://issues.redhat.com/browse/OCPBUGS-59518?focusedId=28188598&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28188598

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.

[camilamacedo86]

/jira refresh

[openshift-ci-robot]

@camilamacedo86: This pull request references Jira Issue OCPBUGS-62722, which is invalid:

• expected dependent Jira Issue OCPBUGS-59518 to target a version in 4.21.0, 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.

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.

[camilamacedo86]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-59518 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-59518 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), 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 openshift-eng/jira-lifecycle-plugin repository.

[bandrade]

/label qe-approved
/verified by @bandrade

[openshift-ci-robot]

@camilamacedo86: This pull request references Jira Issue OCPBUGS-62722, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• 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
• dependent bug Jira Issue OCPBUGS-59518 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-59518 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

In response to this:

Description

ClusterExtension upgrade could fail due to oversized CRD validation status updates

When upgrading a ClusterExtension, CRD validation status updates could exceed the Kubernetes 32 KB limit, causing the update to fail with the error “Too long: may not be more than 32768 bytes.” This prevented the ClusterExtension status from being updated, leaving no status conditions or information about why the upgrade did not occur.

This issue occurred when the crddiff library returned a large JSON diff for unhandled CRD changes.

The problem has been resolved by truncating and summarising the diff output for unhandled scenarios, instead of including the full JSON diff. This ensures status updates remain within size limits and users receive clear, actionable error messages.

Cherry-picks

• Cherry-pick of: 0c6b003
• Cherry-pick of: 525f497

More info

To address the fix verified for 4.21 to 4.20 ( version where the bug was reported initially).
More info: https://issues.redhat.com/browse/OCPBUGS-59518?focusedId=28188598&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28188598

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]

@bandrade: This PR has been marked as verified by @bandrade.

In response to this:

/label qe-approved
/verified by @bandrade

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.

[tmshort]

/lgtm
/approved

[tmshort]

Still have a problem in techpreview

[camilamacedo86]

/test openshift-e2e-aws-techpreview

[openshift-ci]

@camilamacedo86: all tests passed!

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.

[tmshort]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, 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

[oceanc80]

/label backport-risk-assessed

[openshift-ci-robot]

@camilamacedo86: Jira Issue OCPBUGS-62722: All pull requests linked via external trackers have merged:

• openshift/operator-framework-operator-controller#496
• operator-framework/operator-controller#216
• operator-framework/operator-controller#2179
• openshift/operator-framework-operator-controller#456
• openshift/operator-framework-operator-controller#492

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

In response to this:

Description

ClusterExtension upgrade could fail due to oversized CRD validation status updates

When upgrading a ClusterExtension, CRD validation status updates could exceed the Kubernetes 32 KB limit, causing the update to fail with the error “Too long: may not be more than 32768 bytes.” This prevented the ClusterExtension status from being updated, leaving no status conditions or information about why the upgrade did not occur.

This issue occurred when the crddiff library returned a large JSON diff for unhandled CRD changes.

The problem has been resolved by truncating and summarising the diff output for unhandled scenarios, instead of including the full JSON diff. This ensures status updates remain within size limits and users receive clear, actionable error messages.

Cherry-picks

• Cherry-pick of: 0c6b003
• Cherry-pick of: 525f497

More info

To address the fix verified for 4.21 to 4.20 ( version where the bug was reported initially).
More info: https://issues.redhat.com/browse/OCPBUGS-59518?focusedId=28188598&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28188598

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.