https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-08-27T20:24:24ZPulpPulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=59332015-08-27T20:24:24Zbmbouterbmbouter@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5933/diff?detail_id=5732">diff</a>)</li><li><strong>Tags</strong> <i>Easy Fix</i> added</li></ul><p>The root cause of this bug is that the Celery code doesn't know how to find the settings file. I believe currently only httpd knows where the settings file is. The fix is to ensure that all Pulp components know how to find the settings file. All entry points for celery processes need to ensure they set the environment variable like this:</p>
<pre><code>os.environ.setdefault("DJANGO_SETTINGS_MODULE", "pulp.server.webservices.settings")
</code></pre>
<p>I'll also suggest this becomes a constant in pulp server so that we don't duplicate the string we are setting here.</p>
<p>This is where httpd does it for example: <a href="https://github.com/pulp/pulp/blob/fa1af4fbc6f37874879a4eb209ff2b57efc16a5d/server/pulp/server/webservices/wsgi.py#L11" class="external">https://github.com/pulp/pulp/blob/fa1af4fbc6f37874879a4eb209ff2b57efc16a5d/server/pulp/server/webservices/wsgi.py#L11</a></p> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=59352015-08-28T14:23:53Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>dkliban@redhat.com</i></li></ul> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=59432015-08-28T14:36:58Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Severity</strong> changed from <i>2. Medium</i> to <i>3. High</i></li><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=59732015-09-02T17:44:07Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>MODIFIED</i></li><li><strong>Platform Release</strong> set to <i>2.7.0</i></li></ul> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=60432015-09-09T11:31:17Zbmbouterbmbouter@redhat.com
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-12 priority-6 priority-default closed" href="/issues/1242">Issue #1242</a>: Django setting undefined error in importer update</i> added</li></ul> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=65692015-10-12T15:55:51Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=68722015-11-06T19:31:16Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=396032019-04-15T20:44:11Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul> Pulp - Issue #1216: Updating a pulp repo importer settings via api causes an errorhttps://pulp.plan.io/issues/1216?journal_id=581922020-06-16T20:54:35Zbmbouterbmbouter@redhat.com
<ul><li><strong>Category</strong> deleted (<del><i>14</i></del>)</li></ul><p>We are removing the 'API' category per open floor discussion June 16, 2020.</p>