Fixes VNF state being stuck in PENDING_CREATE

This commit fixes the issue where the VNF state is stuck in
PENDING_CREATE instead of ERROR when a VM fails to be created as
part of VNF creation.
Change-Id: Ib52870320887fbd64ec05432c52bed1f85d33ba4
Closes-Bug: #1499067
Closes-Bug: #1497035
This commit is contained in:
Vishwanath Jayaraman 2015-10-05 13:14:26 -05:00
parent 04e08a3fd7
commit d6c7961d56
1 changed files with 2 additions and 2 deletions

View File

@ -344,7 +344,7 @@ class DeviceHeat(abstract_driver.DeviceAbstractDriver):
stack_retries = stack_retries - 1
LOG.debug(_('stack status: %(stack)s %(status)s'),
{'stack': stack, 'status': status})
{'stack': str(stack), 'status': status})
if stack_retries == 0:
LOG.warn(_("Resource creation is"
" not completed within %(wait)s seconds as "
@ -352,7 +352,7 @@ class DeviceHeat(abstract_driver.DeviceAbstractDriver):
{'wait': (STACK_RETRIES * STACK_RETRY_WAIT),
'stack': device_id})
if status != 'CREATE_COMPLETE':
raise RuntimeError(_("creation of server %s faild") % device_id)
raise vnfm.DeviceCreateWaitFailed(device_id=device_id)
outputs = stack.outputs
LOG.debug(_('outputs %s'), outputs)
PREFIX = 'mgmt_ip-'