-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.14.z
-
None
-
No
-
False
-
Description of problem:
Another node is not coming up after deleting running node for the hosted cluster although the node replica count for the hosted cluster is more than 1.
Version-Release number of selected component (if applicable):
How reproducible:
Have referred, https://docs.openshift.com/container-platform/4.14/hosted_control_planes/hcp-managing.html#scale-down-data-plane_hcp-managing to scale down, scale up and delete nodes of the hosted cluster.
Note:
But ignored the 1st step then,
- Set the kubeconfig file to access the hosted cluster by running the following command:
$ ** export KUBECONFIG=<install_directory>/auth/kubeconfig
As the nodepools are not available in hosted clusters its available in the 'clusters' namespace available for the hosting cluster.
Steps to Reproduce:
1. Create one provider-client hci cluster with hosted cluster
2. export KUBECONFIG=<kubeconfig of the hosting cluster>
3. list the nodepools available for the hosting cluster
oc get nodepool -A
4. scale down nodepool resource for the hosted cluster to zero.
oc scale nodepool/<NODEPOOL_NAME> --namespace <HOSTED_CLUSTER_NAMESPACE> --replicas=0
5. Check the nodes are deleted.
export KUBECONFIG=<kubeconfig of the hosted cluster>
6. check no nodes are running
oc get nodes
7. scale up nodepool resource for the hosted cluster to zero.
oc scale nodepool/<NODEPOOL_NAME> --namespace <HOSTED_CLUSTER_NAMESPACE> --replicas=2
8. new nodes did not come up and the hosted cluster moved to 'Pending' status
Actual results:
New nodes did not come up for the hosted cluster and it moved to 'Pending' status
Expected results:
New nodes should have come up ad the hosted clusted should be in 'Ready' status.
Additional info:
