yahoo-eng-team team mailing list archive

[Sean McGinnis <sean.mcginnis@xxxxxxxxx>]

Public bug reported:

We've seen several cases now where n-cpu fails to start in gate runs. It
appears that during the service init it tries to call out to the cell1
conductor. Logs show n-cond-cell1 did start about 1 second before this,
but maybe too soon to accept API calls. Traceback in the n-cpu log has
the message:

"MessagingTimeout: Timed out waiting for a reply to message ID"

http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-
nova.2018-08-28.log.html#t2018-08-28T19:28:52

http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22_determine_version_cap%5C%22%20AND%20tags:%5C%22screen-n-cpu.txt%5C%22&from=7d

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  n-cpu fails init on timeout calling n-cond-cell1

Status in OpenStack Compute (nova):
  New

Bug description:
  We've seen several cases now where n-cpu fails to start in gate runs.
  It appears that during the service init it tries to call out to the
  cell1 conductor. Logs show n-cond-cell1 did start about 1 second
  before this, but maybe too soon to accept API calls. Traceback in the
  n-cpu log has the message:

  "MessagingTimeout: Timed out waiting for a reply to message ID"

  http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-
  nova.2018-08-28.log.html#t2018-08-28T19:28:52

  http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22_determine_version_cap%5C%22%20AND%20tags:%5C%22screen-n-cpu.txt%5C%22&from=7d

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