Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONSOLE-3084: frontend/packages/console-shared/src/hooks/useCanClusterUpgrade: Not ROSA #13184

Merged

Conversation

wking
Copy link
Member

@wking wking commented Sep 21, 2023

ROSA cluster updates are via OCM:

There are three methods to upgrade Red Hat OpenShift Service on AWS (ROSA) clusters:

  • Individual upgrades through the ROSA CLI (rosa)
  • Individual upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console
  • Recurring upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console

This is similar to OpenShift Dedicated (OSD), although there is no OSD command-line client analogous to rosa. This catches this one function up with f783d87 (#12889), CC @rhamilto, although I have not audited to see if there are other branding consumers that might want similar updates.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 21, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 21, 2023

@wking: This pull request references CONSOLE-3084 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set.

In response to this:

ROSA cluster updates are via OCM:

There are three methods to upgrade Red Hat OpenShift Service on AWS (ROSA) clusters:

  • Individual upgrades through the ROSA CLI (rosa)
  • Individual upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console
  • Recurring upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console

This is similar to OpenShift Dedicated (OSD), although there is no OSD command-line client analogous to rosa. This catches this one function up with f783d87 (#12889), CC @rhamilto, although I have not audited to see if there are other branding consumers that might want similar updates.

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.

@openshift-ci openshift-ci bot added the component/shared Related to console-shared label Sep 21, 2023
@rhamilto
Copy link
Member

Thanks, @wking. Note the rosa branding option is new-ish. Will want to work with the packaging team to make sure they are using it, otherwise this fix won't work.

@rhamilto
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 21, 2023
@wking
Copy link
Member Author

wking commented Sep 22, 2023

Neither failure seems relevant, and pull-ci-openshift-console-master-e2e-gcp-console seems pretty dead, but:

/retest-required

Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wking you need to run yarn prettier-all to properly format the changes

@wking wking force-pushed the rosa-updates-are-not-in-cluster branch from 9d11ec6 to b7261e9 Compare September 22, 2023 17:07
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2023
@wking
Copy link
Member Author

wking commented Sep 22, 2023

I don't have yarn installed locally, and CI:

/go/src/github.com/openshift/console/frontend/packages/console-shared/src/hooks/useCanClusterUpgrade.ts
  16:33  error  Insert `⏎···`  prettier/prettier
  17:28  error  Insert `⏎···`  prettier/prettier

suggests line wrapping, but doesn't print a convenient diff for me to apply as a patch. But I've taken a guess and pushed 9d11ec6 -> b7261e9.

…ROSA

ROSA cluster updates are via OCM [1]:

  There are three methods to upgrade Red Hat OpenShift Service on AWS (ROSA) clusters:

  * Individual upgrades through the ROSA CLI (rosa)
  * Individual upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console
  * Recurring upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console

This is similar to OpenShift Dedicated (OSD) [2], although there is no
OSD command-line client analogous to 'rosa'.  This catches this one
function up with f783d87 (OCPBUGS-14716: add ROSA branding option,
2023-06-12, openshift#12889), although I have not audited to see if there are
other branding consumers that might want similar updates.

[1]: https://docs.openshift.com/rosa/upgrading/rosa-upgrading.html#rosa-sts-upgrading-a-cluster
[2]: https://docs.openshift.com/dedicated/upgrading/osd-upgrades.html
@wking wking force-pushed the rosa-updates-are-not-in-cluster branch from b7261e9 to ad7fc68 Compare September 22, 2023 18:14
Copy link
Member

@rhamilto rhamilto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhamilto, wking

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:

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

@rhamilto
Copy link
Member

/retest

@rhamilto
Copy link
Member

QE Approver:

/assign @yanpzhan
PX Approver:
/assign @RickJWagner
Docs Approver:
/assign @opayne1

@opayne1
Copy link
Contributor

opayne1 commented Sep 25, 2023

/label docs-approved

@openshift-ci openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Sep 25, 2023
@RickJWagner
Copy link

/label px-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Sep 25, 2023
@RickJWagner RickJWagner removed their assignment Sep 25, 2023
@yanpzhan
Copy link
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 11, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 11, 2023

@wking: This pull request references CONSOLE-3084 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set.

In response to this:

ROSA cluster updates are via OCM:

There are three methods to upgrade Red Hat OpenShift Service on AWS (ROSA) clusters:

  • Individual upgrades through the ROSA CLI (rosa)
  • Individual upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console
  • Recurring upgrades through the OpenShift Cluster Manager Hybrid Cloud Console console

This is similar to OpenShift Dedicated (OSD), although there is no OSD command-line client analogous to rosa. This catches this one function up with f783d87 (#12889), CC @rhamilto, although I have not audited to see if there are other branding consumers that might want similar updates.

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 11, 2023

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

@openshift-ci openshift-ci bot merged commit d543e01 into openshift:master Oct 11, 2023
6 checks passed
@wking wking deleted the rosa-updates-are-not-in-cluster branch October 12, 2023 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. component/shared Related to console-shared docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants