** Description changed: 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 + Then, after that I tried simply $ time sudo bmc-config --checkout --k - ey-pair="Lan_Conf:IP_Address" + 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. - 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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064527 Title: detect_ipmi needs improvement. detects non-existant device in nested kvm To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1064527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
