Comment 3 for bug 1489963

It won't bind to the vip and member network IP addr since vip and member network IP addr are located in namespace amphora-haproxy.
Cloud you list more drawbacks of user scenarios when binds to '0.0.0.0'?
Thanks a lot.

root@amphora-84ef3a6b-f6b3-4aea-a106-a862de13ba5f:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fa:16:3e:4a:bb:2e brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.3/24 brd 192.168.0.255 scope global eth0 <<<< lb-mgmt ip addr
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe4a:bb2e/64 scope link
       valid_lft forever preferred_lft forever
root@amphora-84ef3a6b-f6b3-4aea-a106-a862de13ba5f:~# ip netns exec amphora-haproxy ip addr
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fa:16:3e:1f:75:6e brd ff:ff:ff:ff:ff:ff
    inet 1.0.0.4/24 brd 1.0.0.255 scope global eth1 <<<< member network IP address
       valid_lft forever preferred_lft forever
    inet 1.0.0.100/24 brd 1.0.0.255 scope global secondary eth1:0 <<<< vip
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe1f:756e/64 scope link
       valid_lft forever preferred_lft forever
root@amphora-84ef3a6b-f6b3-4aea-a106-a862de13ba5f:~#