← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1672625] [NEW] Instance stuck in schedule state in Ocata release

 

Public bug reported:

I have built devstack multinode setup on ocata release. Unable to launch
any instances. All the instances are stuck into "scheduling" state. The
only error in n-api log is:

n-api.log:1720:2017-03-14 11:48:59.805 25488 ERROR nova.compute.api [req-9a0f533b-b5af-4061-9b88-d00012762131 vks vks] No cells are configured, unable to list instances
n-api.log:1730:2017-03-14 11:49:21.641 25488 ERROR nova.compute.api [req-5bdcd955-ddec-4283-9b07-ccd1221912b5 vks vks] No cells are configured, unable to list instances
n-api.log:1740:2017-03-14 11:49:26.659 25488 ERROR nova.compute.api [req-8f9e858b-d80a-4770-a727-f94dcebcc986 vks vks] No cells are configured, unable to list instances
n-api.log:1816:2017-03-14 11:49:48.611 25487 ERROR nova.compute.api [req-da86d769-49d7-4eec-b389-0dca123b7e16 vks vks] No cells are configured, unable to list instances
n-api.log:1899:2017-03-14 11:51:04.481 25487 INFO nova.api.openstack.ws

n-sch has no error log.

o/p: of service list

stack@stack:~$ nova service-list
/usr/local/lib/python2.7/dist-packages/novaclient/client.py:278: UserWarning: The 'tenant_id' argument is deprecated in Ocata and its use may result in errors in future releases. As 'project_id' is provided, the 'tenant_id' argument will be ignored.
  warnings.warn(msg)
+----+------------------+-------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary           | Host  | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+-------+----------+---------+-------+----------------------------+-----------------+
| 3  | nova-conductor   | stack | internal | enabled | up    | 2017-03-14T07:21:38.000000 | -               |
| 5  | nova-scheduler   | stack | internal | enabled | up    | 2017-03-14T07:21:37.000000 | -               |
| 6  | nova-consoleauth | stack | internal | enabled | up    | 2017-03-14T07:21:44.000000 | -               |
| 7  | nova-compute     | nfp   | nova     | enabled | up    | 2017-03-14T07:21:38.000000 | -               |
+----+------------------+-------+----------+---------+-------+----------------------------+-----------------+

** Affects: nova
     Importance: Undecided
         Status: New

** Summary changed:

- Instance stuck in schedule state
+ Instance stuck in schedule state in Ocata release

** Project changed: openstack-manuals => nova

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

Title:
  Instance stuck in schedule state in Ocata release

Status in OpenStack Compute (nova):
  New

Bug description:
  I have built devstack multinode setup on ocata release. Unable to
  launch any instances. All the instances are stuck into "scheduling"
  state. The only error in n-api log is:

  n-api.log:1720:2017-03-14 11:48:59.805 25488 ERROR nova.compute.api [req-9a0f533b-b5af-4061-9b88-d00012762131 vks vks] No cells are configured, unable to list instances
  n-api.log:1730:2017-03-14 11:49:21.641 25488 ERROR nova.compute.api [req-5bdcd955-ddec-4283-9b07-ccd1221912b5 vks vks] No cells are configured, unable to list instances
  n-api.log:1740:2017-03-14 11:49:26.659 25488 ERROR nova.compute.api [req-8f9e858b-d80a-4770-a727-f94dcebcc986 vks vks] No cells are configured, unable to list instances
  n-api.log:1816:2017-03-14 11:49:48.611 25487 ERROR nova.compute.api [req-da86d769-49d7-4eec-b389-0dca123b7e16 vks vks] No cells are configured, unable to list instances
  n-api.log:1899:2017-03-14 11:51:04.481 25487 INFO nova.api.openstack.ws

  n-sch has no error log.

  o/p: of service list

  stack@stack:~$ nova service-list
  /usr/local/lib/python2.7/dist-packages/novaclient/client.py:278: UserWarning: The 'tenant_id' argument is deprecated in Ocata and its use may result in errors in future releases. As 'project_id' is provided, the 'tenant_id' argument will be ignored.
    warnings.warn(msg)
  +----+------------------+-------+----------+---------+-------+----------------------------+-----------------+
  | Id | Binary           | Host  | Zone     | Status  | State | Updated_at                 | Disabled Reason |
  +----+------------------+-------+----------+---------+-------+----------------------------+-----------------+
  | 3  | nova-conductor   | stack | internal | enabled | up    | 2017-03-14T07:21:38.000000 | -               |
  | 5  | nova-scheduler   | stack | internal | enabled | up    | 2017-03-14T07:21:37.000000 | -               |
  | 6  | nova-consoleauth | stack | internal | enabled | up    | 2017-03-14T07:21:44.000000 | -               |
  | 7  | nova-compute     | nfp   | nova     | enabled | up    | 2017-03-14T07:21:38.000000 | -               |
  +----+------------------+-------+----------+---------+-------+----------------------------+-----------------+

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


Follow ups