-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-12713 CVO log levels release note #100340
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
OSDOCS-12713 CVO log levels release note #100340
Conversation
bab43d9 to
b39b3c8
Compare
|
\lgtm |
|
/lgtm |
|
/hold |
|
/unhold |
|
🤖 Wed Oct 15 15:52:17 - Prow CI generated the docs preview: |
|
@JianLi-RH Could you PTAL? |
|
@DavidHurta Will we cherry-pick 1232 to 4.20? If yes, when will the change be merged into payload? As I know |
|
@cbippley @DavidHurta If we really want to announce this feature in 4.20 release note, we would also want to add it in to #99971 |
Oh, I see, we already listed it as |
|
/lgtm |
|
/label merge-review-needed |
|
|
||
| With this release, the Cluster Version Operator (CVO) log level verbosity can be changed by the cluster administrator. | ||
|
|
||
| For more information, see xref:../updating/troubleshooting_updates/gathering-data-cluster-update.adoc#changing-log-data_troubleshooting_updates[Changing the CVO log level]. |
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.
When I click this link, I'm brought to the "Gathering data about your cluster update" document but I do not see a section named Changing the CVO log level.I do not see the term "log level" used in the .
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'll try and fix it now that I've merged the other doc changes.
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.
@dfitzmau I think I fixed it. Please try again.
|
Hi, @cbippley . Just one comment. Please let me know what you think. |
b39b3c8 to
9c45d4b
Compare
|
New changes are detected. LGTM label has been removed. |
9c45d4b to
86c7ff1
Compare
|
|
||
| With this release, the Cluster Version Operator (CVO) log level verbosity can be changed by the cluster administrator. | ||
|
|
||
| For more information, see xref:../updating/troubleshooting_updates/gathering-data-cluster-update.adoc#changing-log-data_troubleshooting_updates[Changing CVO log level]. |
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.
| For more information, see xref:../updating/troubleshooting_updates/gathering-data-cluster-update.adoc#changing-log-data_troubleshooting_updates[Changing CVO log level]. | |
| For more information, see xref:../updating/troubleshooting_updates/gathering-data-cluster-update.adoc#changing-log-data_gathering-data-cluster-update[Changing CVO log level]. |
I think this is the correct link structure.
86c7ff1 to
b00d412
Compare
|
@cbippley: 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-sigs/prow repository. I understand the commands that are listed here. |
Version(s): 4.20
Issue: OSDOCS-12713
Link to docs preview: https://100340--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-20-release-notes.html#ocp-4-20-install-update-cvo-log-levels_release-notes
QE review:
Additional information: