Sort ip addresses chooses the wrong primary IPv4

[JOJ0]

Hi,
since this commit we are experiencing an issue on our servers: 86ff7be

Usually we have the hosts "physical" interface on e.g eth0 and then several interfaces for running services e.g eth0:123, eth0:124

Let's assume host ip is 192.168.0.200 and service ips are 192.168.0.123 and 192.168.0.124

Prior to mentioned commit the behaviour was as expected: If hosts::one_primary_ipv4: true, the ip address
192.168.0.200 would be under # Primary interface

Now the new behaviour is that the sorting puts the lowest IP address first (192.168.0.123) and uses it as the Primary interface.
We can't assume that always the lowest IP is also the node IP. We would expect the physical interface (i.e eth0 vs. eth0:something) to be used as the first primary_ipv4 interface.

[JOJ0]

In the meantime we downgraded to 3.0.1, to fix the issue on our servers :-)

[chrekh]

Thanks for the report. This was indeed unfortunate and bad: I'll look into it later, and if I don't come up with a better solution make the sorting optional by boolean parameter, (defaulting to false)

[JOJ0]

Thanks for your quick reply! That's great news! Since downgrading fixes it for us without any tedious workarounds, there is no need to hurry, at least on our side! Good luck with finding a good solution. Fun fact: We also thought about that making the sorting configurable could be a possible solution!

[chrekh]

This should be fixed in version 4.0.0