-
Notifications
You must be signed in to change notification settings - Fork 377
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
OTA-1292: upgrade-status: improve messages for NotReady/DiskPressure/NetworkUnavailable #1851
Conversation
@hongkailiu: This pull request references OTA-1292 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.18.0" version, but no target version was set. In response to this:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know the PR is marked wip
but I thought I'd give some feedback, less about the code but perhaps on the functionality
...rade/status/examples/4.16.0-ec2-control-plane-updated-pdb-prohibits-draining.detailed-output
Outdated
Show resolved
Hide resolved
...admin/upgrade/status/examples/4.16.0-ec2-control-plane-updated-pdb-prohibits-draining.output
Outdated
Show resolved
Hide resolved
I will follow up tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change looks good! I feel like we're changing the logic fairly significantly but we don't have many tests to exercise the new behavior, so I would feel safer if we had some basic testcases for the improved logic: given a node in a certain state, what is the expected status we report, and what are the insights we report (as unit tests, not the example ones, although having one example showing multiple conditions like not ready && disk pressure would not hurt)
We don't need 100% code coverage for all possible cases ofc, but reasonable coverage of the main branches (unschedulable node, node with a bad condition but below the duraiton threshold, node with multiple bad conditions sound like the basic cases?).
…NetworkUnavailable
@hongkailiu: The following test failed, say
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, great work!
/lgtm
/hold
Holding to give QE chance to test this before merging (writing brief testing instructions may be handy for them to help verifying the new behavior)
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hongkailiu, petr-muller 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 |
follow up the discussion in the ticket, considering this one pre-merge verified |
@hongkailiu: This pull request references OTA-1292 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.18.0" version, but no target version was set. In response to this:
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. |
4682bd8
into
openshift:master
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-cli |
[ART PR BUILD NOTIFIER] Distgit: ose-tools |
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-deployer |
[ART PR BUILD NOTIFIER] Distgit: ose-cli-artifacts |
https://issues.redhat.com/browse/OTA-1292
Addressing the 4th case from #1838 (review)
/cc @petr-muller @Davoska