Pulp 2.19.1
Pulp 2.19.1 is now available in the stable repositories:
This release includes bugfixes for Debian Support, Docker Support, Pulp, and RPM Support.
Upgrading
The Pulp 2 stable repositories are included in the pulp repo files:
After enabling the pulp-stable or pulp-2-stable repository, you’ll want to follow the standard upgrade path with migrations:
$ sudo systemctl stop httpd pulp_workers pulp_resource_manager pulp_celerybeat pulp_streamer goferd
$ sudo yum upgrade
$ sudo -u apache pulp-manage-db
$ sudo systemctl start httpd pulp_workers pulp_resource_manager pulp_celerybeat pulp_streamer goferd
The pulp_streamer and goferd services should be omitted if those services are not installed.
Issues Addressed
Debian Support
Docker Support
Pulp
- 3098 Docker publish may fail with “OSError: [Errno 17] File exists” if two publishes triggered at same time
- 4581 Task Cancellation doesn’t interrupt/cancel a running task with Celery 4+
- 4603 pulp_streamer streams decodes responses, but sends the ‘gzip’ Content-Encoding header
- 4654 Modulemd profiles not getting removed from the consumer
RPM Support
- 4550 rpm_rsync_distributor is broken for yum_repo_metadata_file units
- 4617 Migration of modular content can fail (upgrade from <=2.16 to 2.17+)
- 4529 Broken repo can be published if zchunk metadata is not ignored at sync time
- 4560 Publish YumMetadataFiles as files and not symlinks
- 4627 Pulp does not resync yum metadata files on change
- 4644 Modular and RPM Errata Copy Documentation can be misleading of intended expected behavior
- 4661 incremental publish of yum_repo_metadata_repo fails after upgrade from 2.18/2.19 to 2-master
- 4692 syncing is broken on 2-master branch
- 4718 Module integrity is not preserved at copy time
- 4741 Migration of modular content fails for very old Fedora repos (upgrade from <=2.16 to 2.17+)