AppArmor permission issues - Is it okay to diable apparmor?

Asked by John Barbee

I am still yet to successfully build a MAAS server, deploy nodes, and charms with 12.04 LTS. I my latest troubleshooting in my logs I have found several errors in my syslog pertaining the permissions with apparmor. Everytime I would fix one, another would show up. I finally decided to disable apparmor with the following command:

$ln -s /etc/apparmor.d/usr.bin.cobblerd /etc/apparmor.d/disable/
$apparmor_parser -R /etc/apparmor.d/usr.bin.cobblerd

Do you see any problems with doing this? After apparmor was disabled, I was able to successfully run 'sudo cobbler check' and got a message back saying 'All systems go.'

I am now on rebuild #6 or #7. Any recommendations? Do you know if anyone is successfully running MAAS on 12.04 LTS? Are there any new repos I should be using to get the latest updates?

All help and suggestions are appreciated.

Question information

English Edit question
MAAS Edit question
No assignee Edit question
Solved by:
John Barbee
Last query:
Last reply:
Revision history for this message
Andres Rodriguez (andreserl) said :

Hi John,

Thank you for trying out MAAS and asking the question. Could you please specify what kind of apparmor denials are you seeing on the syslog when using maas, and how are these being triggered (i.e. doing operations outside of maas and to cobbler directly?)

While it would be ok to disable the apparmor profile for maas-provision, I'd highly discourage it. The profile handles the operations that are needed for MAAS within cobbler, and, while you might see denials, it continues to work the way MAAS needs cobbler to.


Revision history for this message
John Barbee (jbarbee00) said :

After further testing, I have found these apparmor permission errors to be irrelevant.