Pulp

09/29/2020

• 
  ggainey RPM Support

  06:50 PM · Edited issue

  Task #7537 (ASSIGNED): Add support for ALLOWED_CONTENT_CHECKSUMS

  The pulp_rpm should honor ALLOWED_CONTENT_CHECKSUMS. Some areas that might be affected (that I know of) include syncing (and verifying content), upload, and when publishing content.
• 
  ggainey Pulp

  06:35 PM · Commented on issue

  mdepaulo@redhat.com wrote:
  > How about we use the [systemd unit files to set the umask](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#UMask=) to 002?
  The problem with setting it outside code is, that umask can be... Issue #7445: Pulp2 overrides permissions set by pulp3

  Imagine you have pulp2 and some data( in this case i had only ISO content), then pulp3 gets installed.
  Write permission for the pulp group is granted and setgid is set [0] Issue comes when new content gets synced into pulp2( in this cas...
• 
  ggainey mdepaulo@redhat.com wrote:
  > How about we use the [systemd unit files to set the umask](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#UMask=) to 002?
  Interesting idea. We're explicitly setting umask for pulp-reso...

  02:42 PM · Commented on issue

09/28/2020

• 
  ggainey Pulp

  08:06 PM · Commented on issue

  Is the problem here *just* the leaf-node? If it's just the leaf-node, then we can 'fix' this just by insuring we directly chmod() the end-result to the perms we want/need/expect. If any/all internediate dirs need the permissions as well,... Issue #7445: Pulp2 overrides permissions set by pulp3

  Imagine you have pulp2 and some data( in this case i had only ISO content), then pulp3 gets installed.
  Write permission for the pulp group is granted and setgid is set [0] Issue comes when new content gets synced into pulp2( in this cas...
• 
  ggainey This isn't an installer or migration issue. What's happening here is that Pulp2 uses os.makedirs() to create new paths when syncing. makedirs(), even when mode= is specified, uses current-umask to set permissions (see the [os.makedirs](h...

  05:44 PM · Commented on issue

09/24/2020

• 
  ggainey Pulp

  02:27 PM · Edited issue

  Issue #7445 (ASSIGNED): Pulp2 overrides permissions set by pulp3

  Imagine you have pulp2 and some data( in this case i had only ISO content), then pulp3 gets installed.
  Write permission for the pulp group is granted and setgid is set [0] Issue comes when new content gets synced into pulp2( in this cas...

09/22/2020

• 
  ggainey RPM Support

  11:59 AM · Closed issue

  Applied in changeset commit:766f97d44c5fe28ff068ecc3547fc34239797669. Issue #7519 (MODIFIED): Tests rely on MD5 - Stop That

  See pulp_rpm/tests/functional/api/test_publish.py

09/18/2020

• 
  ggainey RPM Support

  07:43 PM · Committed changeset

  fixes #7519
  [nocoverage] Revision 766f97d4: Updated pulp_rpm tests to stop relying on md5 checksum.

09/17/2020

• 
  ggainey RPM Support

  07:01 PM · Closed issue

  Issue #7519 (CLOSED - CURRENTRELEASE): Tests rely on MD5 - Stop That

  See pulp_rpm/tests/functional/api/test_publish.py

09/16/2020

• 
  ggainey Pulp

  09:26 PM · Commented on issue

  Adding discussion from #pulp:
  ~~~
  <thm> just noticed that tasks will stay there until deleted. so, two questions: is there a way to remove old tasks in one go? and, should the examples in the doc be extended to delete successful tasks ... Story #7513: bulk-delete tasks

  Currently, tasks can only deleted one-at-a-time. It would be useful to have a way to bulk-delete tasks by state and/or by date range.
  In a follow-up discussion on #pulp it was proposed that task deletion could also be automatic, using...