Skip to content

Conversation

@wgabor0427
Copy link
Contributor

@wgabor0427 wgabor0427 commented Apr 3, 2025

Version(s):
4.12+

Issue:
https://issues.redhat.com/browse/OCPBUGS-52653

Link to docs preview:
https://91615--ocpdocs-pr.netlify.app/openshift-dedicated/latest/support/gathering-cluster-data.html
https://91615--ocpdocs-pr.netlify.app/openshift-enterprise/latest/support/gathering-cluster-data.html
https://91615--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/support/gathering-cluster-data.html
https://91615--ocpdocs-pr.netlify.app/openshift-rosa/latest/support/gathering-cluster-data.html

QE review:

  • QE has approved this change.

The following topic steps should have the same information:

  • Gathering data about your cluster for Red Hat Support (step 3)
  • Gathering data about specific features (step 4)
  • Gathering network logs (step 2)

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 3, 2025
@wgabor0427 wgabor0427 force-pushed the OCPBUGS-52653 branch 2 times, most recently from a19398f to 76268f8 Compare April 4, 2025 19:03
. Create a compressed file from the `must-gather` directory that was just created in your working directory. For example, on a computer that uses a Linux
operating system, run the following command:
. Create a compressed file from the `must-gather` directory that was just created in your working directory. Make sure you provide the date and cluster ID for a unique must-gather. For moe information on how to fiind the cluster ID, see the Red Hat Knowledge base solution link:https://access.redhat.com/solutions/5280291[How to find the cluster-id or name on Opeshift cluster]. For example, on a computer that uses a Linux operating system, run the following command:
+

Choose a reason for hiding this comment

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

There is a typo fiind the cluster ID , please update , thanks

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@zhouying7780 Can you please review the docs again under "Links to doc preview" above. Thanks.

$ tar cvaf must-gather.tar.gz must-gather.local.5421342344627712289/ <1>
$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-$CLUSTERID.tar.gz must-gather.local.426787175854303238 <1>
----
<1> Make sure to replace `must-gather-local.5421342344627712289/` with the actual directory name.

Choose a reason for hiding this comment

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

here should be the same as the example : must-gather.local.426787175854303238

@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 Apr 8, 2025
@wgabor0427 wgabor0427 force-pushed the OCPBUGS-52653 branch 4 times, most recently from 33376bd to 421df5a Compare April 14, 2025 17:45
@zhouying7780
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2025
@wgabor0427
Copy link
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 Apr 16, 2025
@xenolinux xenolinux 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 Apr 16, 2025
Copy link
Contributor

@xenolinux xenolinux left a comment

Choose a reason for hiding this comment

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

Left a few comments; otherwise LGTM

By default, the `must-gather` tool collects the OVN `nbdb` and `sbdb` databases from all of the nodes in the cluster. Adding the `-- gather_network_logs` option to include additional logs that contain OVN-Kubernetes transactions for OVN `nbdb` database.
====
. Create a compressed file from the `must-gather` directory that was just created in your working directory. For example, on a computer that uses a Linux operating system, run the following command:
. Create a compressed file from the `must-gather` directory that was just created in your working directory. Make sure you provide the date and cluster ID for a unique must-gather. For more information on how to find the cluster ID, see the Red Hat Knowledge base solution link:https://access.redhat.com/solutions/5280291[How to find the cluster-id or name on OpenShift cluster]. For example, on a computer that uses a Linux operating system, run the following command:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
. Create a compressed file from the `must-gather` directory that was just created in your working directory. Make sure you provide the date and cluster ID for a unique must-gather. For more information on how to find the cluster ID, see the Red Hat Knowledge base solution link:https://access.redhat.com/solutions/5280291[How to find the cluster-id or name on OpenShift cluster]. For example, on a computer that uses a Linux operating system, run the following command:
. Create a compressed file from the `must-gather` directory that was just created in your working directory. Make sure you provide the date and cluster ID for a unique must-gather data. For more information about how to find the cluster ID, see link:https://access.redhat.com/solutions/5280291[How to find the cluster-id or name on OpenShift cluster]. For example, on a computer that uses a Linux operating system, run the following command:
  • "....a unique must-gather": Assuming this is poiniting to a unique must-gather data. If not, please replace with the suitable name/term.
  • "...Knowledge base solution" can be omitted

Copy link
Contributor Author

Choose a reason for hiding this comment

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

  • Replaced "for a unique must-gather" with "for the unique must-gather data."
  • Deleted "Knowledge base solution"

[source,terminal]
----
$ tar cvaf must-gather.tar.gz must-gather.local.472290403699006248 <1>
$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-$CLUSTERID.tar.gz must-gather.local.426787175854303238 <1>
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-$CLUSTERID.tar.gz must-gather.local.426787175854303238 <1>
$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-<cluster_id>.tar.gz <must_gather_local_dir> <1>
  • I'd suggest to use a user-replaced variable for cluster id. I believe $ is not needed for <cluster_id>. You might want to confirm with SME/QE.
  • because must-gather.local.426787175854303238 is replaceable, suggestion to use a placeholder -- <must_gather_local_dir>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

  • Added the user-replaced variable <cluster_id>
  • Added the placeholder <must_gather_local_dir>

