Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-03-04T16:38:19ZPulp
Planio Packaging - Issue #724 (CLOSED - CURRENTRELEASE): Integration test runner fails because it can't ...https://pulp.plan.io/issues/7242015-03-04T16:38:19Zbcourtbcourt@redhat.com
<p>The Jenkins job to run the integration tests against a given repository is currently broken due to a problem selecting the appropriate image to use in the qeos environment. The get_pulp_images() in the os1 utils script should be updated to use the image name rather than a tag.</p>
<p><a href="https://github.com/pulp/pulp_packaging/blob/master/ci/deploy/utils/os1_utils.py#L100" class="external">https://github.com/pulp/pulp_packaging/blob/master/ci/deploy/utils/os1_utils.py#L100</a></p> Pulp - Issue #682 (CLOSED - CURRENTRELEASE): publish_repo failures that do not raise an exception...https://pulp.plan.io/issues/6822015-02-28T23:22:14Zbcourtbcourt@redhat.com
<p>Description of problem:</p>
<p>When a distributor has it's publish_repo method called and the publish report return indicates a failure the task is marked as completing successfully. If the publish_repo method raises an exception the task is marked properly as failed.</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1186920" class="external">Bugzilla Bug #1186920</a> +</p> Pulp - Issue #640 (CLOSED - CURRENTRELEASE): Current master of nectar requires a newer version of...https://pulp.plan.io/issues/6402015-02-28T22:46:43Zbcourtbcourt@redhat.com
<p>Description:<br>
The current master branch of nectar will fail if run against python-requests 2.2.1. The dependency in pulp & nectar should be updated or the threaded downloader should be updated to not use the new python-requests api.</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1174283" class="external">Bugzilla Bug #1174283</a> +</p> Pulp - Issue #489 (MODIFIED): When an task worker dies or restarts, work assigned to that worker ...https://pulp.plan.io/issues/4892015-02-28T22:15:18Zbcourtbcourt@redhat.com
<p>Description of problem:</p>
<p>When an RQ restarts (or dies) the tasks assigned to that worker get marked as cancelled. The cancelled state is correct, but users who dispatch work don't expect random cancelling of tasks so this isn't a great behavior.</p>
<p>To reproduce:<br>
1. Start Pulp system with exactly 1 worker<br>
2. Start a really long sync<br>
3. List the tasks and observe that the task you submitted is in the running state<br>
4. During the sync `kill -9` the worker<br>
5. Start that worker up again<br>
6. List the tasks again and observe that the task you submitted is in the cancelled state</p>
<p>Expected result: That the work you submitted to Pulp doesn't end up in the cancelled state when a worker dies. I expect it to be re-picked up by the worker and be in the running state.</p> Pulp - Issue #387 (CLOSED - WONTFIX): Pulp Distributors should not be created using the distribut...https://pulp.plan.io/issues/3872015-02-28T22:00:11Zbcourtbcourt@redhat.com
<p>Description of problem:</p>
<p>Distributors that are currently created by the command line & the unit tests are using the distributor_type_id as the distributor_id. Katello specifies a different value for the distributor_id. This has led to a number of bugs including 1038309 that were not found until Katello had a release in hand.</p>
<p>Our client & server code should be reworked to use the id generated by mongo automatically instead of creating one. Have the server (mongo) generate a unique distributor id automatically if one is not specified on the API, or use the object id that mongo is already creating. The client code should be updated to not specify the distributor ID.</p>
<p>We could also consider removing the distributor_id entirely and just use the id from mongo.</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1038751" class="external">Bugzilla Bug #1038751</a> +</p> Pulp - Refactor #302 (CLOSED - WONTFIX): Package nodes as core functionality of pulp-server inste...https://pulp.plan.io/issues/3022015-02-25T16:05:16Zbcourtbcourt@redhat.com
<p>Currently Nodes is packages as 4 separate rpms. These should be collapsed into the core pulp-server rpms<br>
pulp-nodes-common -> python-pulp-common<br>
pulp-nodes-parent -> pulp-server<br>
pulp-nodes-child -> pulp-server<br>
pulp-nodes-admin-extensions -> pulp-admin-client<br>
pulp-nodes-consumer-client -> pulp-admin-client * Currently the nodes consumer client depends on the pulp-consumer-client but it is only valid when run on a pulp-server. If we don't want to move the functionality purely to the admin client then it should be kept as a separate RPM until a major version release when it can be moved.</p>
<p>All of the old RPMs should be obsoleted in the spec file. The nodes directories within the project should be merged into the respective directories that match the components the RPMs are being merged into.</p> Crane - Story #260 (CLOSED - WONTFIX): [RFE] Crane should install a default /etc/crane.confhttps://pulp.plan.io/issues/2602015-02-19T01:19:48Zbcourtbcourt@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1150222" class="external">Bugzilla Bug #1150222</a> +</span>+</p>
<p>Description of problem:</p>
<p>Crane should create a default /etc/crane.conf that is commented out similarly to the /etc/pulp/server.conf.</p> Pulp - Story #259 (CLOSED - WONTFIX): [RFE] Automatically load global configuration for pluginshttps://pulp.plan.io/issues/2592015-02-19T01:19:44Zbcourtbcourt@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1150162" class="external">Bugzilla Bug #1150162</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:</p>
<p>Currently all plugins have to specify their global configuration file and load it manually. The platform should automatically look for a server/plugin.conf.d/<plugin_id>.ini file and use that for the global plugin configuration.</p> Pulp - Story #258 (CLOSED - WONTFIX): [RFE] Use the same configuration file format everywhere in ...https://pulp.plan.io/issues/2582015-02-19T01:19:41Zbcourtbcourt@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1150153" class="external">Bugzilla Bug #1150153</a> +</span>+</p>
<p>Description of problem:</p>
<p>Currently we have configuration files in both INI and JSON format. The server plugin.conf.d format is json and the rest of the pulp configuration files are in ini format. This is confusing to the user. We should use the same format for<br>
configuration files everywhere. I would propose that we use ini files everywhere since as a format it allows us to include comments that show all the valid keys that could be filled in.</p>
<p>--- Additional comment from <a href="mailto:mhrivnak@redhat.com" class="email">mhrivnak@redhat.com</a> at 10/10/2014 16:20:50 ---</p>
<p>This will definitely impact katello, so keep them in the loop.</p> Packaging - Task #151 (CLOSED - CURRENTRELEASE): Add automation to perform beta/release builds.https://pulp.plan.io/issues/1512015-02-06T19:17:26Zbcourtbcourt@redhat.com
<p>Assumptions:</p>
<ul>
<li>All projects built using this framework use the x.y-dev,x.y-testing,x.y-release</li>
<li>RPM signing is still completed manually</li>
<li>The spec files in the x.y-testing repository will have their versions bumped when the content is merged from x.y-dev or when the first new commit is added after a release build. This is not auto-bumped as part of the release build as we would have no way to know if no changes have been added to a project.</li>
</ul> Packaging - Task #89 (CLOSED - CURRENTRELEASE): Add automation to run unit tests for all PRs agai...https://pulp.plan.io/issues/892015-01-05T21:24:17Zbcourtbcourt@redhat.com
<p>Us the jenkins github pull request builder plugin to build all PRs against the core Pulp project automatically. This includes creating comments on the PRs indicating the success/failure of the test run.</p>
<p>This will require dynamically figuring out which nightly repo should be used to install the base pulp and plugin.</p>
<p>General procedure for running the unit tests</p>
<ol>
<li>Determine the base repository to install from</li>
<li>Install @pulp-server-qpid</li>
<li>Install the plugin that is being tested from RPM (this will ensure all dependencies are installed)</li>
<li>Uninstall the plugin that is being tested</li>
<li>Install the plugin from source</li>
<li>Run the tests</li>
</ol> Pulp - Task #85 (CLOSED - CURRENTRELEASE): Add automation to run unit tests for all PRs against p...https://pulp.plan.io/issues/852015-01-02T18:06:20Zbcourtbcourt@redhat.com
<p>Us the jenkins github pull request builder plugin to build all PRs against the core Pulp project automatically. This includes creating comments on the PRs indicating the success/failure of the test run.</p> Puppet Support - Story #83 (CLOSED - CURRENTRELEASE): As a user I can install puppet modules usin...https://pulp.plan.io/issues/832014-12-19T21:40:05Zbcourtbcourt@redhat.com
<p>As a user I can install a module using the puppet module install command line using the v3 forge api enumerated at <a href="https://forgeapi.puppetlabs.com/" class="external">https://forgeapi.puppetlabs.com/</a></p>
<p>This will entail creating a new /v3/releases endpoint. We will have to go back to the pre-puppet 3.3 method of determining the repository and consumer as the ability to specify a context root has been disabled.</p>
<p>The api now requires pagination, offset tracking, and providing the urls for the next/previous queries in the case of pagination.<br>
There are now many more options for filtering.</p>
<p>We will only have to support the /v3/releases endpoint at this time.</p> Debian Support - Task #80 (CLOSED - CURRENTRELEASE): Design data model to support Debian reposhttps://pulp.plan.io/issues/802014-12-19T14:10:04Zbcourtbcourt@redhat.com
<p>Debian repositories support publishing multiple sub-repositories with a shared content folder. We need to figure out what that looks like in Pulp where a repositories have traditionally been much more monolithic.</p> Pulp - Task #79 (CLOSED - WONTFIX): Move Nodepool to a dedicated locationhttps://pulp.plan.io/issues/792014-12-18T23:39:22Zbcourtbcourt@redhat.com
<p>Currently nodepool is running on a personal workstation. It should be moved to either a dedicated server, a docker image or an openshift gear that has more of an uptime guarantee</p>