[MDEV-2570] LP:491349 - MariaDB 5.1 apparmor profile incompatible with mysql-test-run.pl Created: 2009-12-02  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Kristian Nielsen Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug491349.xml    

 Description   

The apparmor profile shipped in MariaDB 5.1.39 ubuntu debs prevents mysql-test-run.pl from working (the reason is that /usr/sbin/mysqld needs write permissions to the --vardir directory given by the user to mysql-test-run.pl).

Since I believe apparmor is enabled by default in recent Ubuntu's, this means mysql-test-run.pl fails out-of-the-box on such systems.

I don't think apparmor functionality is critical for MariaDB at this stage. Options for fixes (all ok with me):

1. Move the MariaDB apparmor profile to /usr/share/doc/mariadb-server with comments about the issue (so it is only enabled if users do so explicitly).

2. Document the issue that apparmor needs to be uninstalled/disabled to run the test suite (it is in any case not trivial to run the test suite due to need to pass writable --vardir to mysql-test-run.pl, /usr/share/mysql/mysql-test is usually not writable).

3. Fix the apparmor profile to not restrict /usr/sbin/mysqld from writing files anywhere normal permissions allow.



 Comments   
Comment by Kristian Nielsen [ 2012-03-02 ]

Re: MariaDB 5.1 apparmor profile incompatible with mysql-test-run.pl
We removed the default apparmor profile from mariadb packages due to this and multiple other issues for users.

Users can still maintain their own profile for mariadb, and adjust it to allow running mysql-test-run as they want/need.

Comment by Rasmus Johansson (Inactive) [ 2012-03-02 ]

Launchpad bug id: 491349

Generated at Thu Feb 08 06:42:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.