Project

General

Profile

Bug #6748

problem with BMC access

Added by Pablo Escobar over 7 years ago. Updated over 7 years ago.

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

Description

Hi

I have installed foreman in centos6.5

[root@ccc ~]# rpm -qa |grep -i foreman
foreman-postgresql-1.5.1-2.el6.noarch
foreman-release-1.5.1-2.el6.noarch
ruby193-rubygem-foreman_bootdisk-2.0.8-1.el6.noarch
ruby193-rubygem-foreman_setup-2.0.3-1.el6.noarch
foreman-installer-1.5.1-1.el6.noarch
rubygem-foreman_api-0.1.11-1.el6.noarch
foreman-proxy-1.5.1-1.el6.noarch
foreman-1.5.1-2.el6.noarch

I have foreman and foreman-proxy installed in the same machine. In the same machine I have bind and dhpc running. The proxy seems to run fine, I can add hosts in the foreman webui and the right entries are created in bind and dhcp for both interfaces (eth and BMC). The machine has two network interfaces, one in the range of the machines and another interface in the range of BMC. To achieve this I had to manually add a new zone to /etc/zones.conf and also manually edit /etc/dhcpd.conf to add a second range for BMC.

eth0 Link encap:Ethernet HWaddr 82:6F:00:95:66:8F
inet addr:10.1.25.3 Bcast:10.1.127.255 Mask:255.255.128.0
inet6 addr: fe80::806f:ff:fe95:668f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2956637 errors:0 dropped:0 overruns:0 frame:0
TX packets:1162 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:277826691 (264.9 MiB) TX bytes:172525 (168.4 KiB)
Interrupt:18

eth0:0 Link encap:Ethernet HWaddr 82:6F:00:95:66:8F
inet addr:10.1.153.3 Bcast:10.1.255.255 Mask:255.255.128.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:18

I have configured the proxy to use bmc and in the webui I see that foreman-proxy has the BMC feature enabled.

[root@ccc network-scripts]# grep -i bmc /etc/foreman-proxy/settings.yml
  1. enable BMC management (Bare metal power and bios controls)
    :bmc: true
    :bmc_default_provider: ipmitool

I have the required packages installed in the machine

[root@ccc network-scripts]# rpm -qa|grep ipmi
rubygem-rubyipmi-0.7.0-1.el6.noarch
ipmitool-1.8.11-16.el6.x86_64

And using the cli in the same machine I can do "ipmitool power status" and it works.

But when I go to "hosts >> all hosts >> machine name" in the foreman webui I get this error in /var/log/foreman/production.log
https://gist.github.com/pescobar/82dee53aae3d1c7804b2

The machine name is ufe01 (the main ethernet interface) but the BMC interface has the hostname ufe01a (not sure if this can be related)

Then if I click in the BMC tab for this machine I get this message:

Failure: undefined method `downcase' for nil:NilClass

History

#1 Updated by Dominic Cleal over 7 years ago

  • Category set to BMC

Perhaps also check /var/log/foreman-proxy/proxy.log on the BMC proxy in case an error is given there?

#2 Updated by Pablo Escobar over 7 years ago

Hi

I have enabled debug in the proxy log.

@[root@ccc network-scripts]# grep -i log /etc/foreman-proxy/settings.yml
  1. Where our proxy log files are stored
    :log_file: /var/log/foreman-proxy/proxy.log
    :log_level: DEBUG@

this is what I get in the proxy.log file when adding the BMC interface to this machine (notice the name is ufe01a) (ufe01 >> main ethernet) (ufe01a >> bmc interface)
https://gist.github.com/pescobar/cf037f9bd2126a2e61c5

But when using the webui I access all machines >> machine >> BMC (and I get the message "Failure: undefined method `downcase' for nil:NilClass") nothing new appears in the proxy.log

#3 Updated by Pablo Escobar over 7 years ago

btw, I also tried to replace the interface "eth0:0" with a new interface "eth2" with the same ip in case this was causing any problem (eth0:0 is the interface in the BMC network). After enabling eth2 I can reach the BMC from the cli:

[root@ccc foreman-proxy]# ipmitool -H ufe01a -U ***** -P ******* power status
Chassis Power is on

but still getting the same error when using the webui

#4 Updated by Pablo Escobar over 7 years ago

I have just tried to add another machine (different hardware) and this one works fine with BMC, so the problem seems related only to this specific hardware.

But I don't know how to debug where the problem can be. Any clue about where to look or how to debug? I supposed that if "ipmitool power status" on command line works it should also work from foreman.

#5 Updated by Pablo Escobar over 7 years ago

Hi

after doing some testing I tried to add a new user to my BMC/ipmi interface and now it works :?

The only difference is that in the previous user I was using a password which was a 20 characters string (with numbers and capitals) and now I used a eight characters string.

does it makes any sense?

#6 Updated by Lukas Zapletal over 7 years ago

  • Status changed from New to Rejected

Glad to read that, I don't know. Try to reproduce it again with 20 characters password?

#7 Updated by Pablo Escobar over 7 years ago

Hi

I have just edited the host to change the BMC user/pass and again the foreman web interface fails to access BMC. Both accounts works when using ipmitool on command line.

it seems that somehow foreman has a problem with long BMC passwords.

Also available in: Atom PDF