Skip to content

OSDOCS-16853-2:OVN-CQA-troubleshooting#112595

Merged
JoeAldinger merged 1 commit into
openshift:mainfrom
JoeAldinger:OSDOCS-16853-2
Jun 3, 2026
Merged

OSDOCS-16853-2:OVN-CQA-troubleshooting#112595
JoeAldinger merged 1 commit into
openshift:mainfrom
JoeAldinger:OSDOCS-16853-2

Conversation

@JoeAldinger
Copy link
Copy Markdown
Contributor

@JoeAldinger JoeAldinger commented Jun 1, 2026

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 1, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jun 1, 2026

@JoeAldinger: This pull request references OSDOCS-16853 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

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

ocpdocs-previewbot commented Jun 1, 2026

@JoeAldinger JoeAldinger added this to the Continuous Release milestone Jun 2, 2026
@JoeAldinger JoeAldinger added the merge-review-needed Signifies that the merge review team needs to review this PR label Jun 2, 2026
@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 Jun 3, 2026
Copy link
Copy Markdown
Contributor

@dfitzmau dfitzmau left a comment

Choose a reason for hiding this comment

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

Hi, @JoeAldinger . I've not checked the abstracts for technical accuracy as this should be outside the scope of CQA reviews?

[role="_abstract"]
To debug OVN-Kubernetes in {product-title}, you can raise log levels by applying an `env-overrides` `ConfigMap` and restarting affected pods.

The default log level for OVN-Kubernetes is 4. To debug OVN-Kubernetes, set the log level to 5. Follow this procedure to increase the log level of the OVN-Kubernetes to help you debug an issue.
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
The default log level for OVN-Kubernetes is 4. To debug OVN-Kubernetes, set the log level to 5. Follow this procedure to increase the log level of the OVN-Kubernetes to help you debug an issue.
The default log level for OVN-Kubernetes is 4. To debug OVN-Kubernetes, set the log level to 5. To help debug an issue, follow the procedure to increase the log level of the OVN-Kubernetes.

Removes the anthrophomorphism.

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.

This isn't anthropomorphism.

Comment thread modules/nw-ovn-kubernetes-change-log-levels.adoc Outdated
Comment thread modules/nw-ovn-kubernetes-logs-cli.adoc Outdated

You can view the logs for each of the pods in the `ovnkube-master` and `ovnkube-node` pods in the web console.
[role="_abstract"]
To view OVN-Kubernetes pod logs in the {product-title} web console, you can open pod logs for each container in the `openshift-ovn-kubernetes` project.
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.

Kind of deviates from the original that specifically mentions the pods.

Comment thread modules/observability-ovs-sampling-flags.adoc Outdated

toc::[]

OVN-Kubernetes has many sources of built-in health checks and logs. Follow the instructions in these sections to examine your cluster. If a support case is necessary, follow the xref:../../support/gathering-cluster-data.adoc#support_gathering_data_gathering-cluster-data[support guide] to collect additional information through a `must-gather`. Only use the `-- gather_network_logs` when instructed by support.
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.

Has this link been completely removed. The Monitoring application health by using health checks link covers this aspect?

@dfitzmau dfitzmau removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Jun 3, 2026
[role="_abstract"]
To troubleshoot OVN-Kubernetes in {product-title}, you can use built-in health checks, alerting, logs, and connectivity checks. Follow these sections to examine your cluster before opening a support case.

OVN-Kubernetes has many sources of built-in health checks and logs. Follow the instructions in these sections to examine your cluster. If a support case is necessary, collect additional information through a `must-gather` as described in the Additional resources section. Only use the `-- gather_network_logs` option when instructed by support.
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.

It is down here and has been reworded @dfitzmau

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jun 3, 2026

@JoeAldinger: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

@JoeAldinger JoeAldinger merged commit 805ef30 into openshift:main Jun 3, 2026
2 checks passed
@JoeAldinger
Copy link
Copy Markdown
Contributor Author

/cherrypick enterprise-4.22

@JoeAldinger
Copy link
Copy Markdown
Contributor Author

/cherrypick enterprsie-4.21

@JoeAldinger
Copy link
Copy Markdown
Contributor Author

/cherrypick enterprise-4.20

@openshift-cherrypick-robot
Copy link
Copy Markdown

@JoeAldinger: new pull request created: #112739

Details

In response to this:

/cherrypick enterprise-4.22

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.

@openshift-cherrypick-robot
Copy link
Copy Markdown

@JoeAldinger: cannot checkout enterprsie-4.21: error checking out "enterprsie-4.21": exit status 1 error: pathspec 'enterprsie-4.21' did not match any file(s) known to git

Details

In response to this:

/cherrypick enterprsie-4.21

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.

@openshift-cherrypick-robot
Copy link
Copy Markdown

@JoeAldinger: new pull request created: #112743

Details

In response to this:

/cherrypick enterprise-4.20

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.

@JoeAldinger
Copy link
Copy Markdown
Contributor Author

/cherrypick enterprise-4.21

@openshift-cherrypick-robot
Copy link
Copy Markdown

@JoeAldinger: new pull request created: #112744

Details

In response to this:

/cherrypick enterprise-4.21

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.

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

Labels

branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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.

5 participants