EduFrazao opened a new issue, #13519: URL: https://github.com/apache/cloudstack/issues/13519
### problem Hi. In a advanced netowrk zone, VXLAN based, my KVM agents are using the storage network address as private ip address. The network storage network is not routable between components, and it is causing severe problems like mal function on CPVM that try to connect on the wrong address to establish a connection with the hypervisor VNC Port. The storage address is correctly found. This is an exemple of my interfaces config: ` root@hypr2-rck3:~# ip -br a lo UNKNOWN 127.0.0.1/8 10.1.4.2/32 fd00:1337:1:4::2/128 ::1/128 ens8f0np0 DOWN ens8f1np1 DOWN ens5f0np0 UP 10.1.32.3/31 fd00:1337:1:20::3/127 fe80::e4f8:1110:2c37:62ca/64 ens5f1np1 DOWN vxlan200 UNKNOWN vxlan202 UNKNOWN v-secstorbr@v-secstor UP v-secstor@v-secstorbr UP 10.1.48.2/22 fd00:1337:1:2d::2/64 fe80::a6c6:ac43:1c4:ab35/64 v-clmgmtbr@v-clmgmt UP v-clmgmt@v-clmgmtbr UP 10.1.0.2/22 fd00:1337:1::2/64 fe80::a535:f84c:40f1:b424/64 eth-clguest UNKNOWN v-clstoragebr@v-clstorage UP v-clstorage@v-clstoragebr UP 10.1.16.2/20 fd00:1337:1:10::2/64 fe80::e263:1ef4:9243:237e/64 br-secstor UP eth-clpublic UNKNOWN vxlan100 UNKNOWN br-clmgmt UP br-clguest UP br-clstorage UP br-clpublic UP cloud0 UNKNOWN 169.254.0.1/16 fe80::d028:d0ff:fe30:3c0d/64 ` The agent is selecting 10.1.16.2 address as storage (correct) and private (incorrect, the correct IP should be 10.1.0.2). This range is directly routable. The agent can reach the management servers from this address, and the management servers can do stablish new connections with hosts too. There is some property that I can change to enforce the private address? ### versions Cloudstack 4.22.1.0 OS: Rocky Linux 10.2 Agent: 4.22.1.0 Java: OpenJDK 64-Bit Server VM (Red_Hat-21.0.11.0.10-1) (build 21.0.11+10-LTS, mixed mode, sharing) ### The steps to reproduce the bug 1. Setup a FRR / VXLAN / EVPN enviroment 2. Setup an advanced network zone in Cloudstack. 3. Adopt an hypervisor (using the correct ip address on the UI). 4. Adotion will work and hypervisor will be connected, able to run VMs, but with management IP incorrectly stored. ### What to do about it? _No response_ -- 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]
