I ran into a similar problem when I tried to allocate an additional IP on the agent machine (for other purposes), the hypervisor would then show up in the UI with this new IP and in "Alert" state.
I solved the problem by moving the IP out of br0 and on to the loopback interface. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "li jerry" <div...@hotmail.com> > To: "users" <us...@cloudstack.apache.org>, "dev" <dev@cloudstack.apache.org> > Sent: Monday, 22 April, 2019 14:36:51 > Subject: Cloudstack-agent gets the local IP address exception > HI All > > > my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via keepalived. > > After I started the cloudstack-agent, I got vip[10.226.16.10] and I couldn't > get > the correct IP [10.226.16.11]; > > Can I have any way to get the cloudstack agent to get the correct IP address? > > > > Cloudstack 4.11.2 > CentOS 7.5 > > > > br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group > default qlen 1000 > link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff > inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute br2 > valid_lft forever preferred_lft forever > inet 10.226.16.10/24 scope global secondary br2 > valid_lft forever preferred_lft forever > inet6 fe80::1456:f9ff:fe06:6228/64 scope link > valid_lft forever preferred_lft forever
