Hi Valentin,
thank you for your interest in this issue.
The cluster does not exist anymore, but the problem was probably
due to the the fact that the cluster was using DHCP for network
configuration. I agree that is not recomandable for server, but the
cluster was intended for testing purpose e not for production environment.
It is clearly a minor bug that could be closed, but inserting a
hook in the dhclient (man dhclient-script for details) script directory
to reload the o2cb may solve this issue.
Regards.
On 08/07/16 12:16, Valentin Vidic wrote:
This probably depends on the type on networking on the host. If the
problem still exists please send the network and cluster config.
