https://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-06-05T16:44:52ZPulpPulp - Issue #2792: syncing an importer has SELinux denialshttps://pulp.plan.io/issues/2792?journal_id=200252017-06-05T16:44:52Zbmbouterbmbouter@redhat.com
<ul></ul><p>On Pulp2 SELinux was disabled in the Vagrant environment which is tracked as Issue <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a>. With Pup3's Vagrant env it sets SELinux to Enforcing currently (I think). I read this issue as basically Issue <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> only for Pulp3. Is this issue a duplicate of Issue <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> if we repurpose Issue <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> to be fixed with Pulp3?</p>
<p>The temporary workaround is to disable SELinux via the Ansible playbooks like we did on Pulp2. I think that is OK given its a dev environment and the work of fixing <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> in Vagrant is non-trivial at this time.</p>
<p>What do others think?</p> Pulp - Issue #2792: syncing an importer has SELinux denialshttps://pulp.plan.io/issues/2792?journal_id=200262017-06-05T16:49:01Zamacdona@redhat.comaustin@redhat.com
<ul></ul><p>Pulp 3 SELinux is set to "Permissive" for now. It is fine with me if we want to use <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> instead, but I don't want to have 1 SELinux issue to track Pulp 3 and Pulp 2, the environments are too different.</p> Pulp - Issue #2792: syncing an importer has SELinux denialshttps://pulp.plan.io/issues/2792?journal_id=200282017-06-05T17:37:24Zbmbouterbmbouter@redhat.com
<ul></ul><p>With our focus on Pulp3 for active development I think we should close either this or <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> as a duplicate and rewrite the open one to be Pulp3 specific. Since I know exactly what needs to be done to fix up the descriptions, should I do this?</p> Pulp - Issue #2792: syncing an importer has SELinux denialshttps://pulp.plan.io/issues/2792?journal_id=200292017-06-05T17:41:42Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul><p>Per IRC confirmation, I'm closing this one as a duplicate of Issue <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> and will then update <a class="issue tracker-3 status-1 priority-6 priority-default parent" title="Story: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment (NEW)" href="https://pulp.plan.io/issues/97">#97</a> to be for Pulp3 only.</p> Pulp - Issue #2792: syncing an importer has SELinux denialshttps://pulp.plan.io/issues/2792?journal_id=200302017-06-05T17:42:15Zbmbouterbmbouter@redhat.com
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-3 status-1 priority-6 priority-default parent" href="/issues/97">Story #97</a>: As a contributor, I rest easy knowing SELinux is Enforcing in the Pulp3 Vagrant environment</i> added</li></ul> Pulp - Issue #2792: syncing an importer has SELinux denialshttps://pulp.plan.io/issues/2792?journal_id=382502019-04-15T20:17:45Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>