GitHub user Qinshan886 closed a discussion: In version 4.18.1, under the VPC network resource domain, DHCP dynamic IP addresses cannot be allocated across hosts
<!-- 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 ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ Virtual Router ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on main branch. --> ~~~ 4.18.1 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> Centos 7 ##### SUMMARY <!-- Explain the problem/feature briefly --> I am using CloudStack 4.18.1. After creating a resource domain of the VPC network type, I added two host nodes.  And created a VPC network (it automatically creates a virtual router on host node 1) and added the network layer   ##### 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 --> When I started to create the first instance machine, I chose the hk-node1 node. It is on the same host node as the vpc virtual router  The instance machine and the virtual router can be connected normally, and the instance machine can request the DHCP of the virtual router of the vpc to obtain the IP address  The above picture shows the log information of DHCP in the vpc virtual router   The above picture shows the log and IP information of the instance machine requesting the vpc virtual router during the dhcp process.this is normal ==================================hk-node2 host node dividing line============================ I now create an instance machine on the hk-node2 host node   The above picture shows the vpc virtual router log (it is on the hk-node1 host node), and there is no log showing the IP address assigned to the instance machine on the hk-node2 host node.   The above figure shows that the instance machine on the hk-node2 host node cannot access the gateway address of the vpc virtual router 10.1.100.1 during the dhcp request process, resulting in a dhcp timeout. Failed to obtain the IP address； This is abnormal. Why can't the instance machine on the hk-node2 host node obtain an IP address when the two host nodes are in the same resource domain cluster? I tried to reproduce this operation in the latest version 4.19, and the problem of not being able to obtain an IP address across host nodes also exists. Please help!!! ##### EXPECTED RESULTS The instance machine I created on the hk-node2 host node should be able to obtain the IP address dynamically allocated by DHCP normally, just like the instance machine on the hk-node1 host node. ##### ACTUAL RESULTS The actual result is that the instance machine I created on another host node cannot connect to the host node where the vpc virtual router is located, resulting in the instance machine on other host nodes being unable to dynamically obtain an IP address through dhcp. In simple terms, the instance machine I created must be on the same host node as the vpc virtual router. If it is not on the same host node, the instance machine cannot obtain an IP GitHub link: https://github.com/apache/cloudstack/discussions/9320 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
