yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #81112
[Bug 1857306] [NEW] _bury_in_cell0 could not handle instance duplicate exception
Public bug reported:
For stable/stein
if there were NoValidHost from scheduler, conductor should create
Instance object in cell0. But I found if there is additional
exception(InstanceExist) in the function, conductor could not catch the
exception which result in instance state stuck in 'scheduling'.
How to reproduce
1. osapi_compute_unique_server_name_scope = True
2. Cellv2
3. Create instance with hostname which previously built and without any valid host.
Result
1. Conductor does not make instance DB creation in cell0 from
_bury_in_cell0
What to expect
1. nova_cell0 create instance in cell0 with error state.
Thanks
** 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/1857306
Title:
_bury_in_cell0 could not handle instance duplicate exception
Status in OpenStack Compute (nova):
New
Bug description:
For stable/stein
if there were NoValidHost from scheduler, conductor should create
Instance object in cell0. But I found if there is additional
exception(InstanceExist) in the function, conductor could not catch
the exception which result in instance state stuck in 'scheduling'.
How to reproduce
1. osapi_compute_unique_server_name_scope = True
2. Cellv2
3. Create instance with hostname which previously built and without any valid host.
Result
1. Conductor does not make instance DB creation in cell0 from
_bury_in_cell0
What to expect
1. nova_cell0 create instance in cell0 with error state.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1857306/+subscriptions
Follow ups