MariaDB 5.1 apparmor profile incompatible with mysql-test-run.pl

Bug #491349 reported by Kristian Nielsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MariaDB
Fix Released
Medium
Unassigned
OurDelta
Confirmed
Undecided
Unassigned

Bug 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.

Changed in maria:
importance: Undecided → Medium
status: New → Confirmed
Changed in ourdelta:
status: New → Confirmed
Changed in maria:
milestone: none → 5.1
Revision history for this message
Kristian Nielsen (knielsen) wrote :

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.

Changed in maria:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.