$ tar cvaf must-gather.tar.gz must-gather.local.472290403699006248 <1>
$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-$CLUSTERID.tar.gz must-gather.local.426787175854303238 <1>
----
<1> Replace `must-gather-local.472290403699006248` with the actual directory name.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
<1> Replace `must-gather-local.472290403699006248` with the actual directory name.
<1> Replace `<must_gather_local_dir>` with the actual directory name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

ifndef::openshift-origin[]
. Create a compressed file from the `must-gather` directory that was just created in your working directory. For example, on a computer that uses a Linux
. Create a compressed file from the `must-gather` directory that was just created in your working directory. Make sure you provide the date and cluster ID for a unique must-gather. For more information on how to find the cluster ID, see the Red Hat Knowledge base solution link:https://access.redhat.com/solutions/5280291[How to find the cluster-id or name on OpenShift cluster]. For example, on a computer that uses a Linux
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comments as earlier

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made same edits in this file

[source,terminal]
----
$ tar cvaf must-gather.tar.gz must-gather.local.5421342344627712289/ <1>
$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-$CLUSTERID.tar.gz must-gather.local.426787175854303238 <1>
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comments as earlier

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made same edits in this file

$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-$CLUSTERID.tar.gz must-gather.local.426787175854303238 <1>
----
<1> Make sure to replace `must-gather-local.5421342344627712289/` with the
<1> Make sure to replace `must-gather.local.426787175854303238` with the
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
<1> Make sure to replace `must-gather.local.426787175854303238` with the
<1> Make sure to replace `<must_gather_local_dir>` with the actual directory name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made changes

----
<1> Make sure to replace `must-gather-local.5421342344627712289/` with the
<1> Make sure to replace `must-gather.local.426787175854303238` with the
actual directory name.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
actual directory name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made the same changes to this file as above


. Create a compressed file from the `must-gather` directory that was just created in your working directory. For example, on a computer that uses a Linux
operating system, run the following command:
. Create a compressed file from the `must-gather` directory that was just created in your working directory. Make sure you provide the date and cluster ID for a unique must-gather. For more information on how to find the cluster ID, see the Red Hat Knowledge base solution link:https://access.redhat.com/solutions/5280291[How to find the cluster-id or name on Opeshift cluster]. For example, on a computer that uses a Linux operating system, run the following command:
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comments

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Comment on lines 82 to 84
$ tar cvaf must-gather-`date +"%m-%d-%Y-%H-%M-%S"`-$CLUSTERID.tar.gz must-gather.local.426787175854303238 <1>
----
<1> Make sure to replace `must-gather-local.5421342344627712289/` with the actual directory name.
<1> Make sure to replace `must-gather-local.426787175854303238/` with the actual directory name.
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comments

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@xenolinux xenolinux 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 Apr 16, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2025
@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.16

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.17

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.18

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.19

@xenolinux xenolinux added this to the Continuous Release milestone Apr 21, 2025
@openshift-cherrypick-robot

@xenolinux: #91615 failed to apply on top of branch "enterprise-4.12":

Applying: OCPBUGS-52653 made edits to the files
Using index info to reconstruct a base tree...
M	modules/gathering-data-network-logs.adoc
M	modules/gathering-data-specific-features.adoc
M	modules/support-gather-data.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/support-gather-data.adoc
Auto-merging modules/gathering-data-specific-features.adoc
Auto-merging modules/gathering-data-network-logs.adoc
CONFLICT (content): Merge conflict in modules/gathering-data-network-logs.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-52653 made edits to the files

Details

In response to this:

/cherrypick enterprise-4.12

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

@xenolinux: #91615 failed to apply on top of branch "enterprise-4.13":

Applying: OCPBUGS-52653 made edits to the files
Using index info to reconstruct a base tree...
M	modules/gathering-data-network-logs.adoc
M	modules/gathering-data-specific-features.adoc
M	modules/support-gather-data.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/support-gather-data.adoc
Auto-merging modules/gathering-data-specific-features.adoc
Auto-merging modules/gathering-data-network-logs.adoc
CONFLICT (content): Merge conflict in modules/gathering-data-network-logs.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-52653 made edits to the files

Details

In response to this:

/cherrypick enterprise-4.13

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

@xenolinux: new pull request created: #92393

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-sigs/prow repository.

@openshift-cherrypick-robot

@xenolinux: new pull request created: #92394

Details

In response to this:

/cherrypick enterprise-4.15

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

@xenolinux: new pull request created: #92395

Details

In response to this:

/cherrypick enterprise-4.16

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

@xenolinux: new pull request created: #92396

Details

In response to this:

/cherrypick enterprise-4.17

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

@xenolinux: #91615 failed to apply on top of branch "enterprise-4.18":

Patch is empty.
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To record the empty patch as an empty commit, run "git am --allow-empty".
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"

Details

In response to this:

/cherrypick enterprise-4.18

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

@xenolinux: new pull request created: #92397

Details

In response to this:

/cherrypick enterprise-4.19

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.

@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.18

@openshift-cherrypick-robot

@xenolinux: new pull request created: #92398

Details

In response to this:

/cherrypick enterprise-4.18

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.

@xenolinux
Copy link
Contributor

@wgabor0427 Automated cherry-picks for 4.12 and 4.13 failed. You need to create manual CP PRs.

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

Labels

branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 lgtm Indicates that a PR is ready to be merged. peer-review-done Signifies that the peer review team has reviewed this PR 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.

5 participants