Pulp

04/14/2021

• 
  mmccune@redhat.com Pulp

  06:31 AM · Commented on issue

  jsherril@redhat.com wrote:
  > Today a user of pulp would have to manually request all tasks using a filter and then manually trigger a delete for each one. It would be much simpler if we could simply call an API and trigger a task that ... Story #8554: Provide easy task cleanup api

  Today a user of pulp would have to manually request all tasks using a filter and then manually trigger a delete for each one. It would be much simpler if we could simply call an API and trigger a task that would bulk delete all tasks ma...

07/29/2019

• 
  mmccune@redhat.com Docker Support

  10:26 PM · Commented on issue

  nice work on the optimization. IMO, the memory consumption for this call is a worthy tradeoff for the performance increases we are getting with your optimization. If you were quoting numbers in the 2-10G consumption I'd be concerned.
  Issue #4549: Removing docker manifests from a docker repository takes a long time

  Removing all docker manifests from a large docker repo seems to take a long time:
  \~300 manifests takes \~2 minutes
  \~2000 manifests takes \~30-40 minutes
  Reproducer:
  1\. Create and sync a docker repo such as: https://quay.io...

01/17/2018

• 
  mmccune@redhat.com Pulp

  05:12 PM · Commented on issue

  RPM only is completely acceptable
  Story #2619: Need a file-system integrity report for /var/lib/pulp

  In certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
  We have customers wh...

01/16/2018

• 
  mmccune@redhat.com Pulp

  06:47 PM · Commented on issue

  @bmbouter yes, exactly that. verify that the metadata matches the set of files in the published repository to ensure none are missing, corrupt or don't match the size/checksum
  Story #2619: Need a file-system integrity report for /var/lib/pulp

  In certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
  We have customers wh...

01/05/2018

• 
  mmccune@redhat.com Pulp

  04:48 PM · Commented on issue

  \+1 to the above report.
  Perhaps for the metadata corruption we could just list the path to each set of metadata that could be considered 'invalid' where it references things that don't exist or are corrupt.
  ..
  "invalid_metadata": \[... Story #2619: Need a file-system integrity report for /var/lib/pulp

  In certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
  We have customers wh...

10/17/2017

• 
  mmccune@redhat.com Pulp

  10:52 PM · Commented on issue

  Requirement: if we are going to be using a CLI tool, we will need to machine parse the output of the report in other tools so it would be required to have an option to output in JSON or CSV in the least. JSON preferable.
  Story #2619: Need a file-system integrity report for /var/lib/pulp

  In certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
  We have customers wh...

10/11/2016

• 
  mmccune@redhat.com Pulp

  09:04 PM · Commented on issue

  I'd like to bump the severity to High as it isn't obvious from the user perspective of the interaction between the two. Generally we would always recommend a full restart of Mongo goes down but it would be much more resilient if services... Issue #2331: The "unsafe_autoretry" feature does not retry with mongoengine.QuerySet codepaths

  If on a running pulp deployment you stop mongod, pulp_celerybeat will eventually die and produce the following log output, including a traceback.
  Instead, it should handle the connection failure gracefully and recover when mongod beco...

10/06/2016

• 
  mmccune@redhat.com Pulp

  06:37 PM · Commented on issue

  Ok, I think overall, cost/benefit guess makes it look like we all win if we just maintain this patch downstream as a NOOP for that migration file.
  If it is a patch to the RPM specfile + Patch#: stanza, that we can keep separate from our... Task #2323: Support skipping the standard storage path migration.

  In 2.8, pulp standardized how the platform determines where a content unit is stored under /var/lib/pulp/content. In the past, each plugin determined this on its own so it varied. To achieve consistency, a migration was added in 2.8 that...

10/05/2016

• 
  mmccune@redhat.com Pulp

  12:08 AM · Commented on issue

  can we at least have a flag of some sort that we could pass in to get the migration to NOOP?
  That would not require us to maintain a special patch, in perpetuity. I realize this puts a special consideration into the upstream code which ... Task #2323: Support skipping the standard storage path migration.

  In 2.8, pulp standardized how the platform determines where a content unit is stored under /var/lib/pulp/content. In the past, each plugin determined this on its own so it varied. To achieve consistency, a migration was added in 2.8 that...

08/02/2016

• 
  mmccune@redhat.com Pulp

  07:58 PM · Commented on issue

  This issue is blocking Satellite 6.1 -\> 6.2 upgrades, see:
  https://bugzilla.redhat.com/show_bug.cgi?id=1361196
  it requires manual intervention to skip certain upgrade steps and work around the issue. I'd mark this as highly severe/urg... Issue #2124: Pulp status check leaves open Pipes

  First monitor the current open files for the wsgi:pulp process, here will just pick teh first one:
  ~~~
  watch "lsof | grep `ps aux | grep wsgi:pulp\) | grep -v grep | awk '{print $2}' | head -n 1` | wc -l"
  ~~~
  Then hit the status ...