Yeah, the nova.CONF cpu_allocation_ratio is being overridden to 0.0:
Aug 27 07:43:02.179927 dsvm-devstack-citrix-lon-nodepool-1379254
nova-compute[21125]: DEBUG oslo_service.service [None
req-4bb236c4-54c3-42b7-aa4e-e5c8b1ece0c7 None None] cpu_allocation_ratio
= 0.0 {{(pid=21125) log_opt_values
/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:3019}}
Best,
-jay
On 08/28/2018 10:01 AM, Bob Ball wrote:
We're not running with [1], however that did also fail the CI in the same way -
see [2] for the full logs.
The first failing appeared to be around Aug 27 08:32:14:
Aug 27 08:32:14.502788 dsvm-devstack-citrix-lon-nodepool-1379254
devstack@placement-api.service[13219]: DEBUG nova.api.openstack.placement.requestlog
[req-94714f18-87f3-4ff5-9b17-f6e50131b3a9 req-fc47376d-cf04-4cd3-b69c-31ef4d5739a4 service
placement] Starting request: 192.168.33.1 "GET
/placement/allocation_candidates?limit=1000&resources=MEMORY_MB%3A64%2CVCPU%3A1"
{{(pid=13222) __call__ /opt/stack/new/nova/nova/api/openstack/placement/requestlog.py:38}}
Aug 27 08:32:14.583676 dsvm-devstack-citrix-lon-nodepool-1379254
devstack@placement-api.service[13219]: DEBUG
nova.api.openstack.placement.objects.resource_provider
[req-94714f18-87f3-4ff5-9b17-f6e50131b3a9
req-fc47376d-cf04-4cd3-b69c-31ef4d5739a4 service placement] found 0 providers
with available 1 VCPU {{(pid=13222) _get_provider_ids_matching
/opt/stack/new/nova/nova/api/openstack/placement/objects/resource_provider.py:2928}}
Just looking at Naichuan's output, I wonder if this is because allocation_ratio
is registered as 0 in the inventory.
Bob
[2]
http://dd6b71949550285df7dc-dda4e480e005aaa13ec303551d2d8155.r49.cf1.rackcdn.com/41/590041/17/check/dsvm-tempest-neutron-network/afadfe7/
-----Original Message-----
From: Eric Fried [mailto:openst...@fried.cc]
Sent: 28 August 2018 14:22
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently
because of placement update
Naichuan-
Are you running with [1]? If you are, the placement logs (at debug
level) should be giving you some useful info. If you're not... perhaps you
could pull that in :) Note that it refactors the _get_provider_ids_matching
method completely, so it's possible your problem will magically go away when
you do.
[1] https://review.openstack.org/#/c/590041/
On 08/28/2018 07:54 AM, Jay Pipes wrote:
On 08/28/2018 04:17 AM, Naichuan Sun wrote:
Hi, experts,
XenServer CI failed frequently with an error "No valid host was found.
" for more than a week. I think it is cause by placement update.
Hi Naichuan,
Can you give us a link to the logs a patchset's Citrix XenServer CI
that has failed? Also, a timestamp for the failure you refer to would
be useful so we can correlate across service logs.
Thanks,
-jay
______________________________________________________________________
____ OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
