yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

http://logs.openstack.org/82/482382/4/gate/gate-nova-tox-functional-py35
-ubuntu-xenial/fdfd05a/testr_results.html.gz

The relevant trace is here:

nova.exception.NoValidHost: No valid host was found. Is the appropriate service running?
2017-07-15 12:27:14,738 WARNING [nova.scheduler.utils] Failed to compute_task_build_instances: No valid host was found. Is the appropriate service running?
2017-07-15 12:27:14,738 WARNING [nova.scheduler.utils] Setting instance to ERROR state.
2017-07-15 12:27:14,783 INFO [nova.osapi_compute.wsgi.server] 127.0.0.1 "POST /v2.1/6f70656e737461636b20342065766572//servers HTTP/1.1" status: 202 len: 957 time: 0.2136991
2017-07-15 12:27:14,848 INFO [nova.osapi_compute.wsgi.server] 127.0.0.1 "GET /v2.1/6f70656e737461636b20342065766572//servers/8e48b388-2599-4dec-a920-bcba43a5ffb0 HTTP/1.1" status: 200 len: 2281 time: 0.0618613
2017-07-15 12:27:14,886 INFO [nova.api.openstack.wsgi] HTTP exception thrown: Instance 8e48b388-2599-4dec-a920-bcba43a5ffb0 is in an invalid state for 'rebuild'

And I think there are no hosts because of a lock timeout exception when
updating available resources for the compute node - which I'm not sure
if that's related to this specific test and how it's setup or if it's
more generic, but we can't really fingerprint the timeout exception
logstash.

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22%5Bnova.api.openstack.wsgi%5D%20HTTP%20exception%20thrown%3A%20Instance%5C%22%20AND%20message%3A%5C%22is%20in%20an%20invalid%20state%20for%20'rebuild'%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d

18 hits in 7 days, check and gate, all failures.

** Affects: nova
     Importance: Undecided
         Status: Confirmed


** Tags: functional testing

-- 
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/1704588

Title:
  Functional test_rebuild_server_with_description fails with
  "[nova.api.openstack.wsgi] HTTP exception thrown: Instance
  8e48b388-2599-4dec-a920-bcba43a5ffb0 is in an invalid state for
  'rebuild'"

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  http://logs.openstack.org/82/482382/4/gate/gate-nova-tox-functional-
  py35-ubuntu-xenial/fdfd05a/testr_results.html.gz

  The relevant trace is here:

  nova.exception.NoValidHost: No valid host was found. Is the appropriate service running?
  2017-07-15 12:27:14,738 WARNING [nova.scheduler.utils] Failed to compute_task_build_instances: No valid host was found. Is the appropriate service running?
  2017-07-15 12:27:14,738 WARNING [nova.scheduler.utils] Setting instance to ERROR state.
  2017-07-15 12:27:14,783 INFO [nova.osapi_compute.wsgi.server] 127.0.0.1 "POST /v2.1/6f70656e737461636b20342065766572//servers HTTP/1.1" status: 202 len: 957 time: 0.2136991
  2017-07-15 12:27:14,848 INFO [nova.osapi_compute.wsgi.server] 127.0.0.1 "GET /v2.1/6f70656e737461636b20342065766572//servers/8e48b388-2599-4dec-a920-bcba43a5ffb0 HTTP/1.1" status: 200 len: 2281 time: 0.0618613
  2017-07-15 12:27:14,886 INFO [nova.api.openstack.wsgi] HTTP exception thrown: Instance 8e48b388-2599-4dec-a920-bcba43a5ffb0 is in an invalid state for 'rebuild'

  And I think there are no hosts because of a lock timeout exception
  when updating available resources for the compute node - which I'm not
  sure if that's related to this specific test and how it's setup or if
  it's more generic, but we can't really fingerprint the timeout
  exception logstash.

  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22%5Bnova.api.openstack.wsgi%5D%20HTTP%20exception%20thrown%3A%20Instance%5C%22%20AND%20message%3A%5C%22is%20in%20an%20invalid%20state%20for%20'rebuild'%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d

  18 hits in 7 days, check and gate, all failures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1704588/+subscriptions