Bug 1251559
Summary: | overcloud deploy fails due to ResourceUnknownStatus | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Adriano Petrich <apetrich> | ||||
Component: | rhosp-director | Assignee: | chris alfonso <calfonso> | ||||
Status: | CLOSED NOTABUG | QA Contact: | yeylon <yeylon> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | Director | CC: | apetrich, hbrock, mburns, rhel-osp-director-maint, sbaker, shardy, srevivo, yeylon | ||||
Target Milestone: | --- | Keywords: | Automation, ZStream | ||||
Target Release: | Director | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-08-18 19:29:28 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Adriano Petrich
2015-08-07 17:09:37 UTC
a heat event-list overcloud shows these errors | CephStorageNodesPostDeployment | e9507fe2-9e6b-46ca-bb22-d1cbae59a508 | ResourceUnknownStatus: Resource failed - Unknown status FAILED due to "Resource CREATE failed: ResourceUnknownStatus: Resource failed - Unknown status FAILED due to "Resource CREATE failed: Error: Deployment to server failed: deploy_status_code : Deployme | CREATE_FAILED | 2015-08-07T14:49:44Z | 14:50:11 | overcloud | f0ca3117-cce5-4cc1-affc-af51ab89118a | Resource CREATE failed: ResourceUnknownStatus: Resource failed - Unknown status FAILED due to "Resource CREATE failed: ResourceUnknownStatus: Resource failed - Unknown status FAILED due to "Resource CREATE failed: Error: Deployment to server failed: deplo | CREATE_FAILED | 2015-08-07T14:49:45Z | 'UnknownStatus' is a red herring here (and the error message will be improved in a future release) - the status in question is CREATE_FAILED and is quite well-known. The reason for the failure is to be found at the end, not the beginning: "Deployment exited with non-zero status code: 6" Since we know that Puppet routinely exits with the status code 6, we can surmise that the SoftwareDeployment that failed was almost certainly one running Puppet and you've confirmed that it was in fact CephStorageNodesPostDeployment. You'd need to look into the puppet logs for CephStorageNodesPostDeployment to find the actual cause. Adriano, were you able to get any more info from your deployment based upon Comment 4? Chris I'm closing this bug as it stopped happening. |