tripleo-ci-centos-7-scenario002-multinode-oooq-container failing with timeout in deploy overcloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Arx Cruz |
Bug Description
Please, notice, this is not job timeout, it's the overcloud deploy timeout, that is set to 69 minutes according [1].
I notice some details:
1 - This is in stable/pike branch
2 - Some warnings in overcloud deploy command:
2018-01-04 23:32:43 | The disable_
2018-01-04 23:32:52 | Waiting for messages on queue '3c627656-
2018-01-04 23:33:13 | Configuration has 8 errors, fix them before proceeding. Ignoring these errors is likely to lead to a failed deploy.
2018-01-04 23:35:39 | Started Mistral Workflow tripleo.
2018-01-04 23:35:39 | {u'kernel_id': None, u'ramdisk_id': None, u'errors': [u"No image with the name 'bm-deploy-kernel' found - make sure you have uploaded boot images.", u"No image with the name 'bm-deploy-ramdisk' found - make sure you have uploaded boot images."], u'warnings': []}
2018-01-04 23:35:39 | {u'errors': [u'Error: There are no nodes in an available or active state and with maintenance mode off.'], u'warnings': []}
2018-01-04 23:35:39 | {u'errors': [u'Not enough baremetal nodes - available: 0, requested: 1'], u'result': {u'enough_nodes': False, u'statistics': {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_
3 - Errors:
2018-01-04 23:35:39 | ERRORS
2018-01-04 23:35:39 | [u"No image with the name 'bm-deploy-kernel' found - make sure you have uploaded boot images.", u"No image with the name 'bm-deploy-ramdisk' found - make sure you have uploaded boot images.", u'Error: There are no nodes in an available or active state and with maintenance mode off.', u'Not enough baremetal nodes - available: 0, requested: 1', u"No image with the name 'bm-deploy-kernel' found - make sure you have uploaded boot images.", u"No image with the name 'bm-deploy-ramdisk' found - make sure you have uploaded boot images.", u'Error: There are no nodes in an available or active state and with maintenance mode off.', u'Not enough baremetal nodes - available: 0, requested: 1']
After this, the deployment continues until get this error:
2018-01-05 00:44:35 | 2018-01-05 00:44:29Z [overcloud.
2018-01-05 00:44:35 | 2018-01-05 00:44:29Z [overcloud]: CREATE_FAILED Create timed out
2018-01-05 00:44:35 |
2018-01-05 00:44:35 | Stack overcloud CREATE_FAILED
2018-01-05 00:44:35 |
2018-01-05 00:44:35 | overcloud.
2018-01-05 00:44:35 | resource_type: OS::Heat:
2018-01-05 00:44:35 | physical_
2018-01-05 00:44:35 | status: CREATE_FAILED
2018-01-05 00:44:35 | status_reason: |
2018-01-05 00:44:35 | CREATE aborted
2018-01-05 00:44:35 | deploy_stdout: |
2018-01-05 00:44:35 | None
2018-01-05 00:44:35 | deploy_stderr: |
2018-01-05 00:44:35 | None
2018-01-05 00:44:35 | + status_code=1
IMHO, if the warning is already saying that we must fix the warnings otherwise the deployment will fail, it should actually not continue with the deployment
Changed in tripleo: | |
milestone: | rocky-3 → queens-3 |
Changed in tripleo: | |
status: | Triaged → Fix Released |
Just notice the same behavior in https:/ /logs.rdoprojec t.org/openstack -periodic/ periodic- tripleo- ci-centos- 7-multinode- 1ctlr-featurese t016-pike/ 1ef9e3f/ undercloud/ home/jenkins/ overcloud_ deploy. log.txt. gz