saffronjam commented on issue #7829:
URL: https://github.com/apache/cloudstack/issues/7829#issuecomment-1674452351

   The issue appears to remain. 
   
   
![image](https://github.com/apache/cloudstack/assets/26722370/667675a5-2bdc-417c-b6ce-6fa9fe523657)
   
   We tried CKS 1.24 and 1.27.3 (the one without version in the name) with 7 
and 10 nodes respectively. I tried with and without HA (2 control nodes, made 
no difference). The last test was with HA, so that's what I'm reporting on.
   
   1.24:
   ```
   ➜  ~ kubectl get nodes
   NAME                                   STATUS   ROLES           AGE   VERSION
   test-weizhou-124-control-189e015f8ad   Ready    control-plane   17h   v1.24.0
   ```
   
[test-weizhou-124-control2.txt](https://github.com/apache/cloudstack/files/12320159/test-weizhou-124-control2.txt)
   
   1.27.3:
   ```
   ➜  ~ kubectl get nodes
   NAME                               STATUS   ROLES           AGE   VERSION
   test-weizhou-control-189e0152f9d   Ready    control-plane   17h   v1.27.3
   test-weizhou-control-189e0156d4a   Ready    control-plane   17h   v1.27.3
   test-weizhou-node-189e015b3a9      Ready    <none>          17h   v1.27.3
   test-weizhou-node-189e015ead7      Ready    <none>          17h   v1.27.3
   test-weizhou-node-189e0162b2e      Ready    <none>          17h   v1.27.3
   ```
   
[test-weizhou-node4.txt](https://github.com/apache/cloudstack/files/12319995/test-weizhou-node4.txt)
   
   The result is pretty much same as earlier where it get stuck on some node, 
as you can read in the logs.
   ```
   /var/log/daemon.log
   
   Aug 10 16:00:30 systemvm cloud-init[1109]: Waiting for Binaries directory 
/mnt/k8sdisk/ to be available, sleeping for 15 seconds, attempt: 100
   Aug 10 16:00:45 systemvm cloud-init[1109]: Warning: Offline install timed 
out!
   ```
   
   Lmk if you need more information about our setup


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to