yahoo-eng-team team mailing list archive

[wingwj <wingwj@xxxxxxxxx>]

Public bug reported:

Now there's a 'None' task_state between 'SCHEDULING' &
'BLOCK_DEVICE_MAPPING'.

So if compute node is rebooted after that procession, all building VMs on it will always stay in 'None' task_state.
And it's useless and not convenient for locating problems. 

Therefore, we need to add one new task_state(like 'STARTING_BUILD') for
that period.

This new task_state also needs to be added in the Doc.

The related discussion could be found here:
http://lists.openstack.org/pipermail/openstack-dev/2014-June/038638.html

** Affects: nova
     Importance: Undecided
     Assignee: wingwj (wingwj)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => wingwj (wingwj)

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

Title:
  Need to add a new task_state between 'SCHEDULING' &
  'BLOCK_DEVICE_MAPPING'

Status in OpenStack Compute (Nova):
  New

Bug description:
  Now there's a 'None' task_state between 'SCHEDULING' &
  'BLOCK_DEVICE_MAPPING'.

  So if compute node is rebooted after that procession, all building VMs on it will always stay in 'None' task_state.
  And it's useless and not convenient for locating problems. 

  Therefore, we need to add one new task_state(like 'STARTING_BUILD')
  for that period.

  This new task_state also needs to be added in the Doc.

  The related discussion could be found here:
  http://lists.openstack.org/pipermail/openstack-dev/2014-June/038638.html

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