paji@redhat.com
- Login: paji@redhat.com
- Email: paji@redhat.com
- Registered on: 02/19/2015
- Last connection: 07/13/2022
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 1 | 1 |
| Reported issues | 0 | 71 | 71 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Container Support | Private Access | 12/06/2019 |
| Crane | Private Access | 02/19/2015 |
| Debian Support | Private Access | 02/19/2015 |
| Docker Support | Private Access | 02/19/2015 |
| File Support | Private Access | 07/17/2017 |
| Migration Plugin | Private Access | 01/14/2020 |
| Nectar | Private Access | 02/19/2015 |
| OSTree Support | Private Access | 02/19/2015 |
| Packaging | Private Access | 02/19/2015 |
| Pulp | Private Access | 02/19/2015 |
| Puppet Support | Private Access | 02/19/2015 |
| Python Support | Private Access | 02/19/2015 |
| RPM Support | Private Access | 02/19/2015 |
Activity
08/05/2021
-
Story #9214 (CLOSED - DUPLICATE): Need a `dry-run` option for export similar to imports
**Ticket moved to GitHub**: "pulp/pulpcore/2082":https://github.com/pulp/pulpcore/issues/2082
----
Pulp provides a nice dry run api when importing that cheks things like
* Importing archive files are in the right plac...
04/26/2021
-
Connected to -> https://projects.theforeman.org/issues/32421 Issue #8628: Need better error message on invalid chunk-size for exportThe chunking parameter in the export call is unable to handle super large files. There is a possibility that the user may accidentally give bytes for megabytes. We need pulp to fail more gracefully for unreasonable values.
Try to exp... -
The chunking parameter in the export call is unable to handle super large files. There is a possibility that the user may accidentally give bytes for megabytes. We need pulp to fail more gracefully for unreasonable values.· Closed issue
Try to exp...
01/18/2021
-
Also uploading my tgz Issue #8116: pulp-import relying on 'next_version' in ways it can't, causing import to fail.* Create a repo
* upload a package -> this should generate version 1
* remove a package -> this should generate version 2
* optionally upload another package -> this should generate version 3
* Now export version 1
* copy and extrac... -
* Create a repo· Closed issue
* upload a package -> this should generate version 1
* remove a package -> this should generate version 2
* optionally upload another package -> this should generate version 3
* Now export version 1
* copy and extrac...
01/13/2021
-
ggainey wrote:
> daviddavis jsherril@redhat.com paji@redhat.com - I am working on implementing this for Pulp3.10, and need a final agreement on the API and what we check.
>
> **Details**:
> * Proposed API is `GET /pulp/api/v3/import... Issue #7549: Need a dry run option for import/export apiKatello checks things like
* Is the import path exists
* Does it have the right permissions
It would be ideal if pulp provided a dry-run operation for import and export operations. Katello can then use that to figure out the correc...
10/21/2020
-
https://pulp.plan.io/issues/7716
(cherry picked from commit 8b1531c8e2086fe2febdae47bde22b5defae2cf3)
[noissue] Revision c03ac347 (pulpcore): Incremental export to happen if start_version provided, even if last_export is null -
Applied in changeset commit:pulpcore|8b1531c8e2086fe2febdae47bde22b5defae2cf3. Issue #7716 (MODIFIED): Incremental export not happening if last export was null even if start_version is providedKatello needs to be able to control the versions being exported. Pulp 3 introduced the start_versions and versions exporting for incremental in https://pulp.plan.io/issues/6763 . This api seems to do the correct thing, however it assumes...
-
10/20/2020
Also available in: Atom
.