[release-4.17] OCPBUGS-56375: remove 60 day alert from cluster update modal

[openshift-cherrypick-robot]

This is an automated cherry-pick of #15055

/assign rhamilto

/cherrypick release-4.16

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56255 has been cloned as Jira Issue OCPBUGS-56375. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-56375: remove 60 day alert from cluster update modal

In response to this:

This is an automated cherry-pick of #15055

/assign rhamilto

/cherrypick release-4.16

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.

[rhamilto]

/approve
/lgtm
/label backport-risk-assessed

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-56255 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

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:

This is an automated cherry-pick of #15055

/assign rhamilto

/cherrypick release-4.16

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, rhamilto

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:

• frontend/OWNERS [rhamilto]

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

[rhamilto]

/test e2e-gcp-console

[yanpzhan]

Checked on cluster launched against the pr, there was new update available, clicked 'Select a version' button, chose 'Control plane only update', there was not message about resuming in 60 days.
/label qe-approved
/label cherry-pick-approved

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-56255 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

In response to this:

This is an automated cherry-pick of #15055

/assign rhamilto

/cherrypick release-4.16

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.

[rhamilto]

/jira refresh
/retest

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-56375, 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.17.z) matches configured target version for branch (4.17.z)
• 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-56255 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-56255 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh
/retest

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.

[rhamilto]

/test e2e-gcp-console

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f9c412e and 2 for PR HEAD 75f9ecb in total

[rhamilto]

/test e2e-gcp-console

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c56591f and 1 for PR HEAD 75f9ecb in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c56591f and 2 for PR HEAD 75f9ecb in total

[openshift-ci]

@openshift-cherrypick-robot: 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.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56375: All pull requests linked via external trackers have merged:

• openshift/console#15062

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

In response to this:

This is an automated cherry-pick of #15055

/assign rhamilto

/cherrypick release-4.16

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-cherrypick-robot]

@openshift-cherrypick-robot: #15062 failed to apply on top of branch "release-4.16":

Applying: OCPBUGS-56255: remove 60 day alert from cluster update modal
Using index info to reconstruct a base tree...
M	frontend/public/components/modals/cluster-update-modal.tsx
M	frontend/public/components/utils/documentation.tsx
M	frontend/public/locales/en/public.json
Falling back to patching base and 3-way merge...
Auto-merging frontend/public/locales/en/public.json
CONFLICT (content): Merge conflict in frontend/public/locales/en/public.json
Auto-merging frontend/public/components/utils/documentation.tsx
Auto-merging frontend/public/components/modals/cluster-update-modal.tsx
CONFLICT (content): Merge conflict in frontend/public/components/modals/cluster-update-modal.tsx
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-56255: remove 60 day alert from cluster update modal

In response to this:

This is an automated cherry-pick of #15055

/assign rhamilto

/cherrypick release-4.16

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-console
This PR has been included in build openshift-enterprise-console-container-v4.17.0-202505290736.p0.g072738a.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.17.0-0.nightly-2025-05-29-102043