Re: [Pulp-list] [Feedback needed] Pulp 2 to Pulp 3 migration, export_distributor, RPM/ISO plugin

Tatiana Tereshchenko writes: > As you probably know, we are in the process of designing a tool which will > provide a way to migrate from Pulp 2 to Pulp 3, so we will ask you for > feedback every now and then. > > Export distributor [0] is used for generating ISO images which can contain > one

Re: [Pulp-list] RHEL 6 Server ISOs CDN channel problem?

>>>>> >>>>>> I'm seeing the following problem with the RHEL 6 Server ISOs Red Hat >>>>>> CDN channel since some time ~10 days ago. It seems like the channel is >>>>>> broken somehow or at least something is coming down that is confusing >>>>>> Pulp. All other ISO channels on Red Hat CDN for RHEL 5,6,7 >>>>>> Server,Workstation all seem to work fine. >>>>>> >>>>>> Here's what Pulp sees: >>>>>> >>>>>> https://paste.fedoraproject.org/paste/EzAQRp64UkoFaXdZOkjRLg >>>>>> >>>>>> If anyone else could please try out this CDN channel and report back >>>>>> with results, that would be much appreciated! >>>>>> >>>>>> Thanks! >>>>>> - Kodiak Firesmith, Pittsburgh -- Rohan McGovern ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp fails to sync rhel 7 server repo with repomd.xml not found error, but the optional packages repo syncs okay

Donald Wolfe writes: > I am having an issue with Pulp syncing the rhel 7 server repository, but a > similarly setup optional packages repository sync works. Does anyone have > any suggestions about what to do, or where to look? Any help would be > greatly appreciated. >

Re: [Pulp-list] Space needed by yum repo ISO exports

Rohan McGovern <rmcgo...@redhat.com> writes: > We use the export distributor in pulp_rpm[1] to export yum repositories > as ISOs. > > Sometimes, if many of these exports happen concurrently on the same > host, we find that the filesystem containing /var/lib/pulp/workin

[Pulp-list] Space needed by yum repo ISO exports

We use the export distributor in pulp_rpm[1] to export yum repositories as ISOs. Sometimes, if many of these exports happen concurrently on the same host, we find that the filesystem containing /var/lib/pulp/working runs out of space. Is anyone able to provide some estimate on the amount of

[Pulp-list] Pulp migration order

We're working on some custom Pulp migrations to fix up some data issues in our Pulp installation. https://docs.pulpproject.org/dev-guide/newtypesupport/plugin/migrations.html The migration mechanism has an annoying restriction: there aren't allowed to be any gaps in the migration sequence. For

Re: [Pulp-list] Clean uploaded but not imported content

Brian Bouterse writes: > I'm familiar with this limitation. You can manually delete them [0], but > there is nothing in Pulp which cleans these up automatically as far as I > know. > > Pulp does have a monthly maintenance [1] codepath which could also > delete unimported

[Pulp-list] Clean uploaded but not imported content

The pulp upload API docs [1] explain that uploading a unit to a repo is a 4 step process: 1. Make upload request 2. Upload the content (file) 3. Trigger importer(s), wait for their tasks to run 4. Delete upload request The process interacting with pulp's API might be prone to errors in steps 2