pkg/cli/admin/upgrade/status: Add update duration #1583
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As a cluster admin, I want to understand how the update is going, relative to my expectations around duration [1]. If it's waiting on the Kube API server 5 minutes into the update, that's expected. If it's waiting on the Kube API server an hour into the update, that's unexpected. There is not a lot of information here, but while it is a small amount of context, it only consumes a few characters. $ OC_ENABLE_CMD_UPGRADE_STATUS=true ./oc adm upgrade status An update is in progress for 44m40s: Working towards 4.13.17: 683 of 843 done (81% complete), waiting on network [1]: https://docs.openshift.com/container-platform/4.14/updating/understanding_updates/understanding-openshift-update-duration.html
openshift-ci
bot
added
the
approved
|
/cc |
petr-muller
approved these changes
Oct 20, 2023
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petr-muller, 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 |
|
/retest-required |
|
@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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a cluster admin, I want to understand how the update is going, relative to my expectations around duration. If it's waiting on the Kube API server 5 minutes into the update, that's expected. If it's waiting on the Kube API server an hour into the update, that's unexpected. There is not a lot of information here, but while it is a small amount of context, it only consumes a few characters.