adestis-mf commented on issue #14673:
URL: https://github.com/apache/cloudstack/issues/14673#issuecomment-6810594959
This is the same problem as #12633, which I missed before opening this
issue. I have since reproduced it on 4.23.0.0 as well. I'm closing this one as
a duplicate of #12633; a fix is proposed in #14683.
Three corrections to the description above:
- `size` in `scaleKubernetesCluster` counts the external nodes as well, so
the example in the steps ("scale to 2 workers") is `size=3`: the external node
plus two managed workers, the same numbers as in #12633.
- On `4.22` a failed scale-up leaves the cluster in `Alert`, as reported in
#12633, and keeps the new VMs. Removing the new VMs and returning to `Running`,
as described above, applies from 4.23.0.0 on, where the failure handling
changed with #12386. So the cluster looks healthy after the failed scale-up
only from 4.23.0.0 on; on `4.22` it is in `Alert`.
- `removeSshFirewallRule` does not always revoke the rule starting at 2222.
It revokes the first rule that either starts at 2222 or has a port forwarding
rule to port 22 on the same ports. After earlier scaling that can be an old
rule of an external node, and then the range rule stays and the new range
conflicts with it. I saw this on 4.23.0.0 after a scale-down.
--
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]
