Project

General

Profile

Bug #20977

With wrong IPMI password, calling /bmc/X.X.X.X/lan/ip endpoint causes smart-proxy to stuck in infinite loop

Added by Mateusz Gozdek almost 5 years ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
BMC
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

There is an upstream bug in rubyipmi gem, which is causing this infinite loop, however all errors printed by this gem are logged into log files when DEBUG loglevel is enabled. Additionally, number of system interrupts jumps drastically, as it is spawning new ipmitool processes all the time.

Upstream bugfix: https://github.com/logicminds/rubyipmi/pull/48

When this is merged, rubyipmi dependency should be updated to use it. In the meanwhile, some workaround can be applied in my opinion.

History

#1 Updated by Dmitri Dolguikh almost 5 years ago

The upstream change has been merged and will be available as soon as a new version of the gem is released. I don't think we need to add a workaround for this.

#2 Updated by Nacho Barrientos 9 months ago

4 years later people will still hit this bug as there hasn't been any release containing the patch mentioned above (the version shipped by Foreman 3.0 is rubygem-rubyipmi-0.10.0-7.el8.noarch). IMO this situation should be covered on the Foreman-proxy side with, at least, documentation.

#4 Updated by Ewoud Kohl van Wijngaarden 9 months ago

A new release was requested in July (https://github.com/logicminds/rubyipmi/issues/50) but so far nothing. I wonder if we need to work around this in our packaging. Apply the patches there.

Also available in: Atom PDF