After installing MAAS 3.3.0 on a test system, MAAS is unable to control nodes that use Intel AMT. The machines enlist fine, and as with previous versions of MAAS, the power type shows up as unknown in the web UI. After entering the correct power information (Intel AMT with the correct IP address and password), MAAS reports "power error." The maas.log file shows lines like the following:
2023-02-23T16:14:03.004779+00:00 vb2204t maas.power: [error] kzanol: Could not query power state: Failed to run command: ('amttool', '172.24.124.252', 'info') with error: Can't locate SOAP/Lite.pm in @INC (you may need to install the SOAP::Lite module) (@INC contains: /snap/maas/25850/usr/share/perl5 /snap/maas/25850/usr/share/perl/5.30 /snap/maas/25850/usr/lib/x86_64-linux-gnu/perl/5.30 /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.34.0 /usr/local/share/perl/5.34.0 /usr/lib/x86_64-linux-gnu/perl5/5.34 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.34 /usr/share/perl/5.34 /usr/local/lib/site_perl) at /snap/maas/25850/usr/bin/amttool line 4.#012BEGIN failed--compilation aborted at /snap/maas/25850/usr/bin/amttool line 4..
MAAS 3.2.6 worked fine with these same nodes that use AMT for power control.
I'm attaching all the MAAS log files from this test installation. Affected nodes are brennan (an Intel NUC) and kzanol (an HP ProBook 6470b).
This blocks us from migrating the Server and OEM labs to MAAS 3.3.0 as some OEMs do build and certify servers that use AMT as a management mechanism.