On openshift, nodes can be configured with a different network device than the default one (eth1 instead of eth0 for example).
On zabbix server cartridge it is important to use this explicit device defined in /etc/openshift/node.conf on nodes, if he code use the wrong ip address, somme zabbix agents will not be able to push metrics to zabbix server correctly.
Possible solution :
Today, zabbix server cartridge code use facter to define ZABBIX_SERVERIP and it's possible to do : facter -p "ipaddress$EXTERNAL_ETH_DEV" in a shell to get the correct ip.
On openshift, nodes can be configured with a different network device than the default one (eth1 instead of eth0 for example).
On zabbix server cartridge it is important to use this explicit device defined in /etc/openshift/node.conf on nodes, if he code use the wrong ip address, somme zabbix agents will not be able to push metrics to zabbix server correctly.
Possible solution :
Today, zabbix server cartridge code use facter to define ZABBIX_SERVERIP and it's possible to do : facter -p "ipaddress$EXTERNAL_ETH_DEV" in a shell to get the correct ip.