** Changed in: maas (Ubuntu)
Status: Fix Committed = Fix Released
--
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
** Changed in: maas (Ubuntu)
Status: Fix Committed = Fix Released
--
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
** Changed in: maas
Status: Fix Committed = Fix Released
--
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
** Changed in: maas
Status: Fix Committed = Fix Released
--
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
** Changed in: maas (Ubuntu)
Status: Confirmed = Fix Committed
--
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
** Changed in: maas (Ubuntu)
Status: Confirmed = Fix Committed
--
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
** Changed in: maas
Milestone: None = 14.04
--
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
** Changed in: maas
Milestone: None = 14.04
--
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
I read freeipmi's code to see what the workaround does - it's very
innocuous. It boils down to IPMI sessions being opened with the
privilege level required for the command being used, rather than the
maximum privilege level available for the user/ciphers available. For
ipmipower, freeipmi uses
** Branch linked: lp:~jason-hobbs/maas/opensesspriv-workaround-required-
lp-1287964
--
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
** Changed in: maas
Status: In Progress = Fix Committed
--
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
I read freeipmi's code to see what the workaround does - it's very
innocuous. It boils down to IPMI sessions being opened with the
privilege level required for the command being used, rather than the
maximum privilege level available for the user/ciphers available. For
ipmipower, freeipmi uses
** Branch linked: lp:~jason-hobbs/maas/opensesspriv-workaround-required-
lp-1287964
--
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
** Changed in: maas
Status: In Progress = Fix Committed
--
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
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
Also tested with a freshly-installed maas server using
1.5+bzr1977-0ubuntu3 on Trusty.
I am also seeing the same symptoms as originally reported. The power
settings fail to get configured for the R805 and the M610 also displays
the same behaviors as listed in the previous comment.
I will also
I have one machine that actually gets set up correctly so far. The
PowerEdge T410 is the system.
After enlistment, MAAS assigns the maas username and password and sets
the driver type to IPMI 2.0. On this system, I can actually click
commission node and it powers on without issues via the Web
The PowerEdge R620 also works fine with regard to enlisting and
commissioning. At the end of enlistment it's also set to IPMI 2.0 and I
can power it up from the WebUI.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
For the M610 using version 1.5+bzr1977-0ubuntu3 I think I found a reason
why it refused to power up via the UI after enlistment.
At enlistment time, the Power Driver settings for that BMC are
improperly being identified as IPMI 2.0, when they should be IPMI 1.5.
If I go and set the IPMI Power
PowerEdge R710 also works fine with the IPMI driver defaulted to 2.0
after enlistment.
--
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
MAAS should only be setting the BMCs to 2.0 if the BMC claims it has 2.0
support. IPMI settings are updated after commissioning based on what
settings are changed/discovered in commissioning - see lp #1287828.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Kent,
Can you please get the output of the bmc-info command, from freeipmi-
utils, for one of the BMCs that isn't working?
You can run it remotely like this:
bmc-info -h 192.168.12.34 -u xxx -p xxx
Or locally like this:
bmc-info
--
You received this bug notification because you are a member
Here you go. Attaching output from M610 and M915. Both are blades
sitting in the same chassis. Each server has its own dedicated BMC and
both look to be advertising IPMI 2.0. However, unless I select auto-
detect or IPMI 1.5 from the UI, the systems will not power up when
selecting 'commission
** Attachment added: M915.txt
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4008944/+files/M915.txt
--
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
Kent,
This looks like bug 1288297. Can you try this:
sudo ipmipower -W opensesspriv -D LAN_2_0 -h 10.0.0.39 -u maas -p
Hg6awJQtZ --on
Thanks,
Jason
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Ok. WIth the addition of the -W opensesspriv parameter to the command
for that blade I finally get a sane status back from the BMC. On the
node in question I can run --stat, --on, or --off and all three commands
now work when they didn't before.
--
You received this bug notification because you
If you're blocked by this issue, you can workaround it by editing
/etc/maas/templates/power/ipmi.template to add use of -W opensesspriv.
I've tested this on a handful of systems that don't require the
workaround and it seems to work fine everywhere so far.
=== modified file
Same here. I just tested on a machine that didn't need the parameter
and didn't seem to have a negative impact.
I will leverage this workaround until you guys decide the final fix /
resolution. I'll let you know if there are any negative side effects
along the way.
Thanks!
--
You received
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
Also tested with a freshly-installed maas server using
1.5+bzr1977-0ubuntu3 on Trusty.
I am also seeing the same symptoms as originally reported. The power
settings fail to get configured for the R805 and the M610 also displays
the same behaviors as listed in the previous comment.
I will also
I have one machine that actually gets set up correctly so far. The
PowerEdge T410 is the system.
After enlistment, MAAS assigns the maas username and password and sets
the driver type to IPMI 2.0. On this system, I can actually click
commission node and it powers on without issues via the Web
The PowerEdge R620 also works fine with regard to enlisting and
commissioning. At the end of enlistment it's also set to IPMI 2.0 and I
can power it up from the WebUI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For the M610 using version 1.5+bzr1977-0ubuntu3 I think I found a reason
why it refused to power up via the UI after enlistment.
At enlistment time, the Power Driver settings for that BMC are
improperly being identified as IPMI 2.0, when they should be IPMI 1.5.
If I go and set the IPMI Power
PowerEdge R710 also works fine with the IPMI driver defaulted to 2.0
after enlistment.
--
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
MAAS should only be setting the BMCs to 2.0 if the BMC claims it has 2.0
support. IPMI settings are updated after commissioning based on what
settings are changed/discovered in commissioning - see lp #1287828.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Kent,
Can you please get the output of the bmc-info command, from freeipmi-
utils, for one of the BMCs that isn't working?
You can run it remotely like this:
bmc-info -h 192.168.12.34 -u xxx -p xxx
Or locally like this:
bmc-info
--
You received this bug notification because you are a member
** Attachment added: M915.txt
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4008944/+files/M915.txt
--
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
Here you go. Attaching output from M610 and M915. Both are blades
sitting in the same chassis. Each server has its own dedicated BMC and
both look to be advertising IPMI 2.0. However, unless I select auto-
detect or IPMI 1.5 from the UI, the systems will not power up when
selecting 'commission
Kent,
This looks like bug 1288297. Can you try this:
sudo ipmipower -W opensesspriv -D LAN_2_0 -h 10.0.0.39 -u maas -p
Hg6awJQtZ --on
Thanks,
Jason
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok. WIth the addition of the -W opensesspriv parameter to the command
for that blade I finally get a sane status back from the BMC. On the
node in question I can run --stat, --on, or --off and all three commands
now work when they didn't before.
--
You received this bug notification because you
If you're blocked by this issue, you can workaround it by editing
/etc/maas/templates/power/ipmi.template to add use of -W opensesspriv.
I've tested this on a handful of systems that don't require the
workaround and it seems to work fine everywhere so far.
=== modified file
Same here. I just tested on a machine that didn't need the parameter
and didn't seem to have a negative impact.
I will leverage this workaround until you guys decide the final fix /
resolution. I'll let you know if there are any negative side effects
along the way.
Thanks!
--
You received
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
I'm attaching the cloud-init logs from a PowerEdge R805, which exhibits
scenario #1.
** Attachment added: R805-cloud-init.tar.gz
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4007487/+files/R805-cloud-init.tar.gz
--
You received this bug notification because you
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jason Hobbs (jason-hobbs)
--
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
I see this on the cloud-init-output.log for the R805:
Traceback (most recent call last):
File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 309, in module
main()
File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 276, in main
apply_ipmi_user_settings(user_settings)
File
Please do not file project bugs on the source package, use the maas
project instead.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: In Progress = Invalid
** Changed in: maas
Status: New = In Progress
** Changed in: maas
** Tags added: server-hwe
--
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
This bug also affects the source package, so updating accordingly.
** Changed in: maas (Ubuntu)
Status: Invalid = 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/1287964
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
I'm attaching the cloud-init logs from a PowerEdge R805, which exhibits
scenario #1.
** Attachment added: R805-cloud-init.tar.gz
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4007487/+files/R805-cloud-init.tar.gz
--
You received this bug notification because you
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Jason Hobbs (jason-hobbs)
--
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
I see this on the cloud-init-output.log for the R805:
Traceback (most recent call last):
File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 309, in module
main()
File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 276, in main
apply_ipmi_user_settings(user_settings)
File
Please do not file project bugs on the source package, use the maas
project instead.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: In Progress = Invalid
** Changed in: maas
Status: New = In Progress
** Changed in: maas
** Tags added: server-hwe
--
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 also affects the source package, so updating accordingly.
** Changed in: maas (Ubuntu)
Status: Invalid = Confirmed
--
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
56 matches
Mail list logo
