I tried 1.5+bzr1977+2072+245~ppa0~ubuntu14.04.1 just now today and the
results were no different for the M610 or the R805.

For the M610 I had to power the system up manually or change the
username and password parameters in the UI to get the system to
commission, etc.   The logs don't show anything that jumps out on
systems that behave this way.   MAAS appears to be OK with the settings
it passes to the BMC.

Today, I found that I can run the ipmipower command manually with the
generated maas username and password and that works on the M610:

$ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --stat
10.0.0.39: off

$ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --on
10.0.0.39: ok

$ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --off
10.0.0.39: ok

..the Web UI, for some reason, when clicking 'commission node' or 'start
node' won't power up the machine unless I pass the username and password
that's already on the BMC (i.e. root/calvin).


For the R805, the same traceback occurs at enlistment time (which is no 
surprise given what Jason had said yesterday). 

I'll also try the version of maas that's in the main trusty repos that
Andres uploaded (1.5+bzr1977-0ubuntu3) to see if things are any
different.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in 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/maas/+bug/1287964/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to