Pre-deploy validations should wait for nova resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Dmitry Tantsur |
Bug Description
Currently, if you start a new deploy right after tearing down a previous one, you can hit the following error:
Started Mistral Workflow tripleo.
Waiting for messages on queue '684d93c8-
{u'errors': [u'Only 0 nodes are exposed to Nova of 15 requests. Check that enough nodes are in "available" state with maintenance mode off.'], u'result': {u'enough_nodes': False, u'statistic
s': {u'count': 0, u'vcpus_used': 0, u'local_gb_used': 0, u'manager': {u'api': {u'server_groups': None, u'keypairs': None, u'servers': None, u'server_
ns': None, u'agents': None, u'instance_action': None, u'glance': None, u'hypervisor_
ERRORS
[u'Only 0 nodes are exposed to Nova of 15 requests. Check that enough nodes are in "available" state with maintenance mode off.', u'Only 0 nodes are exposed to Nova of 15 requests. Check that enough nodes are in "available" state with maintenance mode off.']
Configuration has 2 errors, fix them before proceeding. Ignoring these errors is likely to lead to a failed deploy.
It goes away after a minute or two. I think we should retry our workflows instead of making a user retry.
Initially reported in https:/
description: | updated |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Fix proposed to branch: master /review. openstack. org/516382
Review: https:/