Here are the logs from a PowerEdge M610, which exhibits scenario #2. Scenario #2 seems to be the most common problem I've been having as of late. If you need logs from the commissioning phase on one of these I can try and grab those, too.
** Attachment added: "M610-cloud-init.tar.gz" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4007488/+files/M610-cloud-init.tar.gz ** Description changed: Beginning with MAAS 1.5+bzr1977-0ubuntu2 and up to today's daily builds (1.5+bzr1977+2064+245~ppa0~ubuntu14.04.1), maas no longer seems to either detect or properly configure the BMCs on Dell PowerEdge servers during enlistment. I've noticed two scenarios: 1) When the system enlists, the enlistment itself appears to work OK, but, when I look at the node in the MAAS WebUI, MAAS tells me that there is no power type set and that I need to set one. - - 2) The system enlists OK, and node's Power Parameters in the UI appear to be filled out fine. In other words, the correct Power driver is populated as well as the correct IP address for the BMC. I also have a 'maas' power user and generated password. However, if I click 'commission node' nothing happens (i.e. the node doesn't power on). + 2) The system enlists OK, and node's Power Parameters in the UI appear + to be filled out fine. In other words, the correct Power driver is + populated as well as the correct IP address for the BMC. I also have a + 'maas' power user and a pre-generated password. However, if I click + 'commission node' nothing happens (i.e. the node doesn't power on). Workarounds: - In scenario #1 if I go and fill out the IPMI information by hand for an - affected node, then commissioning, etc. works fine after that. + In scenario #1 if I go and fill out all of the IPMI information by hand + for an affected node, then commissioning, etc. works fine after that. In scenario #2 if I change the Power User and Power Password parameters - in the UI to what's already on the BMC (i.e. root/calvin), then - commissioning, etc. works fine after that. + in the UI from 'maas' and the pre-generated password to what's already + on the BMC (i.e. root/calvin), then commissioning, etc. works fine after + that. This is the first time in a while that PowerEdge didn't 'just work' with MAAS with regard to power settings. I know there has been some churn in the IPMI department lately for MAAS. I'll be attaching logs for each one of the PowerEdges affected by the respective scenarios. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
