Pulp

06/23/2021

• 
  sajha Ansible Plugin

  08:27 PM · Closed issue

  Issue #8957 (CLOSED - CURRENTRELEASE): URL validation error on remote displays remote base URL instead of source url from requirements.

  The url validation is somehow leading to this: ["Invalid URL https://galaxy.ansible.com/. Ensure the URL ends '/'."]} This happens when I have some source specified in the requirements.yml without the trailing "/".. However the error dis...

02/22/2021

• 
  sajha Ansible Plugin

  07:00 PM · Closed issue

  Issue #8290 (CLOSED - CURRENTRELEASE): Pulp_ansible unable to sync from galaxy endpoint with token whereas ansible-galaxy client can

  Steps to reproduce:
  Set up a remote with a token and point to a galaxy instance.
  ~~~
  {
  "auth_url": null,
  "ca_cert": null,
  "client_cert": null,
  "client_key": null,
  "down...

09/17/2020

• 
  sajha Container Support

  08:03 PM · Closed issue

  Issue #7520 (CLOSED - NOTABUG): Pulp2 API import_upload endpoint with input of tag name and digest

  With pulp2 we were using the /actions/import_upload/ endpoint with params for tag name and digest for a manifest to tag a manifest. This is used in hammer today with pulp2 to upload tags.
  I am not aware of a similar flow with pulp3 an...

07/31/2020

• 
  sajha RPM Support

  03:46 AM · Closed issue

  Issue #7248 (CLOSED - CURRENTRELEASE): Copy API code still uses packagegroup relation for Package Environment

  A call to copy content between repositories hits this line which seems like an issue given the package group relation has been dropped from the Package Environment model.
  https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/tasks/c...

07/28/2020

• 
  sajha RPM Support

  05:42 PM · Closed issue

  Issue #7228 (CLOSED - CURRENTRELEASE): Optimized sync with mirror set to true unassociates all content units and creates an empty repository version

  

  Syncing a repository with Optimized sync set to true and mirror set to true unassociates all content units and creates an empty repository version. The progress report looks like the attached image.
  The first sync works fine. The subse...

07/27/2020

• 
  sajha Pulp

  05:20 PM · Commented on issue

  Cannot reproduce this on pulpcore 3.5.0 with pulpcore_client-3.5.0 gem or pulpcore_client-3.4.z gem on a katello box. Issue #6989: cert auth does not work with current binding gems

  Our pulp settings.py has these settings added:
  ~~~
  REMOTE_USER_ENVIRON_NAME = 'HTTP_REMOTE_USER'
  AUTHENTICATION_BACKENDS = ['pulpcore.app.authentication.PulpNoCreateRemoteUserBackend']
  REST_FRAMEWORK__DEFAULT_AUTHENTICATION_CLASS...

03/16/2020

• 
  sajha Pulp

  07:23 PM · Closed issue

  Issue #6347 (CLOSED - CURRENTRELEASE): File content list does not return all unique content units

  https://pulp-file.readthedocs.io/en/latest/restapi.html#operation/content_file_files_list does not return all unique content units when used with a page size of ~2000 and there are multiple pages of results.
  To reproduce:
  1. Create and...

03/10/2020

• 
  sajha Migration Plugin

  04:09 PM · Closed issue

  Issue #6314 (CLOSED - WONTFIX): Do not migrate schema1 docker manifests tied to docker tags that aren't migrated.

  Following https://github.com/pulp/pulp-2to3-migration/pull/110 , we could also filter out manifests associated to tags that weren't migrated.

03/09/2020

• 
  sajha Migration Plugin

  06:09 PM · Commented on issue

  Note that the progress report when hitting this issue did not capture this error.
  The progress report looked like below for me when I saw the error in my logs.
  ~~~
  {
  "count": 2,
  "next": null,
  "previous": null,
  "res... Issue #6084: Migration plugin error when trying to migrate the docker plugin with pulpcore 3.1+ and pulp_container >1.0

  Syncing only the docker plugin, and with only docker content in Pulp 2, using the plan
  ~~~
  http POST :24817/pulp/api/v3/migration-plans/ plan='{"plugins": [{"type": "docker"}]}'
  ~~~
  yields the error
  ~~~
  Feb 04 01:34:21 pulp2-...

03/06/2020

• 
  sajha RPM Support

  03:55 PM · Closed issue

  Issue #6295 (CLOSED - NOTABUG): Package in a different repo does not get added to package list on Module

  Steps to reproduce.
  1. Create and sync a modular repo with one of the packages in a module present in a different repo.
  I used https://dhcp-2-152.vms.sat.rdu2.redhat.com/pub/sajha/zoo5/ as the remote for the modular repo. Note that the...