Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1515998 - On controller, container version of ironic.conf is populated but /etc/ironic/ironic.conf is used by ironic conductor
Summary: On controller, container version of ironic.conf is populated but /etc/ironic/...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: mlammon
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-21 19:04 UTC by Bob Fournier
Modified: 2017-11-27 14:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-11-27 14:04:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Bob Fournier 2017-11-21 19:04:27 UTC
Description of problem:

Testing out Ironic in the overcloud using OSP-12 container images from 20171011.  On the controller I was getting numerous errors related to Ironic conductor in ironic-conductor.log, e.g.
2017-11-21 17:43:20.987 453997 ERROR oslo.messaging._drivers.impl_rabbit [req-e2695f81-858b-4427-8a24-a99044b48a81 - - - - -] [ae23f55f-7536-4f68-ac0e-9376f5564f6f] AMQP server on is unreachable: [Errno 111] ECONNREFUSED. Trying again in 32 seconds. Client port: None: error: [Errno 111] ECONNREFUSED

We realized that ironic-conductor is using the conf file in /etc/ironic/ironic.conf but this file has not been populated correctly (we made changes to /etc/ironic/ironic.conf and saw they were picked up).

The ironic.conf that has been configured correctly is in ./var/lib/config-data/puppet-generated/ironic/etc/ironic/ironic.conf and likewise in the ironic.conf files under /var/lib/docker.

For reference, these are all the ironic.conf files on the controller.

I copied the file ./var/lib/config-data/puppet-generated/ironic/etc/ironic/ironic.conf to /etc/ironic/ironic.conf, restarted ironic, and all worked well.

[heat-admin@overcloud-controller-0 /]$ sudo systemctl restart openstack-ironic-conductor

(overcloud) [stack@host01 ~]$ ironic driver-list
| Supported driver(s) | Active host(s)                     |
| ipmi                | overcloud-controller-0.localdomain |
| pxe_drac            | overcloud-controller-0.localdomain |
| pxe_ilo             | overcloud-controller-0.localdomain |
| pxe_ipmitool        | overcloud-controller-0.localdomain |
| redfish             | overcloud-controller-0.localdomain |

Version-Release number of selected component (if applicable):

Container images from 20171011

How reproducible:

Every time

Steps to Reproduce:
Following Ironic in the overcloud deployment steps here -

Actual results:

ironic-conductor on the controller node has numerous errors.

Expected results:

No errors in ironic-conductor.log and ironic driver-list is populated correctly.

Additional info:

Comment 1 Bob Fournier 2017-11-27 14:04:33 UTC
Problem was with following the OSP-11 notes for Ironic in the overcloud which is different with containers in OSP-12.

In OSP-12 the file that should be edited to set the cleaning_network is

And to reset the ironic_conductor container, run the following:
sudo docker restart ironic_conductor

Note You need to log in before you can comment on or make changes to this bug.