yahoo-eng-team team mailing list archive

[Trung Trinh <trung.t.trinh@xxxxxxxxxxxxxx>]

Public bug reported:

Version: stable/juno

Bug description:
In the process of launching new VM instance, it is detected that the information of host is None in the "db_instance" returned by the function get_db_instance(). This especially occurs at the beginning of the process of launching new VM when the task_state is SCHEDULING.

In the function show() or detail() of the class nova.api.openstack.compute.contrib.extended_availability_zone.ExtendedAZController,
it can be seen this phenomenon together with a remarkable comment: # Likely hasn't reached a viable compute node yet

Proposal:
Find out the root cause and fix or add some work-around.

** Affects: nova
     Importance: Undecided
     Assignee: Trung Trinh (trung-t-trinh)
         Status: New


** Tags: nova-manage

** Changed in: nova
     Assignee: (unassigned) => Trung Trinh (trung-t-trinh)

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

Title:
  Info of host is None in the "db_instance" returned by the function
  get_db_instance()

Status in OpenStack Compute (Nova):
  New

Bug description:
  Version: stable/juno

  Bug description:
  In the process of launching new VM instance, it is detected that the information of host is None in the "db_instance" returned by the function get_db_instance(). This especially occurs at the beginning of the process of launching new VM when the task_state is SCHEDULING.

  In the function show() or detail() of the class nova.api.openstack.compute.contrib.extended_availability_zone.ExtendedAZController,
  it can be seen this phenomenon together with a remarkable comment: # Likely hasn't reached a viable compute node yet

  Proposal:
  Find out the root cause and fix or add some work-around.

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