Skip to content

Pulp Community Release 18

Installation & Upgrade

Installation instructions can be found in the Pulp User Guide at the Pulp project web site. As usual, upgraded environments must run pulp-migrate to upgrade to the latest database changes.

Upgrade Database Migration

The pulp-migrate script might warn about repositories with the same relative paths. Relative paths need to be unique across repositories in Pulp. Please make sure to clean up these repositories as this functionality is deprecated and will be unsupported in upcoming releases.

Server Configuration

The configuration option:


has changed to:


This is in preparation for the administrator to “weight” tasks. Currently, the semantics of the property have not changed. Details can be found here on the weighted tasks design wiki.


The pulp consumer certificate location is now configurable. As part of this change, the default location was changed from:




to avoid collisions with RHSM certificates. After upgrading Pulp on consumer systems, the pulp-agent daemon must be restarted and the consumer re-registered. Alternatively, the certificate may be manually migrated to the new directory.

Features & Changes

  • Added support for package uninstallation through the API and CLI.
  • Added support for package group uninstallation through the API and CLI.
  • Enhanced progress reporting of repository synchronization. Progress is now reported on each individual item being downloaded.
  • Exporter (continued from last sprint):
    • Added Support for deltarpms and prestodelta metadata export.
    • Added ability to export repository groups to target location.
  • Distribution Enhancements:
    • Distributions now use a new id format: ks-$family-$variant-$version-$arch
    • New selective sync support to add and remove distributions between repositories.
    • Added new timestamp field to distribution model to capture when the treeinfo was last updated.
    • Pulp now stores distributions in a central location (/var/lib/pulp/distribution) for space optimization and to allow a distribution to be associated with multiple repositories.
    • The distribution relativepath to be path of the distro location.
    • The distribution URL will now use the repository’s relative path. A distribution can be associated to multiple repositories using same distribution ID.
  • Local Discovery: Support to discover repositories from a local file based URL paths.
  • Selective operations such as add/remove packages or errata on a repository will not automatically trigger a metadata generation task. Users need to manually trigger by calling the generate metadata on the repository after the associations are complete (pulp-admin repo generate_metadata).
  • Repository Notes: Repository notes are similar to key-value pairs on consumers. The ability to add, update and delete notes from a repository has been added. Repositories may also be queried on note data. For more information, see the repository section of the user guide.
  • Repo Synchronization Schedule
    • REST API changed to separate sync schedule management from repository creation and update. A new sub-collection has been added (/pulp/api/repositories/<id>/schedules/sync/) that accepts GET, PUT, and DELETE calls. Details can be found inthe repository section of the user guide.
    • The pulp-admin script has been changed to utilize the new REST API. Schedule creation and update are no longer part of the pulp-admin repo create and pulp-admin repo update actions. Repository scheduled syncs can now be viewed and managed with the pulp-admin repo sync action. The --help flag should be used for more details. Details can be found here: