Pulp

08/05/2021

• 
  daviddavis Pulp

  09:41 AM · Committed changeset

  Most repos have branch protection rules against [0-9].[0-9]* which
  prevents us from deleting x.x.x-changelog branches after they are
  merged.
  [noissue] Revision 419011f9 (plugin_template): Change the cherry pick changelog branch name

08/03/2021

• 
  daviddavis Pulp

  08:40 PM · Closed issue

  Applied in changeset commit:pulpcore|32c12013f232465f52713373ad7ce092a3a2b409. Task #8860 (MODIFIED): Move FilesystemExporter out of plugin API into pulpcore

  FilesystemExporter suffers [the same problem as Distributions once did](https://pulp.plan.io/issues/8383).
  The inheritance looks like this:
  ```
  Exporter -> FilesystemExporter -> FileFilesystemExporter
  ```
  Where `Exporter` is t...
• 
  daviddavis Pulp

  08:39 PM · Committed changeset

  fixes #8860 Revision 32c12013 (pulpcore): Move FilesystemExporter into core
• 
  daviddavis Pulp

  02:27 PM · Created issue

  Issue #9200 (POST): pulp_installer creates the db encryption key after the db is migrated

  Background here: https://github.com/pulp/pulpcore/pull/1301#discussion_r680329425
  pulp_installer currently creates the db key when setting up the pulp-api service:
  https://github.com/pulp/pulp_installer/blob/cd93e99687684056412ae75...
• 
  daviddavis Pulp

  10:44 AM · Closed issue

  Discussed today at triage. We resolved the original problem in the CLI and adding a new section with dupe data would be confusing for users so we agreed to close this out. Issue #9084 (CLOSED - WONTFIX): Confusion around component versions

  The status api reports the following:
  ```
  "versions": [
  {
  "component": "core",
  "version": "3.15.0.dev"
  },
  {
  "component": "python",
  "version": "3.5.0.dev"
  }
  ```
  This has let to som...
• 
  daviddavis Pulp

  09:57 AM · Commented on issue

  @mcorr, can you be more explicit about what sorts of checks might benefit users?
  Also, today during our pulpcore meeting we discussed relying on the status api (accessible at /pulp/api/v3/status/ and via the `pulp status` CLI command)... Task #9150: As a Pulp user, I want to validate that my setup is working

  This has been reported in the Pulp Community Survey as a concern that some "Checks" documentation would help alleviate.
  "how do I validate my setup is working." ... I've written my own checkout test cases to address this because it w...
• 
  daviddavis Pulp

  09:00 AM · Edited issue

  Task #8960 (NEW): Ensure that pulp imports can run concurrently with orphan cleanup

  I've [confirmed](https://github.com/pulp/pulpcore/pull/1367#issuecomment-861757194) that when an import happens, it bumps the timestamp_of_interest for artifacts and content so that when the import gets to the repository version creation...

08/02/2021

• 
  daviddavis Pulp

  08:33 PM · Committed changeset

  Fixing the CI release test job which installs pulp-2to3-migration as a
  package (instead of the project files). So we need to use
  /etc/pulp/settings.py.
  [noissue]
  (cherry picked from commit 0867a81f2708a51d6d51f1a1390c05393a13b032) Revision 89dbace8 (pulp-2to3-migration): Fix CI release job by updating /etc/pulp/settings.py
• 
  daviddavis Pulp

  12:42 PM · Committed changeset

  Fixing the CI release test job which installs pulp-2to3-migration as a
  package (instead of the project files). So we need to use
  /etc/pulp/settings.py.
  [noissue] Revision 0867a81f (pulp-2to3-migration): Fix CI release job by updating /etc/pulp/settings.py

07/30/2021

• 
  daviddavis Pulp

  02:19 PM · Committed changeset

  [noissue] Revision 74a06621 (plugin_template): Fixing update ci files workflow