Comment 5 for bug 1668828

Now that I've written a recreate test for this on the nova side, I think patch set 3 on the Tempest change was actually correct and the nova api is performing as intended. The nova api code performs a regex match on the ip filter, it always has. Earlier today when I was looking at this, I thought the nova-api code was short circuiting and only returning the 10.1.1.10 match in this example, but now that I re-read the commit message on the tempest change, it's actually returning both 10.1.1.10 and 10.1.1.1 and it's tempest that's not handling that correctly.