Red Hat Bugzilla – Bug 1289046
Deployment failed: Went to status ERROR due to "Message: Unknown, Code: Unknown"
Last modified: 2016-09-13 12:23:18 EDT
Description of problem:
The complete message in the UI:
ERROR: deployment failed with status: CREATE_FAILED and reason: Resource CREATE failed: ResourceInError: resources.Compute.resources.resources.NovaCompute: Went to status ERROR due to "Message: Unknown, Code: Unknown"
This happened in 26.0% of the RHELOSP deployment. Content synced successfully. This is my third re-deploy of RHELOSP, I have previously un-deployed the overcloud from the Director webUI, so it could be created again. I did not delete nodes, I'm using nodes discovered during the first RHELOSP deployment.
From the nova-compute.log:
Command: qemu-img convert -O raw /var/lib/ironic/master_images/tmpHrdQaf/ed45a705-e8cd-4b7f-84fd-62d50de7c1f8.part /var/lib/ironic/master_images/tmpHrdQaf/ed45a705-e8cd-4b7f-84fd-62d50de7c1f8.converted
Exit code: 1
Stderr: u'qemu-img: error while reading sector 715008: Input/output error\n'
NeutronClientException: 404 Not Found
The resource could not be found.
Please see attached production.log and nova-compute.log excerpts.
I tried to resume the failing tasks and got:
There was a conflict when trying to complete your request. The Stack (overcloud) already exists.
Version-Release number of selected component (if applicable):
Happened to me once
Steps to Reproduce:
1. Do a RHELOSP re-deployment with previously discovered nodes and previously undeployed Overcloud
2. Deployment fails at 26.0% with above error
Deployment fails; upon resuming the failing task, another error appears; unable to continue deployment
Deployment completes successfully
Reproduced while doing another RHELOSP re-deployment.
With QCI-1.2-RHEL-7-20160723.t.0 and QCIOOO-8.0-RHEL-7-20160719.t.0, have done multiple redeploys successfully.
Marking as VERIFIED, please reopen if this reoccurs
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.