RFE-821 - Adding to the support section.#23316
Conversation
|
@openshift/team-documentation for peer review please. Please can someone also add 'Peer Review Needed', 'branch/enterprise-4.5', 'labels and 'Next Release' milestone? Thanks!'. This content is for enterprise-4.5 onward. |
c752422 to
b339ca5
Compare
|
The preview will be available shortly at: |
b339ca5 to
563d96e
Compare
sferich888
left a comment
There was a problem hiding this comment.
This looks great, I have a few nits, here and there but overall this is a strong foundation for us to build on.
563d96e to
bfd24c8
Compare
There was a problem hiding this comment.
Hey Paul - This is an unparalleled effort and will be an enormous asset to our customers. Thanks for letting me review it.
My comments are mostly of the nitpick variety, calling out a few of our OCP and ISG style conventions, such as serial commas and using attributes like {product-title} wherever possible.
You'll also see at times where I suggested adding some more articles to the verbiage, such as "Gather the journald unit logs" rather than "Gather journald unit logs". I think this would help make it sound more human-to-human, but you may have chosen to exclude some of this language to cut down on length or to conform to troubleshooting/support norms, which would be understandable.
Let me know if you need clarification or want to discuss anything further. Great work, Paul!
b5902d9 to
e2a8cba
Compare
bergerhoffer
left a comment
There was a problem hiding this comment.
A few comments from a run through of a few of the sections
ae16a11 to
c4f665d
Compare
bergerhoffer
left a comment
There was a problem hiding this comment.
Last batch of comments. Ton of great info here!
@jianzhangbjz thank you for highlighting this. I have now made this clearer in the description in the assembly. I have also added a note at the base of both of those modules highlighting this point. |
Thank you @juzhao for filing the Bugzilla. I have subsequently assigned the BZ to myself and applied the requested changes through this current PR. Please review the BZ from a QE perspective. Thanks! |
LGTM and bug is moved to VERIFIED |
|
New changes are detected. LGTM label has been removed. |
|
@xltian I believe I have now responded to each of the QE comments from the team in this document. Can you please let me know whether there are any more QE reviews to go? Can you please confirm whether the QE team are now happy for this PR to be merged? Thanks! |
|
Look good to me for modules/specifying-oc-log-levels.adoc |
|
looks good to me for "troubleshooting-installations" section |
|
@pneedle-rh , most of sections look good to QE, once @gpei 's comment is resolved, QE is fine for this PR. |
Thank you @wsun1, that is great. I have now resolved @gpei's comment. @bobfuru @bergerhoffer can you please let me know if you have any further suggestions before this PR is merged? A number of changes were made following QE review. Thanks! |
bobfuru
left a comment
There was a problem hiding this comment.
Looks great! A couple of places where the formatting was off but the rest of my comments are tiny nits. Thanks for letting me review this again.
|
@bobfuru my understanding is that this PR has now passed through peer, SME and QE approval. If you are happy with my responses to your final review comments, can you please merge and CP for branch/enterprise-4.5 and branch/enterprise-4.6? Thanks! |
|
LGTM |
|
/cherrypick enterprise-4.5 |
|
@bobfuru: #23316 failed to apply on top of branch "enterprise-4.5": DetailsIn response to this:
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. |
|
/cherrypick enterprise-4.6 |
|
@bobfuru: #23316 failed to apply on top of branch "enterprise-4.6": DetailsIn response to this:
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. |
Applies to enterprise-4.5 onward. This is the first phase of a new Troubleshooting Guide for OCP 4. Initially content is being added to the Support book.
This relates to https://issues.redhat.com/browse/RFE-821.
Previews available at:
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/getting-support.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/gathering-cluster-data.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/summarizing-cluster-specifications.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/troubleshooting/troubleshooting-installations.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/troubleshooting/verifying-node-health.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/troubleshooting/troubleshooting-crio-issues.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/troubleshooting/troubleshooting-operator-issues.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/troubleshooting/investigating-pod-issues.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/troubleshooting/troubleshooting-s2i.html
https://troubleshooting_guide--ocpdocs.netlify.app/openshift-enterprise/latest/support/troubleshooting/diagnosing-oc-issues.html