Add troubleshooting for server pod failure

[hessio]

Please see detailed reason for creating this PR in #355

Signed-off-by: Patrick Hession patrick.hession@seagate.com

Description

• Added a new troubleshooting section for when a server pod fails during deployment
• You can see this issue being addressed by a community member here: #355

Breaking change

Type of change

• [ ] Bug fix (non-breaking change that fixes an issue)
• [ ] New feature (non-breaking change that adds new functionality)
• [ ] Breaking change (bug fix or new feature that breaks existing functionality)
• [ ] Third-party dependency update
• [X] Documentation additions or improvements
• [ ] Code quality improvements to existing code or test additions/updates

Applicable issues

• This change fixes an issue: #355
• This change is related to an issue: #355

CORTX image version requirements

This change requires the following images:

• cortx-data:<version>
• cortx-rgw:<version>
• cortx-control:<version>

How was this tested?

Additional information

Checklist

• [ ] The change is tested and works locally.
• [ ] New or changed settings in the solution YAML are documented clearly in the README.md file.
• [ ] All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change requires newer CORTX or third party image versions:

• [ ] The image fields in solution.example.yaml have been updated to use the required versions.
• [ ] The appVersion field of the Helm chart has been updated to use the new CORTX version.

If this change addresses a CORTX Jira issue:

• [ ] The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

---

View rendered README.md

[hessio]

I think this needs a bit more work. A troubleshooting step should identify a specific problem and resolution. "Server pod fails during deployment" is too general of a problem, they could fail for a variety of reasons. Restarting the coredns pods won't address every situation like this, so this step should be clear about which specific failure case it applies to.

Ya good point, I have update the heading to: "CORTX Deployment failed due to "timeout waiting for cortx-server or cortx-data-g0 to initialize" " - do you think this is explanatory enough or no? cc: @keithpine

[shailesh-vaidya]

Closing as an obsolete