action #49820
closed
[functional][u] Make the svirt backend work with AppArmor enabled and under company policies
Added by SLindoMansilla about 5 years ago.
Updated about 4 years ago.
Description
Motivation¶
Enabling openSUSE Tumbleweed tests for s390x on openqa.opensuse.org.
Find more details about why this is needed in #48434
Acceptance criteria¶
- AC1: The svirt backend complies with the company policies to be run on a shared worker on openqa.opensuse.org
- AC2: It is possible to enable a worker for z/VM on imagetester
- Blocks action #48434: [functional][u] test Tumbleweed s390x again added
- Assignee set to SLindoMansilla
- Priority changed from Normal to Low
- Status changed from New to Blocked
Waiting for z/VM user from Z system admins
- Status changed from Blocked to Workable
- Assignee changed from SLindoMansilla to binary_sequence
I already got a z/VM user.
- Blocks deleted (action #48434: [functional][u] test Tumbleweed s390x again)
- Related to action #48434: [functional][u] test Tumbleweed s390x again added
I don't think this is feasible as allowing ssh kinda contradicts apparmor by definition, doesn't it?
- Status changed from Workable to Rejected
SLindoMansilla wrote:
[…]
Company policies.
please reference the "company policies" then or state "I did not understand" instead of spreading false rumors.
Also available in: Atom
PDF