andrijapanicsb commented on issue #14552: URL: https://github.com/apache/cloudstack/issues/14552#issuecomment-6887071617
Status update. The fix for this is in #14459. With that PR, a request with no `serviceofferingid` and no `nodeofferings` plans no offering change, so `size=N`, autoscaling-only requests and cluster-autoscaler scale-ups leave existing nodes alone. The autoscaling setting is now also kept when a request changes autoscaling and the worker offering together. #14605 does not fix this issue. It only blocks changing the offering of a single CKS node from the Instances view (#14553). I have removed its link to this issue, so merging it won't close this one. Still open: - Live test of these scenarios on #14459 (only the `nodeids` removal was live-tested so far). - The cluster-wide `serviceofferingid` staying out of date after a per-group scale. It is not fixed by #14459. #14604 (4.22) does not cover this either, so 4.22 and 4.23 keep the bug. -- 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]
