http://bugzilla.opensuse.org/show_bug.cgi?id=1190918 http://bugzilla.opensuse.org/show_bug.cgi?id=1190918#c3 --- Comment #3 from Enzo Matsumiya <ematsumiya@suse.com> --- (In reply to Dominique Leuenberger from comment #2)
In what way confusing? i.e. https://openqa.opensuse.org/tests/1937572
It runs multiple 'test modules' - mainly taking the MicroOS medium (can be downloaded from the test under Logs&Assets) and install it (as role MicroOS container Host) using mostly defaults.
Thanks. I couldn't really see what's being run/logged before audit errors.
- this is trigged by "systemctl start auditd.service", yes or no?
Triggered right after bootup (audit is a default-enabled service). According to the journal, boot happened (in the linked test) at Sep 25 18:42:10, the log from audit appeared at 18:42:45 (regular bootup delay with selinux relabeling and first boot)
Ack.
- what's the host setup like? I don't have experience with microOS and container technologies whatsoever, so if you could give me a step-by-step guide how to get a similar environment I'd appreciate it
Nothing special there: default install of MicroOS from DVD (online repo disabled, role MicroOS Container Host); the VM used is kvm/qemu, 40GB HDD and 2GB RAM)
Ok, I'll try to reproduce it. -- You are receiving this mail because: You are on the CC list for the bug.