You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "weizhouapache (via GitHub)" <gi...@apache.org> on 2025/11/24 13:03:56 UTC

[I] CKS: new created nodes are not added to CKS cluster if scaling fails [cloudstack]

weizhouapache opened a new issue, #12123:
URL: https://github.com/apache/cloudstack/issues/12123

   ### problem
   
   this happens with ACS 4.22 and 4.21, but might also with older versions
   
   - create CKS cluster (1 control node + 1 worker node) as regular user
   - set resource limit (e.g. memory) of regular user, so that the user can deploy a new worker node, but not two worker nodes
   - scale the CKS cluster with two more worker nodes (1 -> 3)
   - a worker node is created, but not 2 due to resource limitation
   
   expected:
   - CKS cluster node size is increased to 2 (2 worker nodes)
   - network rules are configured for the new worker node
   - CKS cluster is Running state
   
   Actual:
   - CKS cluster node size is still 1 (1 worker node)
   - network rules are not configured for the new worker node
   - CKS cluster is Alert state
   
   
   ### versions
   
   The versions of ACS, hypervisors, storage, network etc..
   
   ### The steps to reproduce the bug
   
   1.
   2.
   3.
   ...
   
   
   ### What to do about it?
   
   _No response_


-- 
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: commits-unsubscribe@cloudstack.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] CKS: new created nodes are not added to CKS cluster if scaling fails [cloudstack]

Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache commented on issue #12123:
URL: https://github.com/apache/cloudstack/issues/12123#issuecomment-3654372527

   fixed by #12167


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] CKS: new created nodes are not added to CKS cluster if scaling fails [cloudstack]

Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache closed issue #12123: CKS: new created nodes are not added to CKS cluster if scaling fails
URL: https://github.com/apache/cloudstack/issues/12123


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] CKS: new created nodes are not added to CKS cluster if scaling fails [cloudstack]

Posted by "Pearl1594 (via GitHub)" <gi...@apache.org>.
Pearl1594 commented on issue #12123:
URL: https://github.com/apache/cloudstack/issues/12123#issuecomment-3596437620

   Yes @DaanHoogland selected option 2, because having the cluster partially scale may lead to end users believing it scaled and then later realizing that it didn't scale up to the nodes they expected it to. That was my thought when I chose option 2 to address the issue.


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] CKS: new created nodes are not added to CKS cluster if scaling fails [cloudstack]

Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache commented on issue #12123:
URL: https://github.com/apache/cloudstack/issues/12123#issuecomment-3575693601

   I updated the description with two options of expectation
   both are fine for me. cc @DaanHoogland @Pearl1594 
   
   ```
   expected (option 1):
   
   CKS cluster node size is increased to 2 (2 worker nodes)
   network rules are configured for the new worker node
   CKS cluster is Running state
   
   expected (option 2):
   scaling fails
   No new worker node is deployed
   CKS cluster node size is unchanged (still 1)
   CKS cluster is Running state
   ```


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] CKS: new created nodes are not added to CKS cluster if scaling fails [cloudstack]

Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12123:
URL: https://github.com/apache/cloudstack/issues/12123#issuecomment-3646490368

   fixed in #12167 


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] CKS: new created nodes are not added to CKS cluster if scaling fails [cloudstack]

Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #12123:
URL: https://github.com/apache/cloudstack/issues/12123#issuecomment-3596201866

   looking at #12167 , we are choosing option 2, right @Pearl1594 ? (fine by me)


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org