kiranchavala opened a new issue, #14504: URL: https://github.com/apache/cloudstack/issues/14504
### problem CKS - Control and worker node service offerings are not populated when ### versions ACS 4.22.x and 4.23.0 ### The steps to reproduce the bug 1. Deploy a cks cluster with default settings > do not select anything in advance settings in the form <img width="587" height="929" alt="Image" src="https://github.com/user-attachments/assets/a9f95c6a-5269-4a69-aafd-5fe5c51336c4"; /> Check the database ``` mysql> select control_node_service_offering_id,worker_node_service_offering_id from kubernetes_cluster where id=16 \G; *************************** 1. row *************************** control_node_service_offering_id: NULL worker_node_service_offering_id: NULL 1 row in set (0.00 sec) ``` 2. Deploy a cks cluster with default settings > select separate offering for control and worker node in advance settings <img width="533" height="769" alt="Image" src="https://github.com/user-attachments/assets/9aa90baf-3a67-42a5-ba8e-361a80113c6d"; /> Check the database ``` mysql> select control_node_service_offering_id,worker_node_service_offering_id from kubernetes_cluster where id=15 \G; *************************** 1. row *************************** control_node_service_offering_id: 13 worker_node_service_offering_id: 16 1 row in set (0.00 sec) ``` ### What to do about it? There should be a record of the service offering in the database when a cks cluster has the default setting compute offering As this can lead to issues when scaling is performed on a cks cluster -- 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]
