Troubleshooting: Verify BMO and Ironic healthy #490
Conversation
Signed-off-by: Lennart Jern <lennart.jern@est.tech>
metal3-io-bot
added
the
size/L
lentzi90
force-pushed
the
lentzi90/troubleshooting
branch
from
6a0118a to
b0357a5
Compare
|
/cc @dtantsur |
lentzi90
force-pushed
the
lentzi90/troubleshooting
branch
from
b0357a5 to
f06cb29
Compare
| @@ -0,0 +1,72 @@ | |||
| # Troubleshooting | |||
|
|
|||
| ## Verify that Ironic and Baremetal Operator are healthy | |||
There was a problem hiding this comment.
Honestly, I liked the FAQ format where each title is how a user would google it. Like, what would prompt an operator to look at this section you're adding?
There was a problem hiding this comment.
Sure, I also like that format, but I know also that an unhealthy Ironic or BMO could show itself in probably dozens of ways. It is more of a sanity check and something I would expect to direct users to when they are having issues that are hard to pinpoint. So I think it is important to have this somewhere. If you want, we can split this into troubleshooting and FAQ maybe?
lentzi90
force-pushed
the
lentzi90/troubleshooting
branch
from
f06cb29 to
14edab6
Compare
Add section on how to verify that BMO and Ironic are healthy as well as example output for both healthy and unhealthy examples. Signed-off-by: Lennart Jern <lennart.jern@est.tech>
lentzi90
force-pushed
the
lentzi90/troubleshooting
branch
from
14edab6 to
7526890
Compare
|
/cc @elfosardo @dtantsur |
|
/approve I have some doubts about the format, but the new text is a clear improvement, so let's merge it. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtantsur The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
metal3-io-bot
added
the
approved
Add section on how to verify that BMO and Ironic are healthy as well as
example output for both healthy and unhealthy examples.
I also moved the troubleshooting doc to the top level. My reasoning for this is that users may not know at what level an error is. They need a single place to search instead of first having to figure out if the issue belongs under BMO or CAPM3 or something else.
Part of #435