Pulp

07/26/2017

• 
  elyezer Pulp

  08:16 PM · Edited wiki

  Wiki edit: Virtualization_quickstart (#6)

04/17/2017

• 
  elyezer Crane

  05:22 PM · Commented on issue

  Can you also provide more documentation on how to configure Crane with SSL?
  That will help testing Crane under https and as a secure registry.
  Issue #2701: Crane documentation doesn't answer critical installation and usage questions

  I've read through the following:
  - https://docs.pulpproject.org/plugins/pulp_docker/user-guide/recipes.html
  - https://docs.pulpproject.org/plugins/crane/index.html
  - https://github.com/pulp/crane/blob/master/docs/index.rst
  ...

03/31/2017

• 
  elyezer Pulp

  09:00 PM · Closed issue

  Issue #2688 (CLOSED - CURRENTRELEASE): last_unit_added is not updated when units are copied over from another repo

  Steps to reproduce:
  1. Create a repo with a feed and sync it
  2. Create a second repo without a feed and don't sync it
  3. Copy units from the first repo to the second
  4. Check the last_unit_added field
  The output below was ge...

01/25/2017

• 
  elyezer Pulp

  06:51 PM · Closed issue

  Issue #2545 (CLOSED - CURRENTRELEASE): pulp-manage-db wait time calculation can end up with many hours of wait time

  Running the automation jobs showed that pulp-manage-db can wait for hours instead of to wait for up to 92 seconds (checked `constants.MIGRATION_WAIT_TIME` for this information).
  I've ssh into the machine where pulp-manage-db is runnin...

12/13/2016

• 
  elyezer Pulp

  05:15 PM · Commented on issue

  My suggestion then is to provide some sort of documentation on the release notes since the upgrade instructions usually state:
  ~~~
  > $ sudo systemctl stop httpd pulp_workers pulp_resource_manager pulp_celerybeat
  > $ sudo yum upgrade
  > $... Issue #2485: Add documentation about the need of restart pulp_streamer when upgrading to Pulp 2.11 from old versions

  The documentation should state the need of stopping pulp_streamer before upgrading and starting it after the upgrade when upgrading from older versions.
  If that is not done, then Pulp will raise errors like the following which was rai...
• 
  elyezer mhrivnak wrote:
  > We discussed on IRC that this could potentially be explained by an upgrade where the streamer did not get stopped before the upgrade. If a \< 2.10 streamer was running with a \>=2.10 pulp, this failure would be expecte...

  05:09 PM · Commented on issue
• 
  elyezer The documentation should state the need of stopping pulp_streamer before upgrading and starting it after the upgrade when upgrading from older versions.
  If that is not done, then Pulp will raise errors like the following which was rai...

  02:47 PM · Closed issue

12/07/2016

• 
  elyezer Pulp

  01:11 PM · Commented on issue

  After some conversation we decided that the blocker was #2469.
  Issue #2472: pulp-manage-db does not clear the running worker flag even after the 300 seconds limit when upgrading

  When upgrading Pulp to 2.11 pulp-manage-db does not identify that worker are stopped for more than 300 seconds.
  The following output is from a RHEL7 system which has Pulp upgraded from Pulp 2.10:
  ~~~
  # systemctl status httpd pulp_...

12/06/2016

• 
  elyezer Pulp

  06:24 PM · Commented on issue

  I think this should be a release blocker. #2469 asks for adding a new flag which is good but upgrades should just work and does not require any additional flag to be specified if the services are shutdown properly.
  Issue #2472: pulp-manage-db does not clear the running worker flag even after the 300 seconds limit when upgrading

  When upgrading Pulp to 2.11 pulp-manage-db does not identify that worker are stopped for more than 300 seconds.
  The following output is from a RHEL7 system which has Pulp upgraded from Pulp 2.10:
  ~~~
  # systemctl status httpd pulp_...
• 
  elyezer This is an upgrade issue, running the reproducer script on a fresh 2.11 install works good:
  ~~~
  # ./2472_reproducer.sh
  +----------------------------------------------------------------------+
  Status of the ser...

  12:06 AM · Commented on issue