Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-06-05T19:34:46ZPulp
Planio Docker Support - Refactor #1037 (CLOSED - CURRENTRELEASE): Remove manual setting for repo.repo_idhttps://pulp.plan.io/issues/10372015-06-05T19:34:46Zbcourtbcourt@redhat.com
<p>Remove manual setting of repo.repo_id = repo_transfer.id throughout Docker and OSTree plugins.</p>
<p>All other usages should already use repo_transfer.repo_obj to access the native object (with its id) from the repo_transfer object.</p> Nectar - Story #1031 (CLOSED - WONTFIX): Create a jenkins job to automatically test all Nectar PRshttps://pulp.plan.io/issues/10312015-06-04T13:56:12Zbcourtbcourt@redhat.com
<p>Create a jenkins job similar to the one for Pulp that automatically tests all PR requests</p> Crane - Story #1030 (CLOSED - WONTFIX): Create a jenkins job to automatically test all Crane PRshttps://pulp.plan.io/issues/10302015-06-04T13:54:55Zbcourtbcourt@redhat.com
<p>Create a Jenkins job similar to our plugin builders to automatically unit test all PRs automatically.</p> Pulp - Issue #993 (CLOSED - CURRENTRELEASE): Worker discovery takes 30 seconds when all services ...https://pulp.plan.io/issues/9932015-05-20T17:39:07Zbcourtbcourt@redhat.com
<p>When all of the pulp services are restarted at the same time it often takes 30 seconds before the workers are discovered.</p>
<p>When running the script:</p>
<pre><code>[root@bcourt pulp]# /home/bcourt/bin/restart-pulp.sh
++ systemctl stop httpd
++ systemctl stop pulp_workers
++ systemctl stop pulp_resource_manager
++ systemctl stop pulp_celerybeat
++ systemctl stop goferd
++ systemctl stop qpidd
++ systemctl start qpidd
++ systemctl start goferd
++ systemctl start pulp_celerybeat
++ systemctl start pulp_resource_manager
++ systemctl start pulp_workers
++ systemctl start httpd
[root@bcourt pulp]#
</code></pre>
<p>The following are the relevant log entries:</p>
<pre><code>May 20 13:33:42 bcourt.usersys.redhat.com pulp[8229]: pulp.server.webservices.application:INFO: *************************************************************
May 20 13:33:42 bcourt.usersys.redhat.com pulp[8229]: pulp.server.webservices.application:INFO: The Pulp server has been successfully initialized
May 20 13:33:42 bcourt.usersys.redhat.com pulp[8229]: pulp.server.webservices.application:INFO: *************************************************************
May 20 13:33:42 bcourt.usersys.redhat.com pulp[8229]: gofer.messaging.adapter.qpid.connection:INFO: opened: qpid+tcp://localhost:5672
May 20 13:33:42 bcourt.usersys.redhat.com pulp[8229]: gofer.messaging.adapter.connect:INFO: connected: qpid+tcp://localhost:5672
May 20 13:34:10 bcourt.usersys.redhat.com pulp[8185]: pulp.server.async.worker_watcher:INFO: New worker 'reserved_resource_worker-1@bcourt.usersys.redhat.com' discovered
May 20 13:34:10 bcourt.usersys.redhat.com pulp[8185]: pulp.server.async.worker_watcher:INFO: New worker 'reserved_resource_worker-3@bcourt.usersys.redhat.com' discovered
May 20 13:34:10 bcourt.usersys.redhat.com pulp[8185]: pulp.server.async.worker_watcher:INFO: New worker 'reserved_resource_worker-0@bcourt.usersys.redhat.com' discovered
May 20 13:34:11 bcourt.usersys.redhat.com pulp[8185]: pulp.server.async.worker_watcher:INFO: New worker 'reserved_resource_worker-2@bcourt.usersys.redhat.com' discovered
</code></pre>
<p>This looks like a race condition where the initial heartbeat from the worker is missed as celerybeat is still starting up. A simple solution would be to have the workers heartbeat faster initially and then back off once they have communication with celerybeat.</p> Packaging - Issue #964 (CLOSED - WONTFIX): registry-admin.py unable to create grant https://pulp.plan.io/issues/9642015-05-08T14:08:24Zbcourtbcourt@redhat.com
<p>Relocated from: <a href="https://github.com/pulp/pulp_packaging/issues/53" class="external">https://github.com/pulp/pulp_packaging/issues/53</a><br>
This command line is taken from the README.md file.</p>
<pre><code>[lvu@lvupulp ~]$ python repos/pulp_packaging/dockerfiles/registry-admin.py pulp "auth permission grant --role-id contributor --resource /repositories -o create -o read -o update -o execute"
User certificate not found.
Enter registry username [lvu]: admin
Enter registry password:
Warning: path should have mode 0700 because it may contain sensitive information: /root/.pulp/
Command: login
Description: login and download a session certificate
Available Arguments:
--username, -u - (required) server account username
--password, -p - server account password
The following options were specified but do not exist on the command:
--role-id
Warning: path should have mode 0700 because it may contain sensitive information: /root/.pulp/
The server hostname configured on the client did not match the name found in the
server's SSL certificate. The client attempted to connect to
[lvupulp.dyn.intelerad] but the server returned [pulpapi] as its hostname. The
expected hostname can be changed in the client configuration file.
[lvu@lvupulp ~]$
</code></pre> Debian Support - Refactor #878 (CLOSED - CURRENTRELEASE): Convert pulp_deb to use MongoEngine modelshttps://pulp.plan.io/issues/8782015-04-10T17:35:20Zbcourtbcourt@redhat.com
<p>Convert the pulp_deb to use MongoEngine models for all unit actions instead of the associated unit</p>
<p>Deliverables:</p>
<ul>
<li>ContentUnit model for docker_image units
<ul>
<li>The model is registered via the entry point</li>
<li>The types .json file is removed, and references to it in the spec files are are also removed</li>
</ul>
</li>
<li>All interactions with units in the plugin use the new unit model and the Repository model for creating, saving and updating units</li>
<li>Convert the model according to the <a href="https://fedorahosted.org/pulp/wiki/ConvertingModelsToMongoengine#StepsinvolvedinconvertingaPulpmodeltoMongoEngine" class="external">conversion guide</a>
</li>
</ul>
<p>Supported operations:</p>
<p>Milestone 1:</p>
<ul>
<li>Create repository to host deb packages</li>
<li>Add deb unit to deb repository (implementation detail: importer needs to work)</li>
<li>Publish apt repository (implementation detail: distributor needs to work)</li>
<li>Sign repository metadata within the distributor</li>
</ul>
<p>Milestone 2:</p>
<ul>
<li>Ability to sync a repo produced at milestone 1 (one dist, one component, one architecture)</li>
</ul>
<p>To be done later:</p>
<ul>
<li>Full mirror support - problematic for several reasons:
<ul>
<li>we need a way to keep track of which deb unit came from which dist/component/architecture</li>
<li>in order to not invalidate the repo metadata signature, we may have to save the repo metadata files and publish exactly those.</li>
</ul>
</li>
<li>Partial mirror
<ul>
<li>ability to specify a whitelist of dist/component/architecture combinations to be synced</li>
</ul>
</li>
</ul> OSTree Support - Refactor #876 (CLOSED - CURRENTRELEASE): Convert pulp_ostree to use MongoEngine ...https://pulp.plan.io/issues/8762015-04-10T17:32:26Zbcourtbcourt@redhat.com
<p>Convert the pulp_ostree to use MongoEngine models for all unit actions instead of the associated unit</p>
<p>Deliverables:</p>
<ul>
<li>ContentUnit model for docker_image units
<ul>
<li>The model is registered via the entry point</li>
<li>The types .json file is removed, and references to it in the spec files are are also removed</li>
</ul>
</li>
<li>All interactions with units in the plugin use the new unit model and the Repository model for creating, saving and updating units</li>
</ul> Docker Support - Refactor #863 (CLOSED - CURRENTRELEASE): Convert pulp_docker to use MongoEngine ...https://pulp.plan.io/issues/8632015-04-10T15:32:38Zbcourtbcourt@redhat.com
<p>Convert the pulp_docker to use MongoEngine models for all unit actions instead of the associated unit</p>
<p>Deliverables:</p>
<ul>
<li>ContentUnit model for docker_image units
<ul>
<li>The model is registered via the entry point</li>
<li>The types .json file is removed, and references to it in the spec files are are also removed</li>
</ul>
</li>
<li>All interactions with units in the plugin use the new unit model and the Repository model for creating, saving and updating units</li>
</ul> Packaging - Issue #741 (CLOSED - WONTFIX): pulp::server::install puppet module does not install s...https://pulp.plan.io/issues/7412015-03-06T21:27:29Zbcourtbcourt@redhat.com
<p>The pulp::server::install module only installs the pulp-server yum group. This means that the server does not have everything that it needs to communicate with gofer or rabbitmq and that the selinux policy is not installed. The module should have an option to choose from rabbit or qpid and install the appropriate transport and selinux policy as well.</p> 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 #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> 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> 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> 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>