MAAS

Series 1.7
Bug #1331214
Comment #35

Comment 35 for bug 1331214

Revision history for this message

Newell Jensen (newell-jensen) wrote on 2016-01-05: Re: [Bug 1331214] Re: MAAS (amttool) cannot control AMT version > 8

#35

Akash,

Ah, didn't catch that you had only commissioned the node. Thanks Mike!

On Mon, Jan 4, 2016 at 4:39 PM, Akash Chandrashekar <
<email address hidden>> wrote:

> Newell,
>
> I worked with mpontillo today, and figured out that I had completed a
> task in the 'wrong order of events' when setting up a node in MAAS.
> Apparently you cannot power on a node, after commisioning it and in
> "Ready" state. You have to deploy first.
>
> Once adding my ssh key, I was successfully able to deploy on :
> Hardware Tested : Intel NUC Model:NUC5i5MYHE with VPro extension running
> AMT Version: 10.0.45
> MAAS version : MAAS Version 1.9.0+bzr4533-0ubuntu1 (trusty1)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1331214
>
> Title:
> MAAS (amttool) cannot control AMT version > 8
>
> Status in MAAS:
> Fix Committed
> Status in MAAS 1.7 series:
> Fix Committed
> Status in maas package in Ubuntu:
> Fix Released
>
> Bug description:
> While testing Dell Poweredge T20, I noticed that MAAS will not power
> on/off the node even if you type in the AMT values. (see bug #1280486
> )
>
> amttool shows:
> test@test-Latitude-14-Rugged-Extreme-7404:~$ amttool 192.168.0.117 info
> soap_init: http://192.168.0.117:16992/NetworkAdministrationService
> http://schemas.intel.com/platform/client/NetworkAdministration/2004/01###
> AMT info on machine '192.168.0.117' ###
> AMT version: 9.0.1
> 404 Not Found at /usr/bin/amttool line 244.
> test@test-Latitude-14-Rugged-Extreme-7404:~$
>
> A little googling (for example, https://software.intel.com/en-
> us/blogs/2012/12/01/intel-amt-wsman-interface-is-replacing-the-
> soapeoi-interface ) shows that intel has probably removed amttool
> capability in version 9 of AMT, in favor of WSMAN capability.
>
> I also have several other AMT boxes here, with v 7, 8, and 4, and have
> verified that amttool (and MAAS) works OK on those boxes.
>
> To further check this, I ran some (attached) wsman scripts and
> verified that they did, indeed, power the box on and off.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1331214/+subscriptions
>

Akash,

Ah, didn't catch that you had only commissioned the node.  Thanks Mike!

On Mon, Jan 4, 2016 at 4:39 PM, Akash Chandrashekar <
akash.chandrashekar@canonical.com> wrote:

> Newell,
>
> I worked with mpontillo today, and figured out that I had completed a
> task in the 'wrong order of events' when setting up a node in MAAS.
> Apparently you cannot power on a node, after commisioning it and in
> "Ready" state. You have to deploy first.
>
> Once adding my ssh key, I was successfully able to deploy on  :
> Hardware Tested : Intel NUC Model:NUC5i5MYHE with VPro extension running
> AMT Version: 10.0.45
> MAAS version :  MAAS Version 1.9.0+bzr4533-0ubuntu1 (trusty1)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1331214
>
> Title:
>   MAAS (amttool) cannot control AMT version > 8
>
> Status in MAAS:
>   Fix Committed
> Status in MAAS 1.7 series:
>   Fix Committed
> Status in maas package in Ubuntu:
>   Fix Released
>
> Bug description:
>   While testing Dell Poweredge T20, I noticed that MAAS will not power
>   on/off the node even if you type in the AMT values.  (see bug #1280486
>   )
>
>   amttool shows:
>   test@test-Latitude-14-Rugged-Extreme-7404:~$ amttool 192.168.0.117 info
>   soap_init: http://192.168.0.117:16992/NetworkAdministrationService
> http://schemas.intel.com/platform/client/NetworkAdministration/2004/01###
> AMT info on machine '192.168.0.117' ###
>   AMT version:  9.0.1
>   404 Not Found at /usr/bin/amttool line 244.
>   test@test-Latitude-14-Rugged-Extreme-7404:~$
>
>   A little googling (for example, https://software.intel.com/en-
>   us/blogs/2012/12/01/intel-amt-wsman-interface-is-replacing-the-
>   soapeoi-interface ) shows that intel has probably removed amttool
>   capability in version 9 of AMT, in favor of WSMAN capability.
>
>   I also have several other AMT boxes here, with v 7, 8, and 4, and have
>   verified that amttool (and MAAS) works OK on those boxes.
>
>   To further check this, I ran some (attached) wsman scripts and
>   verified that they did, indeed, power the box on and off.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1331214/+subscriptions
>