numa_topology does not get populated for compute_nodes table

Bug #1519164 reported by Serguei Bezverkhi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

I am running Liberty on RHEL 7.2. When I request via flavor any numa related attributes, instance fails to launch as NUMA filter cannot find host with requested resources available.

When I checked nova database, compute_nodes table, I noticed numa_topoly has no information.

use nova;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [nova]> SELECT numa_topology FROM compute_nodes;
+---------------+
| numa_topology |
+---------------+
| NULL |
+---------------+
1 row in set (0.01 sec)

It supposed to return numa related information.

Here is the version of nova rpms I am running on this server:

openstack-nova-conductor-12.0.0-1.el7.noarch
python-novaclient-2.30.1-1.el7.noarch
openstack-nova-console-12.0.0-1.el7.noarch
openstack-nova-common-12.0.0-1.el7.noarch
openstack-nova-scheduler-12.0.0-1.el7.noarch
openstack-nova-compute-12.0.0-1.el7.noarch
python-nova-12.0.0-1.el7.noarch
openstack-nova-novncproxy-12.0.0-1.el7.noarch
openstack-nova-api-12.0.0-1.el7.noarch
openstack-nova-cert-12.0.0-1.el7.noarch

Please let me know what additional information required.

Thank you

Serguei

affects: tripleo → nova
liunian (839274949-c)
Changed in nova:
status: New → Incomplete
status: Incomplete → New
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

@Serguei Bezverkhi:

Could you please provide the following information:
* How did you request NUMA releated attributes with the flavor? The
  more specific you are the better.
* Would you please attach the following logs
    * nova-compute
    * nova-scheduler
    * nova-conductor
  You could give "sosreport" a try. Execute the following on the
  controller and the compute node:
    $ sudo sosreport -o openstack_nova --batch

After you provided this information, please set this bug status back
to "New".

Changed in nova:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.