Bug 1857217 - When ironic does IPMI retries, using 1 second timeout may be too short
Summary: When ironic does IPMI retries, using 1 second timeout may be too short
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z2
: 16.1 (Train on RHEL 8.2)
Assignee: RHOS Maint
QA Contact: Alistair Tonner
URL:
Whiteboard:
: 1861090 (view as bug list)
Depends On:
Blocks: 1861090
TreeView+ depends on / blocked
 
Reported: 2020-07-15 13:17 UTC by Bob Fournier
Modified: 2020-10-28 15:38 UTC (History)
4 users (show)

Fixed In Version: openstack-ironic-13.0.6-1.20200806013432.165c0ed.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1861090 (view as bug list)
Environment:
Last Closed: 2020-10-28 15:38:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack Storyboard 2007914 0 None None None 2020-07-15 13:17:36 UTC
OpenStack gerrit 740466 0 None MERGED Use min_command_interval when ironic does IPMI retries 2020-11-02 21:02:30 UTC
Red Hat Product Errata RHEA-2020:4284 0 None None None 2020-10-28 15:38:54 UTC

Description Bob Fournier 2020-07-15 13:17:37 UTC 
Description of problem:

For the workaround to ipmitool Cipher Suites issue [1] a change was made to Ironic so that Ironic did the IPMI retries by calling ipmitool for each retry, instead of letting ipmitool do the retry.  As part of this fix a min_command_interval of 1 was used.  This interval has been found to be too short for some BMCs and it results in IPMI failures. 

The fix should be to use the configured min_command_interval instead of 1.  

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1831893
Comment 8 Julia Kreger 2020-09-22 20:18:08 UTC 
*** Bug 1861090 has been marked as a duplicate of this bug. ***
Comment 11 Alistair Tonner 2020-10-15 15:52:35 UTC 
core puddle: RHOS-16.1-RHEL-8-20201005.n.0
openstack-ironic-common.noarch                 1:13.0.7-1.20200825103414.3d77e61.el8ost   @odcs-489304
openstack-ironic-conductor.noarch              1:13.0.7-1.20200825103414.3d77e61.el8ost   @odcs-489512
openstack-ironic-staging-drivers.noarch        0.12.1-0.20200526103911.b5a8aaf.el8ost     @odcs-489512
puppet-ironic.noarch                           15.4.1-1.20200814153354.39f97cc.el8ost     @odcs-489178
python3-ironic-inspector-client.noarch         3.7.1-0.20200522054325.3a41127.el8ost      @odcs-489304
python3-ironic-lib.noarch                      2.21.2-0.20200618093455.cc50dab.el8ost     @odcs-489304
python3-ironicclient.noarch                    3.1.2-0.20200522053422.1220d76.el8ost      @odcs-489198

Code verified in place on ironic-conductor instance

  Verified introspection succeeded and used modified timeout settings.
Comment 15 errata-xmlrpc 2020-10-28 15:38:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.1 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4284
Note You need to log in before you can comment on or make changes to this bug.