rajujith opened a new issue, #8517:
URL: https://github.com/apache/cloudstack/issues/8517
<!--
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
* Improvement Request
* Other
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
KVM, Management Server
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18.1, Any
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
KVM
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Rocky 8 KVM, Management server
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Removed KVM host with agent management server IP configured pointing to a
new management server leads to high CPU load on the management server.

We can see the below logs in the management server:
```
2024-01-16 10:14:00,089 WARN [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-381:null) (logid:) SSL Handshake has taken
more than 30s to connect to: /10.1.35.66:46493. Please investigate this
connection.
2024-01-16 10:14:00,099 WARN [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-29:null) (logid:) SSL Handshake has taken
more than 30s to connect to: /10.1.35.66:46475. Please investigate this
connection.
```
##### 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 -->
~~~
1. Remove a KVM host. Restart the agent.
2. Reinstall the management server or run cloudstack-setup-database
3. Watch the Management server CPU load.
OR
1. Update the agent.properties of a KVM host to point it to an existing
management server where the host is not added.
2. Restart the cloudstack agent.
3. Wait for a few minutes until the management server CPU load goes very
high.
~~~
<!-- You can also paste gist.github.com links for larger files -->
--
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]