Bug 1611450

Summary:	[RHOSP 13] Filter AggregateInstanceExtraSpecsFilter returned 0 hosts
Product:	Red Hat OpenStack	Reporter:	Rajesh Tailor <ratailor>
Component:	openstack-nova	Assignee:	Rajesh Tailor <ratailor>
Status:	CLOSED ERRATA	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	low	Docs Contact:
Priority:	low
Version:	13.0 (Queens)	CC:	berrange, dasmith, eglynn, jhakimra, jschluet, kchamart, lyarwood, mbooth, mnadeem, ratailor, sbauza, sgordon, srevivo, stephenfin, vromanso
Target Milestone:	z5	Keywords:	TestOnly, Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-17.0.7-1.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1460916	Environment:
Last Closed:	2019-03-14 13:54:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1460916, 1611927, 1694152
Bug Blocks:

Description Rajesh Tailor 2018-08-02 09:10:10 UTC

+++ 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.

Comment 6 Jon Schlueter 2018-10-15 13:47:24 UTC

This mentioned patch was also reverted upstream ... 

What is next step for this BZ?

Comment 7 Rajesh Tailor 2018-10-16 05:33:36 UTC

Hi Jon,

The patch mentioned patch [1] is reverted upstream and another patch [2] which
fixes the issue in different way is merged upstream till stable/pike.
We need to import that to relevent branches.

[1] https://review.openstack.org/#/q/Ibd44ba9de5680958f55f0ae6325cfc33dabadc4c
[2] https://review.openstack.org/#/q/I597dee74d33de337913eddda74ab056fbf81a23c

Comment 8 Jon Schlueter 2018-10-16 15:51:25 UTC

fixing up eternal trackers

Comment 9 Jon Schlueter 2018-10-16 16:20:55 UTC

openstack-nova-17.0.7-1.el7ost - new mentioned patch included in build

Comment 10 Shelley Dunne 2018-10-26 15:08:12 UTC

Not in Advisory removing Target Milestone z3 planned to ship 14-Nov

Comment 11 Lon Hohberger 2018-11-26 11:45:19 UTC

According to our records, this should be resolved by openstack-nova-17.0.7-2.el7ost.  This build is available now.

Comment 13 errata-xmlrpc 2019-03-14 13:54:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0565