Pulp

01/14/2020

• 
  rmcgover RPM Support

  06:45 AM · Commented on issue

  I'd like to point out that the workarounds probably are not as simple as it might seem at first glance:
  For the force_full suggestion, we need to minimize the number of force_full publishes triggered because they can be extremely slow... Issue #5951: yum_distributor wrongly skips publish after update of multi-repo errata

  When multi-repo errata are used, publishing a repo may skip with "Repository content has not changed since last publish", even if erratum units in the repo have been changed since last publish.
  h2. Steps to reproduce
  In summary: pu...

01/09/2020

• 
  rmcgover RPM Support

  06:02 AM · Created issue

  Issue #5951 (NEW): yum_distributor wrongly skips publish after update of multi-repo errata

  When multi-repo errata are used, publishing a repo may skip with "Repository content has not changed since last publish", even if erratum units in the repo have been changed since last publish.
  h2. Steps to reproduce
  In summary: pu...

11/13/2019

• 
  rmcgover Pulp

  02:00 AM · Created issue

  Task #5700 (NEW): $date operator doesn't work with $and, $or

  Pulp 2.x supports a "$date" operator extension for queries, documented here: https://docs.pulpproject.org/dev-guide/conventions/criteria.html#search-criteria
  This doesn't work in conjunction with mongo $and or $or operators. Such que...

11/04/2019

• 
  rmcgover RPM Support

  01:45 AM · Commented on issue

  Note also that if you have an iso_rsync_distributor attached to the same repo, attempting to publish with that distributor will fail as it attempts to rsync a nonexistent PULP_MANIFEST file. Issue #5659: Regression: publishing an empty ISO repo no longer publishes PULP_MANIFEST

  Publishing an ISO repo with no units will no longer publish an (empty) PULP_MANIFEST file.
  It seems to be a regression introduced by fast-forward publish support for ISO repos in version 2.20.0.
  h3. Steps to reproduce
  In dev-env...
• 
  rmcgover Publishing an ISO repo with no units will no longer publish an (empty) PULP_MANIFEST file.
  It seems to be a regression introduced by fast-forward publish support for ISO repos in version 2.20.0.
  h3. Steps to reproduce
  In dev-env...

  01:43 AM · Created issue
• 
  rmcgover RPM Support

  01:23 AM · Created issue

  Issue #5658 (MODIFIED): Copying modulemd_defaults over an uploaded unit fails: Not a directory

  Copying a modulemd_defaults unit from one repo to another, where a modulemd_defaults unit with the same "name" was formerly uploaded into the target repo, fails with "[Errno 20] Not a directory".
  h3. Steps to reproduce
  In dev env:
  ...

05/29/2019

• 
  rmcgover RPM Support

  06:25 AM · Commented on issue

  Yes, I couldn't reproduce it now as well.
  
  Actually, there still seems to be a closely related issue - corrupt repo can still be created if you put ISOs into the repo by copy, rather than direct upload. e.g. this process:
  * create... Issue #4856: Uploading ISOs of same name to a repo creates duplicates, makes repo unusable

  Uploading an ISO file into a repo which already contains an ISO of the same name, but with different content, will cause the repo to end up with multiple units of the same name. This breaks the repo, as PULP_MANIFEST will contain two en...

05/23/2019

• 
  rmcgover RPM Support

  03:10 AM · Commented on issue

  I think this is probably caused by https://pulp.plan.io/issues/4708 and related changes, and issue https://pulp.plan.io/issues/4856 being filed around the same time is just a coincidence.
  Specifically, commit d60bd2eaf581dec67d03b4646... Issue #4857: Pulp 2 Nightly Regression in test_iso_crud.ISOUpdateTestCase.test_all

  Problem Summary
  Testing of *test_iso_crud` in nightly CI in 2-master since May 16, 2019.
  Please see the test in Pulp-2-Tests for a good description of the test.
  Using pulp-smash shell or running the test through pulp-smash a...

05/21/2019

• 
  rmcgover RPM Support

  11:16 AM · Created issue

  Issue #4856 (CLOSED - NOTABUG): Uploading ISOs of same name to a repo creates duplicates, makes r...

  Uploading an ISO file into a repo which already contains an ISO of the same name, but with different content, will cause the repo to end up with multiple units of the same name. This breaks the repo, as PULP_MANIFEST will contain two en...

05/16/2019

• 
  rmcgover RPM Support

  04:09 AM · Commented on issue

  The workaround here if you need to update a yum_repo_metadata_file unit is:
  - first remove it from the repo
  - then clear orphans
  - then upload new one to the repo
  Clearing the orphans is needed because, even if you remove units f... Issue #4818: Updating a yum_repo_metadata_file unit silently does nothing

  Attempting to upload and import a yum_repo_metadata_file unit, to a repo which already has a unit with matching data_type, claims to succeed but silently does nothing.
  h3. Steps to reproduce
  (pulp-admin doesn't seem to support uplo...