Comment # 3 on bug 1120472 from Guillaume GARDET

(In reply to Christian Boltz from comment #1)
> That's interesting[tm], and it looks like openQA found a scenario that I
> thought would never happen. (Actually I wasn't even aware that we have
> AppArmor tests in openQA ;-) - thanks to whoever added them!)
> 
> I just tried to reproduce the issue locally by doing what openQA does, but
> (un)fortunately aa-logprof "just works" as expected.

Since it is only in latest openQA snapshot (20181231), it is not in released
Tumbleweed.

> 
> I have two questions:
> 
> Is there a way to get the debug log /tmp/apparmor-bugreport-*.txt from
> openQA? (note that the filename is mktemp-generated)
> The debug log contains the content of variables etc. and is hopefully
> helpful to find out what happens.

Added in attachment.

> 
> Also, where can I find the source code of the AppArmor tests done by openQA?
> Maybe there's a detail I missed in the screenshot.

You can get by clicking aa_logprof (test title) in openQA:
https://openqa.opensuse.org/tests/822549#step/aa_logprof/24


BTW, in latest Tumbleweed snapshot, it seems '/usr/sbin/nscd' has been replaced
by just 'nscd'. Not sure if it could be the cause?