Comment 3 for bug 401109

It is by design that force-complain profiles will not be cached (since their text may not match their binary).

The cache files were created recently in your first "ls" output, which implies that they are being run through the parser. Why they don't appear in aa-status is not clear to me. Can you boot without "quiet splash" and capture the AppArmor start-up output? Also, you can change the init script to drop the "-q" option so it reports each profile as it loads it.