Sorry for the delayed response... IIUC the root cause of the problem is that the nagios VIP is located on a dedicated network (br-monitoring) and with network templates, it isn't possible to assign a default gateway to this network. Also if the nagios VIP were on the management network, it would be fixed by the upcoming 1.0 version of the plugin [1].
Back to the problem described here, the fix is non-trivial and won't be fixed in 1.0 unfortunately. We'll reconsider it for the release coming after 1.0.
Sorry for the delayed response... IIUC the root cause of the problem is that the nagios VIP is located on a dedicated network (br-monitoring) and with network templates, it isn't possible to assign a default gateway to this network. Also if the nagios VIP were on the management network, it would be fixed by the upcoming 1.0 version of the plugin [1].
Back to the problem described here, the fix is non-trivial and won't be fixed in 1.0 unfortunately. We'll reconsider it for the release coming after 1.0.
[1] https:/ /bugs.launchpad .net/lma- toolchain/ +bug/1583994