search

siderolabs / omni-feedback

Omni feature requests, bug reports
https://www.siderolabs.com/platform/saas-for-kubernetes/
MIT License
2 stars 0 forks source link

[bug] Omni shows "not ready" status on some clusters that appear to be fully functional #57

Open ArcherSeven opened 1 year ago

ArcherSeven commented 1 year ago

Is there an existing issue for this?

Current Behavior

Omni shows "Not Ready" on a cluster that appears ready, and all components of the single node are ready.

Expected Behavior

Omni shows "Ready" on a ready cluster, or explains why it believes a cluster is "Not Ready" when it states as such.

Steps To Reproduce

Prod. Extant Slack thread in our Slack channel with specific example.

What browsers are you seeing the problem on?

No response

Anything else?

No response

smira commented 1 year ago

It was traced down to be unready (probably a bug) static pods on that node, so we'd need some logs from the node to understand what is wrong.

talosctl support bundle will be enough

ArcherSeven commented 1 year ago

Sent privately

steverfrancis commented 1 year ago

The UI should highlight the component that is causing the "NotReady"