[Ironic] Nova compute will fail to start if it can not talk to the Ironic API
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Medium
|
Lucas Alvares Gomes |
Bug Description
This can happen during an upgrade. The Ironic driver in nova will try to reach the Ironic API for a certain # of times and after that, if the API doesn't become available the whole service will stop with:
4210>: Failed to establish a new connection: [Errno 111] ECONNREFUSED',)). Attempt 60 of 61 from (pid=14540) wrapper /usr/local/
2017-03-24 10:28:48.703 ERROR ironicclient.
tail: HTTPConnectionP
bf50>: Failed to establish a new connection: [Errno 111] ECONNREFUSED',)). Attempt 61 of 61
2017-03-24 10:28:48.704 ERROR oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
2017-03-24 10:28:48.704 TRACE oslo_service.
ceeded with url: /v1/nodes/detail (Caused by NewConnectionEr
2017-03-24 10:28:48.704 TRACE oslo_service.
---
I don't believe that should be the right behavior. If the ironic nova driver tries to fetch the ndoes from the Ironic service but it's not available I think it should log the error and just return a list of empty nodes.
This happens in the get_available_
[UPDATE]
Apparently we had a similar bug in the past: https:/
Changed in nova: | |
assignee: | nobody → Lucas Alvares Gomes (lucasagomes) |
description: | updated |
tags: | added: ironic |
Changed in nova: | |
importance: | Undecided → Low |
importance: | Low → Medium |
Fix proposed to branch: master /review. openstack. org/449587
Review: https:/