detect_ipmi needs improvement. detects non-existant device in nested kvm

Bug #1064527 reported by Scott Moser on 2012-10-09
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
High
Andres Rodriguez
1.2
High
Julian Edwards
maas (Ubuntu)
High
Andres Rodriguez
Precise
High
Unassigned
Quantal
High
Andres Rodriguez
Raring
High
Andres Rodriguez

Bug Description

I attempted to enlist and then commission a kvm node.
kvm does not present ipmi devices.

http://paste.ubuntu.com/1269572/

Then, after that I tried simply
$ time sudo bmc-config --checkout --k
ey-pair="Lan_Conf:IP_Address"
Unable to get Number of Users

real 10m0.108s
user 2m34.858s
sys 0m48.795s

so a commissioning attempt of a node without ipmi will be delayed by 10 minutes.

[Impact]
This bug causes MAAS to try to detect IPMI on KVM Virtual Machines. This causes a long delay on the enlistment and commissioning process.

[Test Case]
1. Install MAAS
2. Enlist/Commission a machine.
(Without the fix, the machine will take 10+ minutes to enlist/commission. With the fix, it will do it within a couple of minutes)

[Regression Potential]
Minimal. This change simply checks whether the enlisting/commissioning machine is a virtual machine in KVM. If it is, it avoids the process of trying to detect IPMI.

Related branches

Scott Moser (smoser) wrote :

http://paste.ubuntu.com/1269612/

$ sudo ipmi-locate
sudo: unable to resolve host 192-168-77-5
Probing KCS device using DMIDECODE... FAILED

Probing SMIC device using DMIDECODE... FAILED

Probing BT device using DMIDECODE... FAILED

Probing SSIF device using DMIDECODE... FAILED

Probing KCS device using SMBIOS... FAILED

Probing SMIC device using SMBIOS... FAILED

Probing BT device using SMBIOS... FAILED

Probing SSIF device using SMBIOS... FAILED

Probing KCS device using ACPI... FAILED

Probing SMIC device using ACPI... FAILED

Probing BT device using ACPI... FAILED

Probing SSIF device using ACPI... FAILED

Probing KCS device using PCI... FAILED

Probing SMIC device using PCI... FAILED

Probing BT device using PCI... FAILED

Probing SSIF device using PCI... FAILED

KCS device default values:
IPMI Version: 1.5
IPMI locate driver: DEFAULT
IPMI interface: KCS
BMC driver device:
BMC I/O base address: 0xCA2
Register spacing: 1

SMIC device default values:
IPMI Version: 1.5
IPMI locate driver: DEFAULT
IPMI interface: SMIC
BMC driver device:
BMC I/O base address: 0xCA9
Register spacing: 1

BT device default values:
SSIF device default values:
IPMI Version: 1.5
IPMI locate driver: DEFAULT
IPMI interface: SSIF
BMC driver device: /dev/i2c-0
BMC SMBUS slave address: 0x42
Register spacing: 1

$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 2
model name : AMD Phenom(tm) 9550 Quad-Core Processor
stepping : 3
microcode : 0x1000065
cpu MHz : 2399.998
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb lm 3dnowext 3dnow up rep_good nopl extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch npt
bogomips : 4799.99
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:

summary: - ipmi detection takes 10 minutes if no ipmi present
+ detect_ipmi needs improvement. detects non-existant device in nested
+ kvm
Changed in maas:
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas:
milestone: none → 12.10
status: New → Triaged
importance: Undecided → High
Scott Moser (smoser) wrote :

there is some discussion of this at http://irclogs.ubuntu.com/2012/10/09/%23maas.html#t23:18 .
It seems that ' --disable-auto-probe' to bmc-info/config might be an option.

