Zenoss5 (deployed via auto-deploy scripts ) - unable to discover network

For security reasons, my VM ( Centos 7 ) has 3 adapters.

1. mgmt ( for user access ) ens160
2. network discovery ens192
3. to access internet ens224

I used the auto-deploy scripts to install the Zenoss5, I had some trouble in the middle, part of the logs here"
#####
2.1 IP configurations
Network interface auto detection failed. Available interfaces in your system:
ens160 ens192 ens224
Please write interface, which you want to use for deployement (see listing above), e.g. eth1 or ens160:
ens160
... continuing
#####

And

#####
4.1 Adding current host to the default resource pool
Please be patient, because docker image zenoss/serviced-isvcs must be downloaded before first start.
You can check progress in new console: journalctl -u serviced -f -a
Script is trying to check status every 10s. Timeout for this step is 15 minutes.
serviced host list 2>&1
could not create a client to the master: dial tcp 10.100.100.6:4979: connection refused
#1: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#2: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#3: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#####

what I did was to bring up the serviced manually, then continue with the shell script ( cut the sections which have been executed ), then the install went successfully at the end.

After fixing the DNS alias, I am able to reach the ControlCenter console, bring up the Zenoss5 application and even reach the Zenoss5 console, followed the set up winzard, I thought I am done. But after trying to get couple of servers discovered,
I noticed that, I can't reach the servers from Zenoss application, however, I am able to reach those devices from the command line on the VM itself.

After reading the installation guide, I thought there might be something to do with the internal communication between virtual bridge and the real adapter.

So checked the firewalld, it is not runing.
Checked the iptables, it is not loaded ( not installed )

Trying some tcpdump on the serve when I try to model a device or run snmpwalk command, that is something I captured.

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on docker0, link-type EN10MB (Ethernet), capture size 65535 bytes
11:45:37.978531 IP 172.17.0.58.51053 > 172.28.11.244.snmp: C=public GetNextRequest(21) .iso.org
11:45:38.979182 IP 172.17.0.58.51053 > 172.28.11.244.snmp: C=public GetNextRequest(21) .iso.org
11:45:39.980071 IP 172.17.0.58.51053 > 172.28.11.244.snmp: C=public GetNextRequest(21) .iso.org
11:45:40.981066 IP 172.17.0.58.51053 > 172.28.11.244.snmp: C=public GetNextRequest(21) .iso.org
11:45:41.981281 IP 172.17.0.58.51053 > 172.28.11.244.snmp: C=public GetNextRequest(21) .iso.org
11:45:42.981661 IP 172.17.0.58.51053 > 172.28.11.244.snmp: C=public GetNextRequest(21) .iso.org

so here, 172.17.0.58 is a virtual bridge, I believe.
172.28.11.244 is my target server.

the current docker0 address is the default
##############################################################
docker0: flags=4163 mtu 1500
inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0
ether 56:84:7a:fe:97:99 txqueuelen 0 (Ethernet)
RX packets 2045640 bytes 1703948243 (1.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 973695 bytes 786651898 (750.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
###############################################################

Any ideas, guys Any help is appreciated.

I found that Zenoss5 is so hard to deploy in comparison to Zenoss4, the idea of ControCenter is to simply the deployment, but I found it is actually harder, I think I don't fully understand how ControlCenter works.

Cheers,
Hubery