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

OCM-6697 | fix: upgrade role error should print extra info when invoke from upgrade cluster #1878

Merged
merged 1 commit into from Apr 3, 2024

Conversation

mikeshng
Copy link
Member

In PR, some of the error handlings were removed. I've gone through each one of them and brought back the one that should be present: upgrade role error handling when invoke from upgrade cluster.

Jira ref

Copy link

codecov bot commented Mar 27, 2024

Codecov Report

Attention: Patch coverage is 0% with 16 lines in your changes are missing coverage. Please review.

Project coverage is 20.75%. Comparing base (9a635e0) to head (eed055a).
Report is 30 commits behind head on master.

Files Patch % Lines
cmd/upgrade/roles/cmd.go 0.00% 16 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1878      +/-   ##
==========================================
- Coverage   21.82%   20.75%   -1.08%     
==========================================
  Files         117      118       +1     
  Lines       18921    20853    +1932     
==========================================
+ Hits         4129     4327     +198     
- Misses      14481    16147    +1666     
- Partials      311      379      +68     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@chenz4027
Copy link
Contributor

/lgtm
I kinda wanna propose adding unit test for printClusterUpgradeInfo, but it might be tough for reporter. Up to you Mike.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 27, 2024
@oriAdler
Copy link
Contributor

LGTM, can you please attach a sample output to the PR? just to get a sense of how the info message looks to the user?

cmd/upgrade/roles/cmd.go Outdated Show resolved Hide resolved
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 28, 2024
@mikeshng mikeshng force-pushed the OCM-6697 branch 2 times, most recently from afaf377 to 58f11f9 Compare March 28, 2024 16:28
@mikeshng
Copy link
Member Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 28, 2024
…e from upgrade cluster

Signed-off-by: Mike Ng <ming@redhat.com>
@mikeshng
Copy link
Member Author

LGTM, can you please attach a sample output to the PR? just to get a sense of how the info message looks to the user?

I: Account/Operator Role policies are not valid with upgrade version 4.15. Run the following command(s) to upgrade the roles:
        rosa upgrade roles -c redacted_cluster_id_string_here --cluster-version=4.15 --mode=auto

, then run the upgrade command again:
	rosa upgrade cluster -c redacted_cluster_id_string_here

@oriAdler PTAL thanks

@mikeshng
Copy link
Member Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 28, 2024
Copy link
Contributor

@chenz4027 chenz4027 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 Apr 2, 2024
@robpblake
Copy link
Contributor

/lgtm

Copy link
Contributor

openshift-ci bot commented Apr 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chenz4027, mikeshng, robpblake

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 3, 2024
Copy link
Contributor

openshift-ci bot commented Apr 3, 2024

@mikeshng: 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-merge-bot openshift-merge-bot bot merged commit 6f1f390 into openshift:master Apr 3, 2024
9 checks passed
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants