Public bug reported:
When launching a new instance, in some cases NUmaTopology Filter does
not return available compute nodes, but according to the content of
numa_topology in compute_nodes tables, there are sufficient resources to
satisfy requirements.
I started three instances, attached log show changes in numa_topology,
when I try to start 4th instance which is requesting 4vCPU and according
to numa_topology I have left 8 vCPU, NumaTopology filter incorrectly
returns 0 hosts. If I delete existing instances, I can launch failed one
without any modification.
rpm -qa | grep nova
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
** Affects: nova
Importance: Undecided
Status: New
** Attachment added: "Content of numa_topology in compute_nodes after each
instance"
https://bugs.launchpad.net/bugs/1519878/+attachment/4525323/+files/compute_nodes.txt
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1519878
Title:
numatopology filter incorrectly returns no resources
Status in OpenStack Compute (nova):
New
Bug description:
When launching a new instance, in some cases NUmaTopology Filter does
not return available compute nodes, but according to the content of
numa_topology in compute_nodes tables, there are sufficient resources
to satisfy requirements.
I started three instances, attached log show changes in numa_topology,
when I try to start 4th instance which is requesting 4vCPU and
according to numa_topology I have left 8 vCPU, NumaTopology filter
incorrectly returns 0 hosts. If I delete existing instances, I can
launch failed one without any modification.
rpm -qa | grep nova
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1519878/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
