Bug 1253693
| Summary: | Ironic deployment hangs after copying image | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ben Nemec <bnemec> | ||||
| Component: | openstack-ironic | Assignee: | Lucas Alvares Gomes <lmartins> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Toure Dunnon <tdunnon> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | Director | CC: | bschmaus, dtantsur, srevivo | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | 7.0 (Kilo) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-11-10 11:38:50 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: |
|
||||||
Hi! The bug seems to related to the old bash ramdisk, which we unfortunately cannot fix too much. I think it should be gone with switch to IPA. |
Created attachment 1063029 [details] ironic conductor logs from failed deployment Description of problem: On an HA deployment (3 controllers, 1 compute), twice in a row one of the controller nodes failed to deploy properly. Looking through the ironic logs, it appears the node may have been locked when the image copy completed, so ironic failed to send the completion notification and the node just sat at the nc command until it was rebooted. Version-Release number of selected component (if applicable): 2015.1.0-9 How reproducible: Intermittent, but not frequent Steps to Reproduce: 1. Deploy servers via ironic 2. 3. Actual results: One or more may hang waiting for the completion message from ironic Expected results: All servers deployed successfully Additional info: Manually rebooting the server seems to often get around this problem because it re-runs the deployment and the completion signal gets sent successfully. For grep purposes, the node id that hung was 2efd7fea-e163-48d8-8a9f-fc1c72bc3147