+++ This bug was initially created as a clone of Bug #1611927 +++

+++ This bug was initially created as a clone of Bug #1460916 +++

Description of problem:
The Filter AggregateInstanceExtraSpecsFilter returned 0 hosts.

The reason behind was name of compute node(DNUCS002-osd-compute-0.localdomain) added in the host-aggregate. The node name given was in capital letter when we re-attached the compute node to the host aggregate with name in small letter( dnucs002-osd-compute-0.localdomain) as mentioned in nova hypervisor-list, it works fine. 

cu want that the compute name should be case insensitive in this case, if not then while adding the compute node to the host aggregate it should throw the error with proper message like 'compute host not found'.

It is confusing that node successfully attached to the hostaggregate, however while spawning the instance the filter simply return 0 hosts without any clue.  


[stack@dnucs002-ospd ~]$ nova hypervisor-list
+----+------------------------------------+-------+---------+
| ID | Hypervisor hostname                | State | Status  |
+----+------------------------------------+-------+---------+
| 1  | dnucs002-osd-compute-0.localdomain | up    | enabled |
| 4  | dnucs002-compute-3.localdomain     | up    | enabled |


[stack@dnucs002-ospd ~]$ openstack aggregate show 2
+-------------------+-----------------------------------------+
| Field             | Value                                   |
+-------------------+-----------------------------------------+
| availability_zone | mgmt                                    |
| created_at        | 2017-06-12T19:48:03.000000              |
| deleted           | False                                   |
| deleted_at        | None                                    |
| hosts             | [u'DNUCS002-osd-compute-0.localdomain'] |


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
The Filter AggregateInstanceExtraSpecsFilter returned 0 hosts.

Expected results:

It should returned the hosts attached to the hostaggregate

Additional info:

--- Additional comment from Rajesh Tailor on 2017-08-08 04:21:29 EDT ---

The issue is there in upstream master branch as well, I have reported it to
upstream bug tracking launchpad.

https://bugs.launchpad.net/nova/+bug/1709260

--- Additional comment from Scott Lewis on 2017-09-29 14:28:36 EDT ---

Removing TR until this is properly Triaged, planned for a specific TM, and is fully acked.

--- Additional comment from Scott Lewis on 2017-10-06 11:05:18 EDT ---

This item has been properly Triaged and planned for the OSP13 release, and is being tagged for tracking. For details, see https://mojo.redhat.com/docs/DOC-1144661#jive_content_id_OSP_Release_Planning

--- Additional comment from Scott Lewis on 2018-01-25 12:24:14 EST ---

This item has had a change in release flag, and has been removed from tracking in OSP13.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-01-25 12:25:09 EST ---

This item has been properly Triaged and planned for the release, and Target Release is now set to match the release flag. For details, see https://mojo.redhat.com/docs/DOC-1144661#jive_content_id_OSP_Release_Planning

--- Additional comment from Scott Lewis on 2018-04-17 09:09:37 EDT ---

This item has been properly Triaged and planned for the OSP14 release, and is being tagged for tracking.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-08-03 06:03:03 IST ---

This bugzilla has been removed from the release since it is missing the Triaged keyword or does not have an acked release flag. For details, see https://mojo.redhat.com/docs/DOC-1144661#jive_content_id_OSP_Release_Planning.

--- Additional comment from Steve Linabery on 2019-01-11 16:26:38 GMT ---

OSP12 Retirement Text-Only Advisory shipped 19-Dec-2018