** Changed in: maas/1.7
Status: Fix Committed => Fix Released
** Changed in: maas
Status: Fix Committed => Fix Released
** Changed in: maas
Milestone: next => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
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.chandrashe...@canonical.com> wrote:
> Newell,
>
> I worked with mpontillo today, and figured out that I had completed a
> task in the 'wrong order of events'
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
Related is bug #1513198.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications about this bug go to:
https://bugs.launch
Akash,
You should file this as a new bug. Additionally, it would be
interesting to see if you could get this working in MAAS 1.10 or MAAS
trunk as that has the latest AMT power driver code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Update
Hardware Tested : Intel NUC Model:NUC5i5MYHE with VPro extension running AMT
Version: 10.0.45
MAAS Version : 1.8.3+bzr4053-0ubuntu1 (trusty1)
Unit properly can be commissioned in MAAS and is in ready state, however
"power on" function does not work.
--
You received this bug notificat
Tested with: Intel NUC Model:NUC5i5MYHE with VPro extension running AMT
Version: 10.0.45
To get this working properly with MAAS Version 1.8.3+bzr4053-0ubuntu1
(trusty1) , I had to also install the wsmancli package, which MAAS
appears to now take advantage of to properly control the device. This
This issue has been verified to work both on upgrade and fresh install,
and has been QA'd. Marking verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Hello Mark, or anyone else affected,
Accepted maas into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/maas/1.7.5+bzr3369-0ubuntu1~14.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
This bug was fixed in the package maas - 1.7.2+bzr3355-0ubuntu1
---
maas (1.7.2+bzr3355-0ubuntu1) vivid; urgency=medium
* New upstream release, 1.7.2 bzr3355:
- Support AMT Version > 8 (LP: #1331214)
- Fix call to amttool when restarting a node to not fail
disk erasing
** Branch linked: lp:ubuntu/vivid-proposed/maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications about this bug go
** Branch linked: lp:~maas-maintainers/maas/packaging.utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications about
** Changed in: maas/1.7
Assignee: Newell Jensen (newell-jensen) => Raphaël Badin (rvb)
** Changed in: maas/1.7
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
** Changed in: maas/1.7
Milestone: 1.7.2 => 1.7.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications about this b
** Branch linked: lp:~rvb/maas/amt_wsman-1.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications about this bug go to:
** 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/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications ab
Verified on several VPro machines in the Dell lab, with different AMT
firmware levels.
## PowerEdge T20 FW 9.0.21-build 1462works
## Laptop: E6400 FW 4.2.60-build 1060works
## Laptop: E6520 FW 7.1.4-build 1068works
## Laptop: E6430
** Changed in: maas (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications ab
Adding a task for Ubuntu to handle adding wsmancli to the Suggests line.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/133121
19 matches
Mail list logo
