yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

To summarize the problem:

(10:58:09 AM) mriedem: so we start placement-api 32 seconds after we start nova-compute,
(10:58:23 AM) mriedem: nova-compute starts up and tries to register the compute node with placement but gets a 503 b/c placement isn't up yet,
(10:58:34 AM) mriedem: meanwhile, the compute host is mapped to the cell and tests start,
(10:59:01 AM) mriedem: test tries to create a server, scheduler asks placement for a resource provider (compute node) for the server, there are 0 because none are registered, and the server create fails,
(10:59:20 AM) mriedem: 15 seconds later, n-cpu registers the compute node with placement during it's periodic task to update avialable resources (1 minute cron)

** Changed in: nova
       Status: New => Invalid

** Also affects: devstack
   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/1695634

Title:
  Something weird just broke in creating servers

Status in devstack:
  In Progress
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  shade's functional tests just started breaking since yesterday. The
  nova changes between a passing and a failing test are:

  --e git+https://git.openstack.org/openstack/nova@046149825c5d6d5ac56a5f5d4498c996dfe8c7ee#egg=nova
  +-e git+https://git.openstack.org/openstack/nova@28ace935cdc2e040206a1fee84ee29d669856ca8#egg=nova

  Failing run (includes logging of the REST calls):

  http://logs.openstack.org/95/468095/2/gate/gate-shade-
  functional/3f5d8dc/console.html

  Succeeding run from yesterday of the same patch:

  http://logs.openstack.org/95/468095/2/check/gate-shade-
  functional/ad48ef0/console.html

  Looking at the diff between the passing and failing nova changes,
  there do seem to be changes related to server creation and flavors.
  They all seem to be properly behind a microversion, but since I'm
  seeing failures all of a sudden, I figured I'd report it in case nova
  notices something funky in there.

  I'm continuing to investigate shade-side and will update this if I
  find something.

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