https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-03-29T13:29:40ZopenSUSE Project Management ToolopenQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2033332019-03-29T13:29:40ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-4 status-3 priority-3 priority-lowest closed" href="/issues/48434">action #48434</a>: [functional][u] test Tumbleweed s390x again</i> added</li></ul> openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2033392019-03-29T13:30:32ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Assignee</strong> set to <i>SLindoMansilla</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2033482019-03-29T13:35:35ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Blocked</i></li></ul><p>Waiting for z/VM user from Z system admins</p>
openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2150992019-05-25T21:08:59Zbinary_sequence
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>Workable</i></li><li><strong>Assignee</strong> changed from <i>SLindoMansilla</i> to <i>binary_sequence</i></li></ul><p>I already got a z/VM user.</p>
openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2414152019-09-04T16:40:05ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-4 status-3 priority-3 priority-lowest closed" href="/issues/48434">action #48434</a>: [functional][u] test Tumbleweed s390x again</i>)</li></ul> openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2414242019-09-04T16:40:33ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-3 priority-lowest closed" href="/issues/48434">action #48434</a>: [functional][u] test Tumbleweed s390x again</i> added</li></ul> openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2829672020-03-04T10:23:32ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>At the moment this is very low prio since we have a dedicated server (rebel) for testing linux as a zVM guest: <a href="https://openqa.opensuse.org/group_overview/34" class="external">https://openqa.opensuse.org/group_overview/34</a></p>
openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2831862020-03-04T18:41:15Zokurzokurz@suse.com
<ul></ul><p>I don't think this is feasible as allowing ssh kinda contradicts apparmor by definition, doesn't it?</p>
openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2835192020-03-06T08:12:25ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Rejected</i></li></ul><p>Yes, you are right.</p>
openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2835202020-03-06T08:25:59Zpvorelpetr.vorel@suse.com
<ul></ul><p>Could you please explain what's wrong on ssh?<br>
There is sshd profile<br>
<a href="https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor/profiles/extras/usr.sbin.sshd" class="external">https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor/profiles/extras/usr.sbin.sshd</a></p>
openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2835352020-03-06T08:34:05ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>pvorel wrote:</p>
<blockquote>
<p>Could you please explain what's wrong on ssh?<br>
There is sshd profile<br>
<a href="https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor/profiles/extras/usr.sbin.sshd" class="external">https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor/profiles/extras/usr.sbin.sshd</a></p>
</blockquote>
<p>Company policies. They denied me to add ssh to the apparmor profiles.</p>
openQA Tests - action #49820: [functional][u] Make the svirt backend work with AppArmor enabled and under company policieshttps://progress.opensuse.org/issues/49820?journal_id=2835522020-03-06T09:25:21Zokurzokurz@suse.com
<ul></ul><p>SLindoMansilla wrote:</p>
<blockquote>
<p>[…]<br>
Company policies.</p>
</blockquote>
<p>please reference the "company policies" then or state "I did not understand" instead of spreading false rumors.</p>