feat: add omni faq and troubleshooting pages #234
Conversation
| - "self-hosted/omni-deployment-options" | ||
| - "self-hosted/deploy-omni-on-prem" | ||
| - "self-hosted/install-image-factory-on-prem" | ||
| - "self-hosted/deploy-image-factory-on-prem" |
There was a problem hiding this comment.
this would probably affect the redirects
There was a problem hiding this comment.
Because this is a new page I don't think there are any external links that link to it and I fixed the links internal in the docs
s/run/deploy/ for image factory page for consistency Signed-off-by: Justin Garrison <justin.garrison@siderolabs.com>
|
|
||
| Machines connected to Omni can get in states where Omni can no longer cleanly remove them. This may be because the machine is no longer available, the machine has errors, or other reasons. | ||
|
|
||
| This may block the ability to delete a cluster as Omni tries to cleanly remove machines before deleting the clutser resoures. Sometimes trying to force delete the machine from the Omni UI also does not remove the machine. |
There was a problem hiding this comment.
Force delete from the UI goes exactly what omnictl delete link does, fyi.
I would document two paths, but there is no point in doing both.
There was a problem hiding this comment.
I was pretty sure we added a "force delete" in the UI but I didn't see anything that specified "force" when a machine is disconnected or stuck.
There was a problem hiding this comment.
nvm, I found the pop-up after a machine was in a stuck state
There was a problem hiding this comment.
The UI flow didn't work for me so I opened a bug siderolabs/omni#2035
The CLI steps worked immediately so I'll leave those in the doc until the UI works as expected.
4 participants
s/run/deploy/ for image factory page for consistency