http://bugzilla.opensuse.org/show_bug.cgi?id=1074429 Bug ID: 1074429 Summary: [20180101] AppArmor cannot be started in Kubic Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta@cboltz.de Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- With snapshot 20180101, apparmor was updated to version 2.12, which seems to be responsible for the new openQA failure seen on Tumbleweed Kubic: apparmor does not get successfully started, as it seems to try to write to locations it's not supposed to. The journal shows: ● apparmor.service - Load AppArmor profiles Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-01-02 17:15:44 UTC; 3min 34s ago Process: 461 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE) Main PID: 461 (code=exited, status=1/FAILURE) CPU: 221ms Jan 02 17:15:43 localhost apparmor.systemd[461]: mkstemp: Read-only file system Jan 02 17:15:43 localhost apparmor.systemd[461]: Error: /etc/apparmor.d/usr.lib.dovecot.dovecot-auth failed to load Jan 02 17:15:43 localhost apparmor.systemd[461]: mkstemp: Read-only file system Jan 02 17:15:43 localhost apparmor.systemd[461]: Error: /etc/apparmor.d/usr.lib.dovecot.dovecot-lda failed to load Jan 02 17:15:43 localhost apparmor.systemd[461]: mkstemp: Read-only file system Jan 02 17:15:43 localhost apparmor.systemd[461]: Error: /etc/apparmor.d/usr.lib.dovecot.imap failed to load Jan 02 17:15:44 localhost systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE Jan 02 17:15:44 localhost systemd[1]: Failed to start Load AppArmor profiles. Jan 02 17:15:44 localhost systemd[1]: apparmor.service: Unit entered failed state. Jan 02 17:15:44 localhost systemd[1]: apparmor.service: Failed with result 'exit-code'. https://openqa.opensuse.org/tests/572483#step/journal_check/14 -- You are receiving this mail because: You are on the CC list for the bug.