CloudStack Agent on host with DHCP

[damonb123]

ISSUE TYPE

• Improvement Request

COMPONENT NAME

CloudStack Agent

CLOUDSTACK VERSION

4.17, 4.18

SUMMARY

If physical KVM host IP address changes with DHCP, the agent is unable to reconnect to CloudStack management server.

STEPS TO REPRODUCE

Change the IP address of the KVM node the agent is running on and reboot the host.
The agent will not be able to connect back to the management server and throw errors.

EXPECTED RESULTS

The agent should connect back to management server, and the host physical IP address should be updated.

ACTUAL RESULTS

2023-06-29 17:40:15,368 INFO  [utils.nio.NioClient] (main:null) (logid:) NioClient connection closed
2023-06-29 17:40:15,368 INFO  [cloud.agent.Agent] (main:null) (logid:) Attempted to connect to the server, but received an unexpected exception, trying again...
com.cloud.utils.exception.NioConnectionException: SSL Handshake failed while connecting to host: 10.60.96.48 port: 8250

[weizhouapache]

@damonb123
is the IP changed ?

[rohityadavcloud]

Could you try having static DHCP assignments by your router?

[DaanHoogland]

@damonb123 It sounds to me your scenario would have to be;

• remove the host from cloudstack
• change the ip
• reboot
• re-add
  I don´t think we support this out-of-bounds changing of the IP of an host.

[zap51]

@damonb123 Static assignment should always be preferred for your hypervisors for various reasons. Try setting static DHCP assignment on your DHCP server of the host's management MAC address to always lease out a static IP.

[rohityadavcloud]

@damonb123 by design, DHCP enabled KVM hosts aren't support with the CA framework security enabled. You can disable the auth strictness on such hosts to make them work. Though it's not a good idea to have hosts whose rfc1918 IPs can change.