Skip to content

[OCPBUGS#9167]: Updated oc adm upgrade output to reflect 4.14 oc client #65618

Merged
skrthomas merged 1 commit intoopenshift:mainfrom
obrown1205:updatingcluster_CLI
Oct 9, 2023
Merged

[OCPBUGS#9167]: Updated oc adm upgrade output to reflect 4.14 oc client #65618
skrthomas merged 1 commit intoopenshift:mainfrom
obrown1205:updatingcluster_CLI

Conversation

@obrown1205
Copy link
Copy Markdown
Contributor

@obrown1205 obrown1205 commented Oct 2, 2023

@openshift-ci openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 2, 2023
@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented Oct 2, 2023

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

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

@obrown1205 obrown1205 force-pushed the updatingcluster_CLI branch 2 times, most recently from 0b11f13 to 51d9c66 Compare October 5, 2023 14:24
@obrown1205 obrown1205 changed the title [OCPBUGS#9167]: Updated oc adm upgrade output to reflect 4.10 oc client [OCPBUGS#9167]: Updated oc adm upgrade output to reflect 4.14 oc client Oct 5, 2023
Comment thread modules/update-upgrading-cli.adoc Outdated
====

. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.12`, `fast-4.12`, or `eus-4.12`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13`, `fast-4.13`, or `eus-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There's no eus-4.13, it's only for even releases. So 4.13.z releases will only show up in an eus-4.14 channel, and even that won't happen until 45 to 90 days after 4.14 GAs.

Comment thread modules/update-upgrading-cli.adoc Outdated

Upstream is unset, so the cluster will use an appropriate default.
Channel: stable-4.10 (available channels: candidate-4.10, candidate-4.11, eus-4.10, fast-4.10, fast-4.11, stable-4.10)
Channel: stable-version (available channels: candidate-version, eus-version, fast-version, stable-version)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Down below, you're using <version>. I'm agnostic about whether you want to mark these placeholders or not, but whichever way you go, it's probably worth being consistent.

Comment thread modules/update-upgrading-cli.adoc Outdated
====

. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.12`, `fast-4.12`, or `eus-4.12`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

we can keep the reference to fast-4.13 here. It's everything from Channel: ... (available channels: <anything from here>), with the caveat that candidate-4.y channels will not limit you to supported releases.

Comment thread modules/update-upgrading-cli.adoc Outdated

Upstream is unset, so the cluster will use an appropriate default.
Channel: stable-4.10 (available channels: candidate-4.10, candidate-4.11, eus-4.10, fast-4.10, fast-4.11, stable-4.10)
Channel: stable-<version> (available channels: candidate-<version>, eus-<version>, fast-<version>, <stable-version>)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: <stable-version> -> stable-<version>.

Copy link
Copy Markdown
Member

@wking wking 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 Oct 6, 2023

Upstream is unset, so the cluster will use an appropriate default.
Channel: stable-4.10 (available channels: candidate-4.10, candidate-4.11, eus-4.10, fast-4.10, fast-4.11, stable-4.10)
Channel: stable-<version> (available channels: candidate-<version>, eus-<version>, fast-<version>, stable-<version>)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It's the output of oc adm upgrade instead of oc get clusterversion in line https://github.com/openshift/openshift-docs/pull/65618/files#diff-a4543a07ef809868d1b552e88f1c5a5b4dbbc99a3ff5c769ec4ad63cd55d0b4dL120
We can update it to oc adm upgrade

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done :) ty!

@obrown1205 obrown1205 force-pushed the updatingcluster_CLI branch from 58466be to bd8b168 Compare October 9, 2023 14:13
@openshift-ci openshift-ci Bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 9, 2023
@obrown1205 obrown1205 force-pushed the updatingcluster_CLI branch from bd8b168 to 2c88d0c Compare October 9, 2023 14:39
@obrown1205
Copy link
Copy Markdown
Contributor Author

/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 Oct 9, 2023
@bburt-rh bburt-rh added peer-review-in-progress Signifies that the peer review team is reviewing this PR branch/enterprise-4.14 and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Oct 9, 2023
@bburt-rh bburt-rh added this to the Planned for 4.14 GA milestone Oct 9, 2023
Copy link
Copy Markdown
Contributor

@bburt-rh bburt-rh left a comment

Choose a reason for hiding this comment

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

One tiny nitpick, but otherwise lgtm! Thank you.

====

. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.12`, `fast-4.12`, or `eus-4.12`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13` or `fast-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
. Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13` or `fast-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section.
. Based on your organization's requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13` or `fast-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the "Additional resources" section.
  • Per ISG, "If you refer to a smaller piece of work within a larger container such as a chapter within a book or an article in a magazine, use italic font for the larger container and double quotation marks for the smaller piece."

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Resolved :)

@bburt-rh bburt-rh 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 Oct 9, 2023
@obrown1205 obrown1205 force-pushed the updatingcluster_CLI branch from 2c88d0c to 4d90d6d Compare October 9, 2023 16:10
@obrown1205 obrown1205 force-pushed the updatingcluster_CLI branch from 4d90d6d to c041f25 Compare October 9, 2023 17:26
@obrown1205
Copy link
Copy Markdown
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci Bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Oct 9, 2023
@skrthomas skrthomas added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Oct 9, 2023
Copy link
Copy Markdown
Contributor

@skrthomas skrthomas left a comment

Choose a reason for hiding this comment

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

/lgtm

@skrthomas skrthomas merged commit f6cba4d into openshift:main Oct 9, 2023
@skrthomas
Copy link
Copy Markdown
Contributor

/cherrypick enterprise-4.14

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 9, 2023
@openshift-cherrypick-robot
Copy link
Copy Markdown

@skrthomas: new pull request created: #65964

Details

In response to this:

/cherrypick enterprise-4.14

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.14 lgtm Indicates that a PR is ready to be merged. merge-review-in-progress Signifies that the merge review team is reviewing this PR 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.

7 participants