Skip to content

modules/update-upgrading-cli: Use 'oc adm upgrade' for current status#53054

Closed
wking wants to merge 1 commit intoopenshift:mainfrom
wking:oc-adm-upgrade-for-current-status
Closed

modules/update-upgrading-cli: Use 'oc adm upgrade' for current status#53054
wking wants to merge 1 commit intoopenshift:mainfrom
wking:oc-adm-upgrade-for-current-status

Conversation

@wking
Copy link
Copy Markdown
Member

@wking wking commented Nov 21, 2022

It's our command-line interface for pretty-printing the current ClusterVersion status. And customers may not have jq installed, and we shouldn't be asking them to install it.

Preview.

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 21, 2022
@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented Nov 21, 2022

🤖 Updated build preview is available at:
https://53054--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/4190

Copy link
Copy Markdown
Contributor

@kalexand-rh kalexand-rh left a comment

Choose a reason for hiding this comment

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

@jiajliu or @shellyyang1989, will you PTAL and confirm which versions this change applies to?

Comment thread modules/update-upgrading-cli.adoc Outdated
Comment thread modules/update-upgrading-cli.adoc Outdated
It's our command-line interface for pretty-printing the current
ClusterVersion status.  And customers may not have 'jq' installed, and
we shouldn't be asking them to install it.
@wking wking force-pushed the oc-adm-upgrade-for-current-status branch from 9afeaa7 to 37cc657 Compare November 28, 2022 22:22
@wking
Copy link
Copy Markdown
Member Author

wking commented Nov 28, 2022

... confirm which versions this change applies to?

This could go back to 4.8, which currently requires jq as a nominal prerequisite, and 4.7 and earlier are already end-off-life. I'm agnostic about how far it actually gets picked back though, since we've asked folks to install jq for quite a while now, and only recently had @obrown1205 identified it as a rough edge that could use smoothing off.

@shellyyang1989
Copy link
Copy Markdown

/lgtm

BTW, the cluster version in the example needs to be updated based on which version the change goes to.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 29, 2022
@obrown1205
Copy link
Copy Markdown
Contributor

/label peer-review-needed

@openshift-ci openshift-ci Bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jan 6, 2023
@GroceryBoyJr
Copy link
Copy Markdown
Contributor

/remove-label peer-review-needed
/label peer-review-in-progress

@openshift-ci openshift-ci Bot added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jan 6, 2023
Copy link
Copy Markdown
Contributor

@GroceryBoyJr GroceryBoyJr left a comment

Choose a reason for hiding this comment

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

/LGTM

@GroceryBoyJr
Copy link
Copy Markdown
Contributor

/remove-label peer-review-in-progress
/label peer-review-done

@openshift-ci openshift-ci Bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jan 6, 2023
@shellyyang1989
Copy link
Copy Markdown

If it goes to 4.11, it looks good to me. Or else the cluster version in the example is worth to update accordingly.

@kalexand-rh
Copy link
Copy Markdown
Contributor

Then this will need a separate PR for 4.12 and any other versions that you want to backport it to.

@obrown1205
Copy link
Copy Markdown
Contributor

@wking I'm going to create another PR to include your changes here and avoid the merge conflicts from 67e04c2#diff-a4543a07ef809868d1b552e88f1c5a5b4dbbc99a3ff5c769ec4ad63cd55d0b4dL131-R131
keeping this open for reference

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 19, 2023
@openshift-merge-robot
Copy link
Copy Markdown

@wking: PR needs rebase.

Details

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-bot
Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 20, 2023
@openshift-bot
Copy link
Copy Markdown

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 21, 2023
@openshift-bot
Copy link
Copy Markdown

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Jun 20, 2023
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jun 20, 2023

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.11 lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants