-
Bug
-
Resolution: Done
-
Normal
-
4.14.z
-
None
-
Moderate
-
No
-
False
-
Description of problem:
Node restart for the hosted cluster initiated from hosting cluster was unsuccessful.The deleted node is showing as 'Running' under local-cluster, virtualization → virtualmachines page after restart but it is showing as ‘Not Ready’ in CLI and actually the hosted cluster is in 'Pending' status Before restart: > oc get node NAME STATUS ROLES AGE VERSION hcp414-15-0aff72fd-vb2fz Ready worker 9d v1.27.6+b49f9d1 After the restart: > oc get node NAME STATUS ROLES AGE VERSION hcp414-15-0aff72fd-vb2fz NotReady worker 9d v1.27.6+b49f9d1 Version-Release number of selected component (if applicable): ODF: 4.14.1-6.hci
Version-Release number of selected component (if applicable):
How reproducible:
Reproducible
Steps to Reproduce:
1. Create one provider-client hci cluster. 2. Go to local-cluster→virtualization → virtualmachines 3. restart one of the virtual machine 4. the vm gets stopped and comes up running again in local- cluster→virtualization → virtualmachines page. 5. From 'All Clusters' select the hosted cluster for which the node was restarted and check the Status.
Actual results:
The vm shows restarted in the provider console local-cluster→virtualization → virtualmachines page. But the node is showing as ‘Not Ready’ in CLI and the hosted cluster is in 'Pending' status.
Expected results:
The node of the hosted cluster should come up running and the hosted cluster should be in 'Ready' under All Clusters --> <hosted cluster details> Status.
Additional info: