Bug 1329302 - Default min_command_interval is too low, results in nodes losing connectivity during introspection
Summary: Default min_command_interval is too low, results in nodes losing connectivity...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lucas Alvares Gomes
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 14:48 UTC by Ronelle Landy
Modified: 2016-11-10 15:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-10 15:48:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Dan Yocum 2016-04-21 15:05:06 UTC
The proper parameter to set is in /etc/ironic/ironic.conf:

[ipmi]
min_command_interval=10

Then restart the ironic services 'systemctl restart openstack-ironic*'

The puppet modules for ironic should put this parameter into the config file (with the default value) so the operator can modify it as they see fit.

Furthermore, I suggest that ALL parameters should be included in the ironic.conf file for operator reference.  The comments would be nice, too.

Comment 3 Lucas Alvares Gomes 2016-05-19 10:10:27 UTC
Hi Ronelle, Dan,

This varies depending on hardware and operators should adjust it according to what they have, unfortunately there's no perfect value that will work for everybody.

By default Ironic sets 5 seconds between each IPMI command (per BMC), which is already a lot in computing terms.

Comment 6 Dmitry Tantsur 2016-11-10 11:53:43 UTC
Hi! Is this still a problem? I don't think that bumping that ironic default is a way to go, but we can probably bump it via puppet for tripleo specifically.

Comment 7 Ronelle Landy 2016-11-10 15:36:09 UTC
Seems to be working now as far as the CI machines are concerned.

Comment 8 Dmitry Tantsur 2016-11-10 15:48:44 UTC
Thanks! I'm closing it for now. If somebody sees similar issues, we can reopen it and change the option via puppet.


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