Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: rhwa-25.9
Affects Version/s: rhwa-25.7
Component/s: Node Healthcheck Console
Labels:

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Release Note Text:

Hide
Cause: The UI attempted to query MachineHealthChecks to display a warning about potential conflicts with NodeHealthChecks. In Hypershift clusters, where the MachineHealthCheck CRD is not available, this query failed and prevented the entire UI from loading.
Fix: Removed the check from the UI, as it is already handled by the backend and does not need to be displayed proactively.
Result: The NodeHealthCheck console plugin now loads and functions correctly in Hypershift clusters.

Show
Cause: The UI attempted to query MachineHealthChecks to display a warning about potential conflicts with NodeHealthChecks. In Hypershift clusters, where the MachineHealthCheck CRD is not available, this query failed and prevented the entire UI from loading. Fix: Removed the check from the UI, as it is already handled by the backend and does not need to be displayed proactively. Result: The NodeHealthCheck console plugin now loads and functions correctly in Hypershift clusters.
Steps to Reproduce:
- Install the NodeHealthCheck Operator with the plugin enabled.
- Navigate to the NodeHealthChecks screen.
- Observe that an error message appears instead of the expected list view.
Intelligence Requested:
Market:

Severity:
Moderate

Target Version:

rhwa-25.9

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

The Node Health Check Console plugin was configured when console plugin was disabled.

When this is enabled:

We select Compute >> NodeHealthChecks in GUI, the following Error shows:

Error Loading: Model does not exist

--> We checked the subscription and the configurations of the operator.
--> There is one node health check created which is working fine when console plugin is in disabled state.
--> It goes into error state when console plugin is enabled.

Note: This issue reproduces only on hypershift clusters