div8cn opened a new issue #3505: Agent LB for CloudStack failed URL: https://github.com/apache/cloudstack/issues/3505 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master 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 ##### COMPONENT NAME <!-- --> ~~~ Agent ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11 4.11.1 4.11.2 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> indirect.agent.lb.algorithm=roundrobin indirect.agent.lb.check.interval=60 ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> ##### SUMMARY <!-- Explain the problem/feature briefly --> When deploying multiple management nodes, the preferred managment node is forced to power off, the agent will not immediately connect to the second management node. Wait 15 minutes, the agent issues a "No route to host" error and connects to the second management node. ##### 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.Deploying multiple management nodes 2.Modify global settings: indirect.agent.lb.algorithm=roundrobin indirect.agent.lb.check.interval=60 host={all management node ips} 3.Restart all KVM agents 4.View the connection status of each agent through Mysql select host.id ,host.name,host.mgmt_server_id,host.status,mshost.name from host,mshost where host.mgmt_server_id=mshost.msid; 5.close a management node randomly (Forced power off) 6.Observe whether the agent connected to the failure management node will reconnect the new managment node in a very short time ~~~ <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ Agent quickly reconnects to the new management node ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ wait15 minutes, the agent issues a "No route to host" error and connects to the second management node. ~~~
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
