action #25158
closed
- Status changed from New to In Progress
please update today together with zluo, IMHO we are blocked by the same bug as for SLE15 that the layout is cramped together so needles won't match
- Due date set to 2017-09-27
- Priority changed from Normal to High
bumped prio because both TW and SLE are affected, also integrating duplicate
- Has duplicate action #23846: yast2_apparmor failed on recently for TW added
I've verified this on both SLE15 and TW. Despite ugly GUI, we still can test apparmor further as GUI was changed and tests need adjustment.
- Assignee changed from riafarov to SLindoMansilla
As per discussion, assign it to Sergio. The only specific thing about this ticket is to consider creating workaround needles for ugly looking interface.
- Status changed from In Progress to Resolved
- Assignee changed from SLindoMansilla to okurz
needles merged. I looked at the error message. To me it looks like a bug. Especially when I take a look into y2log then which states:
2017-09-15 08:45:28 <3> susetest(3261) [bash] ShellCommand.cc(shellcommand):78 Failed to get unit file state for apparmor.service: No such file or directory
2017-09-15 08:45:28 <3> susetest(3261) [Ruby] modules/Service.rb:443 Service 'apparmor' not found
2017-09-15 08:45:28 <1> susetest(3261) [Ruby] yast2/systemd_unit.rb:123 `systemctl show apparmor.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath `
2
Did you come to the same conclusion? If yes I wonder why you did not create a bug then? After merging the needles I triggered the test now on osd and could confirm the error https://openqa.suse.de/tests/1172782#step/yast2_apparmor/7 So now I created a bug bsc#1058981
I think we are done here as we end up in a product bug. Good job.
Also available in: Atom
PDF