| 2014-03-31 22:05:16 |
Mike Rushton |
bug |
|
|
added bug |
| 2014-03-31 22:05:16 |
Mike Rushton |
attachment added |
|
cloud-init.log https://bugs.launchpad.net/bugs/1300476/+attachment/4056647/+files/cloud-init.log |
|
| 2014-03-31 22:05:37 |
Mike Rushton |
attachment added |
|
cloud-init-output.log https://bugs.launchpad.net/maas/+bug/1300476/+attachment/4056648/+files/cloud-init-output.log |
|
| 2014-03-31 22:05:52 |
Mike Rushton |
attachment added |
|
boot.log https://bugs.launchpad.net/maas/+bug/1300476/+attachment/4056649/+files/boot.log |
|
| 2014-03-31 22:06:25 |
Mike Rushton |
attachment added |
|
lspci.txt https://bugs.launchpad.net/maas/+bug/1300476/+attachment/4056650/+files/lspci.txt |
|
| 2014-03-31 22:06:40 |
Mike Rushton |
attachment added |
|
lshw.txt https://bugs.launchpad.net/maas/+bug/1300476/+attachment/4056651/+files/lshw.txt |
|
| 2014-03-31 22:07:01 |
Mike Rushton |
attachment added |
|
cpuinfo.txt https://bugs.launchpad.net/maas/+bug/1300476/+attachment/4056652/+files/cpuinfo.txt |
|
| 2014-03-31 22:07:22 |
Mike Rushton |
attachment added |
|
ipmi-lan-print.txt https://bugs.launchpad.net/maas/+bug/1300476/+attachment/4056653/+files/ipmi-lan-print.txt |
|
| 2014-03-31 22:07:43 |
Mike Rushton |
bug |
|
|
added subscriber Paul |
| 2014-03-31 22:09:35 |
Mike Rushton |
bug |
|
|
added subscriber Samantha Jian-Pielak |
| 2014-03-31 22:09:55 |
Mike Rushton |
bug |
|
|
added subscriber Roderick Smith |
| 2014-03-31 22:13:35 |
Mike Rushton |
description |
On MAAS 1.5+bzr1977-0ubuntu5 enlisting nodes fails to detect the BMC power type and therefore not able to create a user to control the BMC.
This is for a Cisco B200 M3 server running UCSM to control the BMC.
Running ipmitool manually on an ephemeral image or manual installation of Ubuntu 12.04.4 or 14.04 fails when trying the following:
ipmitool user list
Get User Access command failed (channel 14, user 1): Invalid command
ipmitool user set name 10 maas
Set User Name command failed (user 10, name maas): Invalid command
Running ipmitool against the system event log(sel), chassis status or lan print all work fine.
Cisco mentions that controlling ipmi directly is disabled by default as well as behind a firewall that is disabled. Going through hardware enablement for UCSM might be the better choice. |
On MAAS 1.5+bzr1977-0ubuntu5 enlisting nodes fails to detect the BMC power type and therefore not able to create a user to control the BMC.
Steps to reproduce:
1. power on the node.
2. Check node settings on MaaS Web GUI.
Expected result:
1. Node shows up on MaaS Web GUI.
2. The power type is set to IPMI.
Actual results:
2. Power type is not set.
This is for a Cisco B200 M3 server running UCSM to control the BMC.
Running ipmitool manually on an ephemeral image or manual installation of Ubuntu 12.04.4 or 14.04 fails when trying the following:
ipmitool user list
Get User Access command failed (channel 14, user 1): Invalid command
ipmitool user set name 10 maas
Set User Name command failed (user 10, name maas): Invalid command
Running ipmitool against the system event log(sel), chassis status or lan print all work fine.
Cisco mentions that controlling ipmi directly is disabled by default as well as behind a firewall that is disabled. Going through hardware enablement for UCSM might be the better choice. |
|
| 2014-04-01 00:04:27 |
Julian Edwards |
maas: status |
New |
Incomplete |
|
| 2014-04-02 02:15:05 |
Julian Edwards |
maas: status |
Incomplete |
Triaged |
|
| 2014-04-02 02:15:15 |
Julian Edwards |
maas: importance |
Undecided |
Medium |
|
| 2014-04-02 02:15:23 |
Julian Edwards |
tags |
blocks-hwcert-server |
blocks-hwcert-server hwe |
|
| 2014-04-04 00:05:04 |
Andres Rodriguez |
tags |
blocks-hwcert-server hwe |
blocks-hwcert-server hwe server-hwe |
|
| 2014-04-04 00:05:45 |
Andres Rodriguez |
tags |
blocks-hwcert-server hwe server-hwe |
blocks-hwcert-server server-hwe |
|
| 2014-04-04 00:06:57 |
Andres Rodriguez |
maas: assignee |
|
Andres Rodriguez (andreserl) |
|
| 2014-04-04 00:21:54 |
Andres Rodriguez |
maas: assignee |
Andres Rodriguez (andreserl) |
Jason Hobbs (jason-hobbs) |
|
| 2014-04-21 21:56:47 |
Jason Hobbs |
branch linked |
|
lp:~jason-hobbs/maas/ucs-xml-api |
|
| 2014-04-21 22:00:04 |
Jason Hobbs |
maas: status |
Triaged |
In Progress |
|
| 2014-05-08 06:34:07 |
Julian Edwards |
maas: status |
In Progress |
Fix Committed |
|
| 2014-05-08 06:34:08 |
Julian Edwards |
maas: milestone |
|
14.10 |
|
| 2014-05-08 16:50:50 |
Andres Rodriguez |
bug task added |
|
maas (Ubuntu) |
|
| 2014-05-08 16:57:44 |
Andres Rodriguez |
maas (Ubuntu): importance |
Undecided |
Critical |
|
| 2014-05-08 17:08:09 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-proposed |
|
| 2014-05-08 17:17:02 |
Andres Rodriguez |
description |
On MAAS 1.5+bzr1977-0ubuntu5 enlisting nodes fails to detect the BMC power type and therefore not able to create a user to control the BMC.
Steps to reproduce:
1. power on the node.
2. Check node settings on MaaS Web GUI.
Expected result:
1. Node shows up on MaaS Web GUI.
2. The power type is set to IPMI.
Actual results:
2. Power type is not set.
This is for a Cisco B200 M3 server running UCSM to control the BMC.
Running ipmitool manually on an ephemeral image or manual installation of Ubuntu 12.04.4 or 14.04 fails when trying the following:
ipmitool user list
Get User Access command failed (channel 14, user 1): Invalid command
ipmitool user set name 10 maas
Set User Name command failed (user 10, name maas): Invalid command
Running ipmitool against the system event log(sel), chassis status or lan print all work fine.
Cisco mentions that controlling ipmi directly is disabled by default as well as behind a firewall that is disabled. Going through hardware enablement for UCSM might be the better choice. |
[Test Case]
Without the Fix:
1. Install MAAS
2. Power on Cisco B Series Nodes to boot from MAAS.
3. Nodes won't have Power Management set. MAAS won't be able to control.
With the Fix:
2. Add Cisco B Series nodes to MAAS:
maas <user> node-group probe-and-enlist-ucsm <cluster_uuid> url=<UCS BMC location, ie. https://10.20.30.5/> username=<bmc user> password=<bmc password>
3. Check that all nodes are added and with power parameters set.
On MAAS 1.5+bzr1977-0ubuntu5 enlisting nodes fails to detect the BMC power type and therefore not able to create a user to control the BMC.
Steps to reproduce:
1. power on the node.
2. Check node settings on MaaS Web GUI.
Expected result:
1. Node shows up on MaaS Web GUI.
2. The power type is set to IPMI.
Actual results:
2. Power type is not set.
This is for a Cisco B200 M3 server running UCSM to control the BMC.
Running ipmitool manually on an ephemeral image or manual installation of Ubuntu 12.04.4 or 14.04 fails when trying the following:
ipmitool user list
Get User Access command failed (channel 14, user 1): Invalid command
ipmitool user set name 10 maas
Set User Name command failed (user 10, name maas): Invalid command
Running ipmitool against the system event log(sel), chassis status or lan print all work fine.
Cisco mentions that controlling ipmi directly is disabled by default as well as behind a firewall that is disabled. Going through hardware enablement for UCSM might be the better choice. |
|
| 2014-05-08 17:18:07 |
Launchpad Janitor |
maas (Ubuntu): status |
New |
Fix Released |
|
| 2014-05-09 02:14:22 |
Julian Edwards |
nominated for series |
|
maas/1.5 |
|
| 2014-05-09 02:14:22 |
Julian Edwards |
bug task added |
|
maas/1.5 |
|
| 2014-05-09 02:14:28 |
Julian Edwards |
maas: milestone |
14.10 |
|
|
| 2014-05-09 02:14:30 |
Julian Edwards |
maas/1.5: milestone |
|
1.5.1 |
|
| 2014-05-09 02:14:33 |
Julian Edwards |
maas/1.5: status |
New |
Fix Committed |
|
| 2014-05-09 02:14:35 |
Julian Edwards |
maas/1.5: importance |
Undecided |
Medium |
|
| 2014-05-09 02:14:43 |
Julian Edwards |
maas/1.5: assignee |
|
Jason Hobbs (jason-hobbs) |
|
| 2014-05-09 02:15:29 |
Julian Edwards |
branch linked |
|
lp:~jason-hobbs/maas/ucs-xml-api-1.5 |
|
| 2014-05-09 02:49:30 |
Julian Edwards |
maas/1.5: status |
Fix Committed |
Fix Released |
|
| 2014-05-09 02:49:32 |
Julian Edwards |
maas: status |
Fix Committed |
Fix Released |
|
| 2014-05-09 19:36:26 |
Chris J Arges |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-05-09 19:36:26 |
Chris J Arges |
bug task added |
|
maas (Ubuntu Trusty) |
|
| 2014-05-11 03:19:35 |
Chris J Arges |
maas (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2014-05-11 03:19:38 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-05-11 03:19:43 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2014-05-11 03:19:51 |
Chris J Arges |
tags |
blocks-hwcert-server server-hwe |
blocks-hwcert-server server-hwe verification-needed |
|
| 2014-05-11 03:41:39 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/maas |
|
| 2014-05-11 05:08:41 |
Mike Rushton |
tags |
blocks-hwcert-server server-hwe verification-needed |
blocks-hwcert-server server-hwe verification-done |
|
| 2014-05-21 20:43:08 |
Launchpad Janitor |
maas (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2014-05-21 20:43:40 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2014-07-03 09:11:08 |
Lei Wang |
bug |
|
|
added subscriber Ray Wang |
