Comment 1 for bug 1503881

After some further investigation, I have found that the workaround is unnecessary if I add the secondary IP address with either global or host scope. I still think it's a bug in NetworkManager as I don't think it's the correct or intended behaviour. The first IP address given to an interface is the one that's supposed to be bound to by default, and it shouldn't matter whether additional addresses have host, link or global scope.