tampler commented on issue #8218:
URL: https://github.com/apache/cloudstack/issues/8218#issuecomment-1821180157

   Well, after fiddling out with my test setup, I discovered that it is a 
documentation/configuration issue. The problem is how to correctly resolve the 
`mgmt` server.
   ```
   > cat /etc/cloudstack/management/db.properties
   ...
   # CloudStack database settings
   db.cloud.username=cloud
   db.cloud.password=cloud
   # db.cloud.host=hyp0 < --- won't work - wouldn't resolve my cloudbr1PRIVATE 
IP, returns  503
   # db.cloud.host=192.168.0.4 < --- won't work - db host is inaccessible and 
returns  503
   db.cloud.host=localhost  < --- resolves to cloudbr0 PUBLIC IP, e.g 
10.105.xxx.yyy returns 200 
   db.cloud.driver=jdbc:mysql
   ```
   As a result, `agent` uses a PUBLIC IP from a PRIVATE network and won't 
resolve `cloubr1 IP=192.168.0.4` and won't enter a valid state - SSVM can't 
find a `mgmt` host
   
   > cat /var/log/cloudstack/agent/agent.log
   ...
   Nov 21 15:29:19 hyp0 java[83458]: INFO  [cloud.agent.Agent] 
(agentRequest-Handler-5:) (logid:9e0f385c) Processed new management server 
list: 10.105.xxx.yyy@static
   ```
   
   ![agent 
status](https://github.com/apache/cloudstack/assets/2816743/0e1faa77-264f-4199-87e0-499c23f0f352)
   When I check the SSVM logs, I see it is trying to connect to `cloubr0 - 
public IP` instead of `cloudbr1 - private IP`
   


-- 
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]

Reply via email to