Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694152 - [RHOSP 10] Filter AggregateInstanceExtraSpecsFilter returned 0 hosts
Summary: [RHOSP 10] Filter AggregateInstanceExtraSpecsFilter returned 0 hosts
Keywords:
Status: MODIFIED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: async
: 10.0 (Newton)
Assignee: Rajesh Tailor
QA Contact: nova-maint
URL:
Whiteboard:
Depends On: 1460916 1611927
Blocks: 1611450
TreeView+ depends on / blocked
 
Reported: 2019-03-29 16:27 UTC by Stephen Finucane
Modified: 2019-04-11 13:42 UTC (History)
14 users (show)

Fixed In Version: openstack-nova-14.1.0-45.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1611927
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Stephen Finucane 2019-03-29 16:27:04 UTC
+++ 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


Note You need to log in before you can comment on or make changes to this bug.