Comment 0 for bug 1709260

I have multinode devstack setup with 2 compute and a controller node.
The hostnames of the nodes are as follows:
controller: controller.example.com
compute0: compute0.example.com
compute1: compute1.example.com

Reproduction steps:

1) I have created a host-aggregate in availability zone "nova".
    nova aggregate-create test_agg nova

2) Then I set metadata on that host-aggregate.
    nova aggregate-set-metadata 1 ssd=true

3) Then I added compute hosts mentioned above to host-aggregate.
    nova aggregate-add-host test_agg COMPUTE0.example.com
    nova aggregate-add-host test_agg compute1.example.com

While adding compute0 to host-aggregate, if I provide hostname as "COMPUTE0.example.com", instead of
throwing HostNotFound error, it is added to host-aggregate.

4) After that I have created a flavor.
nova flavor-create ssd.large 6 8192 80 4

5) Added metadata to flavor.
nova flavor-key ssd.large set ssd=true

Now when I try to create instance with above mentioned flavor, I can't spawn it on compute0 host. As scheduler is filtering only compute1 with AggregateInstanceExtraSpecsFilter filter.

Expected Result: while adding the case-sensitive host to host-aggregate, nova-api should have thrown HostNotFound error.