satishglondhe opened a new issue #5976:
URL: https://github.com/apache/cloudstack/issues/5976
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
* Other
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.16.0.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced Network
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
N/A
##### SUMMARY
<!-- Explain the problem/feature briefly -->
After successful creation of kubernetes cluster, and selecting autoscaling,
specifying min and max size of worker nodes, Autoscaling pod are generated in
kube-system, but it doesn't function.
While checking for logs of cluster-autoscaler pod in kube-system we get the
following logs.
I0131 17:01:11.537869 1 client.go:175] NewAPIRequest response status
code:200
I0131 17:01:11.538288 1 cloudstack_manager.go:88] Got cluster :
&{c6496415-daea-4051-993a-3b9f9c58242e voyager 1 3 2
1 [0xc000e889f0 0xc000e88a20 0xc000e88a50]}
E0131 17:01:11.538366 1 static_autoscaler.go:271] Failed to get node
infos for groups: Unable to find node voyager-c
ontrol-17ea9f68878 in cluster
I0131 17:01:21.538749 1 static_autoscaler.go:229] Starting main loop
It seems like, it failed to get node infos for groups.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
Create a kubernetes cluster with versions [1.22.2, 1.20.9, 1.21.3]
Enable auto scaling and specify min and max cluster size
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
After increased load in cluster, cluster autoscaler should increase the node
and assign the pending pods on this new node. Same, for scale down.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
After increased load in cluster, cluster autoscaler is not provisioning new
nodes
~~~
--
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]
