Skip to content

Conversation

@cbippley
Copy link
Contributor

@cbippley cbippley commented Oct 10, 2025

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 10, 2025
@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 10, 2025
@DavidHurta
Copy link

\lgtm

@DavidHurta
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 10, 2025
@DavidHurta
Copy link

DavidHurta commented Oct 10, 2025

/hold
a discussion in Slack related to the functionality

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 10, 2025
@DavidHurta
Copy link

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 10, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Oct 10, 2025

🤖 Wed Oct 15 15:52:17 - Prow CI generated the docs preview:

https://100340--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-20-release-notes.html

@cbippley
Copy link
Contributor Author

@JianLi-RH Could you PTAL?

@JianLi-RH
Copy link

JianLi-RH commented Oct 11, 2025

@DavidHurta Will we cherry-pick 1232 to 4.20? If yes, when will the change be merged into payload? As I know Monday we promoted 4.20.0-rc.3 which we hope to be a final releasable build. and 4.20.0-rc.3 was created on Sep 29 2025. That means in the first few GA versions, we will not include this feature in those versions. So there is a gap between 4.20 GA and CVO log level feature available in TP cluster.
If we announce this feature in release note, readers might be confused.

@JianLi-RH
Copy link

@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

@JianLi-RH
Copy link

@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 ClusterVersionOperatorConfiguration

@JianLi-RH
Copy link

/lgtm

@cbippley
Copy link
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 15, 2025
@dfitzmau dfitzmau 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 15, 2025

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].
Copy link
Contributor

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 .

Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

@dfitzmau
Copy link
Contributor

Hi, @cbippley . Just one comment. Please let me know what you think.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2025
@openshift-ci
Copy link

openshift-ci bot commented Oct 15, 2025

New changes are detected. LGTM label has been removed.


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].
Copy link
Contributor

@dfitzmau dfitzmau Oct 15, 2025

Choose a reason for hiding this comment

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

Suggested change
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.

@openshift-ci
Copy link

openshift-ci bot commented Oct 15, 2025

@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.

@dfitzmau dfitzmau merged commit b7d6ecb into openshift:enterprise-4.20 Oct 15, 2025
2 checks passed
@dfitzmau dfitzmau added branch/enterprise-4.20 and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR labels Oct 15, 2025
@cbippley cbippley deleted the OSDOCS-12713-420rn branch October 15, 2025 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.20 size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants