OS was in a hung state and does not see any logs being generated when it was Not Ready in the system    

Customer is using OCP V.4.16    

    Nodes are hosted over zVM hypervisor.

We have seen the multiple occurences of the issue where node went into NotReady state. We not able to ssh or ping the nodes. However, ZVM team able to see login prompt of the node through console.

- We are not able to find exact replication steps when and how this happens.
- We faced this issue on Feb 17 2025 so as per the recomendations from the support team configured kdump on the cluster nodes. 
- Two Nodes died again on April 25 & 26. Reference case is linked. (Kdump configured on cluster but not able to find any logs why node does not have any logs) 
- Now, the same incident happened again on June 24. (Different cluster as KDUMP is not configured)
- We checked memory and CPU utilization of the node during the time of issue and able to see it is stable.

Requesting engineering help and guidance to check further on this issue and how we can find the root cause of the issue if something similar happens again. As this issue is happening consitently customer is looking for a solution so that we can mitigate this issue further.

Does not have exact steps to replicate the issue but it is happening randmoly
    

    Node OS is not generating logs.

    Node OS should generate logs, so that we can find cause of the issue

    SOS report for April 25 & 26 is already available over the case 04126850.