kiranchavala opened a new issue, #7341:
URL: https://github.com/apache/cloudstack/issues/7341
##### ISSUE TYPE
* Improvement/Enhancement Request
##### COMPONENT NAME
~~~
Component:agent
Component:management-server
Component:kvm
~~~
##### CLOUDSTACK VERSION
~~~
4.17.2
~~~
##### SUMMARY
Cloudstack agent should proactively check for changes made for Global
setting parameter (host)
##### STEPS TO REPRODUCE
1. Create a environment with multiple (2)management servers
2. The global setting parameter "host" is set to Management server 1 ip
address.
3. All the hosts and systemvm point to the Management server 1 ip address
Verify it in on the host and the systemvm
cat /etc/cloudstack/agent/agent.properties
cat /usr/local/cloud/systemvm/conf/agent.properties
4. Admin user adds the second management server ip address to the global
setting host
host= management server 1, management server 2
5. Admin user stops management server 1,
6. The hosts and systemvms will get into a disconnected state
7. In an ideal scneario, cloudstack agent should automataically connect to
second management server ip address
Ideally cloudstack should update the agent properties file present on the
host and systemvm with the 2nd management server ip and restart the agent
service
to connect back to the running management server
5. Currently the hosts and systemvms remain in a disconnected state unless
we perform the following steps
1. Manually edit the agent.properties in the kvm and restart the agent
service
2. Destroy the systemvms so that they connect to the correct management
server
##### EXPECTED RESULTS
~~~
Host and systemvms should connect to the second management server in case
first management server is down
~~~
##### ACTUAL RESULTS
~~~
Host and systemvms remain in a disconnected state and they don't connect to
the second management server
~~~
--
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]
