dmesg has a lot of apparmor denials when machines with AMT power type are used

[Vladimir Grevtsev]

[ 381.604439] audit: type=1400 audit(1614697733.546:299): apparmor="DENIED" operation="open" profile="snap.maas.supervisor" name="/etc/openwsman/openwsman_client.conf" pid=3815 comm="wsman" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 381.678728] audit: type=1400 audit(1614697733.622:300): apparmor="DENIED" operation="open" profile="snap.maas.supervisor" name="/etc/openwsman/openwsman_client.conf" pid=3820 comm="wsman" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 381.689950] audit: type=1400 audit(1614697733.634:301): apparmor="DENIED" operation="open" profile="snap.maas.supervisor" name="/etc/openwsman/openwsman_client.conf" pid=3820 comm="wsman" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Also, I've spotted one more (not AMT-related this time):

[ 381.732730] audit: type=1400 audit(1614697733.674:302): apparmor="DENIED" operation="open" profile="snap.maas.supervisor" name="/etc/ssh/ssh_config" pid=3823 comm="ssh" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

[Bill Wear (billwear)]

I can easily get these messages for most machine actions in MAAS. They do not seem to affect the operation of MAAS for me. Triaging, but with very low priority.

[Jerzy Husakowski (jhusakowski)]

MAAS power driver should not try to access the contents of the file mentioned in the logs as it is provided with connection parameters explicitly.