Comment 2 for bug 1740320

The test does show the issue:

http://logs.openstack.org/67/529867/1/check/tempest-full/23d2919/controller/logs/screen-n-sch.txt.gz#_Dec_22_18_14_13_693048

Dec 22 18:14:13.693048 ubuntu-xenial-ovh-bhs1-0001579658 nova-scheduler[9206]: WARNING nova.scheduler.filters.num_instances_filter [None req-75ecdad4-ef94-46c0-bd60-293038eadbd2 tempest-ServerRescueTestJSON-754723157 tempest-ServerRescueTestJSON-754723157] Reported number of instances (0) does not match the tracked number of instances (1).

That shows up twice in that one Tempest run.

I don't know what the root cause is, and I'm not sure we should just paper over it by checking for 0 and then using the other value if they aren't the same.