Changed in maas:
milestone: 12.10 → 12.10-stabilization
Changed in maas:
milestone: 12.10-stabilization → none
James Page (james-page) on 2012-11-15
Changed in maas (Ubuntu Precise):
status: New → Triaged
Changed in maas (Ubuntu Quantal):
status: New → Triaged
Changed in maas (Ubuntu Raring):
status: New → Triaged
Changed in maas (Ubuntu Precise):
importance: Undecided → High
Changed in maas (Ubuntu Quantal):
importance: Undecided → High
Changed in maas (Ubuntu Raring):
importance: Undecided → High
Changed in maas (Ubuntu Precise):
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas (Ubuntu Quantal):
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas (Ubuntu Raring):
assignee: nobody → Andres Rodriguez (andreserl)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.3+bzr1461+dfsg-0ubuntu1

---------------
maas (1.3+bzr1461+dfsg-0ubuntu1) raring; urgency=low

  * This is a new upstream bugfixs releases only. It includes:
    - Fix detection of non-existant ipmi device in nested kvm (LP: #1064527)
    - Fix IPMI User creation. (LP: #1119696)
    - Assign nodes to the correct nodegroup. (LP: #1148016)
    - Fix to provide useful error reporting for power management (LP: #1155175)

  [ Chris Van Hook ]
  * debian/patches/99-fix-ipmi-stat-lp1086160.patch: Fix ipmi power command
    to correctly use --stat. (LP: #1086160)

  [ Steve Langasek ]
  * Add missing dependency on iproute to maas-region-controller, for use of
    /sbin/ip in postinst.

  [ Andres Rodriguez ]
  * debian/patches/99-fix-maas-fpi.patch: Fix FPI, otherwise nodes have the
    risk of not being installed at all.
  * debian/control: Depends on apache2 for maas-cluster-controller
  * debian/maas-cluster-controller.install: Install maas-cluster-http.conf
  * debian/maas-cluster-controller.{postinst,postrm}: Handle symlink and
    removal of maas-cluster-http.conf.
 -- Andres Rodriguez <email address hidden> Wed, 20 Mar 2013 13:08:04 -0400

Changed in maas (Ubuntu Raring):
status: Triaged → Fix Released
Changed in maas:
status: Triaged → Fix Released
description: updated
Changed in maas (Ubuntu Precise):
status: Triaged → New
Changed in maas (Ubuntu Precise):
assignee: Andres Rodriguez (andreserl) → nobody

Hello Scott, or anyone else affected,

Accepted maas into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/maas/1.2+bzr1373+dfsg-0ubuntu1~12.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in maas (Ubuntu Precise):
status: New → Fix Committed
tags: added: verification-needed
tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.2+bzr1373+dfsg-0ubuntu1~12.04.2

---------------
maas (1.2+bzr1373+dfsg-0ubuntu1~12.04.2) precise-proposed; urgency=low

  * MAAS Stable Release Update, debian/patches:
    - 99_filestorage_empty_files_lp1204507.patch: Fix to allow the storage
      of empty files when using Juju Go, otherwise machines will fail to
      bootstrap. (LP: #1204507)
    - 99_fix_highbank_localboot_lp1172966.patch: Fix to PXE LOCALBOOT on
      highbank servers by removing a PXE message. Otherwise highbank will
      fail to pxe boot. (LP: #1172966)
    - 99_no_ipmi_detection_kvm_lp1064527.patch: Fix to ensure that IPMI
      detection does not happen on KVM VM's, otherwise enlistment and
      commissioning process will take too long. (LP: #1064527)
    - 99_update_cluster_info_cli_lp1172193.patch: Fix to allow admins to
      update cluster information from the API/CLI and not only restrict it
      to the WebUI. (LP: #1172193)
    - 99_fix_ipmi_power_command_lp1171418: Fix to ensure that ipmi commands
      are always executed regardless of the state of the machine.
      (LP: #1171418)
    - 99_default_timezone_utc_lp1211447.patch: Default to UTC for the
      deployed nodes. (LP: #1211447)
 -- Andres Rodriguez <email address hidden> Mon, 12 Aug 2013 12:18:34 -0400

Changed in maas (Ubuntu Precise):
status: Fix Committed → Fix Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in maas (Ubuntu Quantal):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints