I also manually tried using the ipmipower command in addition to
ipmitool:
ubuntu@critical-maas:~$ ipmipower -h 10.0.0.125 -u maas -p TRRnqoEl9ccQy7 --off
10.0.0.125: ok
ubuntu@critical-maas:~$ ipmipower -h 10.0.0.125 -u maas -p TRRnqoEl9ccQy7
--on-if-off --cycle
10.0.0.125: ok
both of these
Since apport didn't gather any maas logs, here they are...
** Attachment added: maas-logs.tar.gz
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+attachment/4031166/+files/maas-logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Also broken on at least two Dell PowerEdge servers: The R820 and R620.
I can also use the commands by hand and they work...but commissioning
via the web UI doesn't work at all.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Can you test that it works with this:
ipmipower -D LAN_2_0 -W opensesspriv -h 10.0.0.125 -u maas -p
TRRnqoEl9ccQy7 --on-if-off --cycle
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Same traceback in celery.log as well.
--
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/1294332
Title:
MAAS fails to manage power for system with Intel Integrated BMC
To manage
I saw similar issues at IBM on 10 March. Same look to the logs, same
success with ipmitool. After an apt-get upgrade on the 11th (trusty) and
a reboot, the issues did not appear for me. I did not refresh after the
11th, though.
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
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/1294332
I think this is bug 1293791
Please try the suggested patch: http://paste.ubuntu.com/7113619/
If it works, this can be marked as a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
I'm hitting the same problem at HP. During one maas bring up the SUT did
power on and off as I expected. Since that run it fails as desribed
above.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Jason, I commented those lines out in an earlier attempt to see if that
would fix things, but, my nodes still won't power up when clicking
commission node
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Kent - you may be hitting some other issue - Jeff reports that the patch
from bug 1293791 fixes it for him
--
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/1294332
Title:
MAAS fails to
Michael, please try the fix from bug 1293791.
--
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/1294332
Title:
MAAS fails to manage power for system with Intel Integrated BMC
To manage
*** This bug is a duplicate of bug 1293791 ***
https://bugs.launchpad.net/bugs/1293791
Ok. blanking out the lines completely via the patch in bug 1293791 did
the trick.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
*** This bug is a duplicate of bug 1293791 ***
https://bugs.launchpad.net/bugs/1293791
** This bug has been marked a duplicate of bug 1293791
ipmi template tries to apply ipmi to *hosts* address rather than ipmi address
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1293791 ***
https://bugs.launchpad.net/bugs/1293791
Please note that you can also work around this by adding the BMC's MAC
address in the power parameters. This a better solution if your BMC is
using DHCP.
--
You received this bug notification because you
15 matches
Mail list logo
