ggainey
- Registered on: 05/15/2019
- Last connection: 01/13/2021
Issues
- Assigned issues: 5
- Reported issues: 56
Projects
- Pulp (Developer, Private Access, Contributor, 05/16/2019)
- RPM Support (Developer, Private Access, Contributor, 05/16/2019)
- Puppet Support (Developer, Private Access, Contributor, 05/16/2019)
- Docker Support (Developer, Private Access, Contributor, 05/16/2019)
- Python Support (Developer, Private Access, Contributor, 05/16/2019)
- Packaging (Developer, Private Access, Contributor, 05/16/2019)
- Crane (Developer, Private Access, Contributor, 05/16/2019)
- OSTree Support (Developer, Private Access, Contributor, 05/16/2019)
- Debian Support (Developer, Private Access, Contributor, 05/16/2019)
- Nectar (Developer, Private Access, Contributor, 05/16/2019)
- File Support (Developer, Private Access, Contributor, 05/16/2019)
- Ansible Plugin (Developer, Contributor, 05/16/2019)
- Maven Plugin (Developer, 09/18/2019)
- Pulp CLI (Developer, Contributor, 05/07/2020)
- CertGuard (Developer, Contributor, 04/06/2020)
- Container Support (Developer, Private Access, Contributor, 12/06/2019)
- NPM Plugin (Developer, Contributor, 05/11/2020)
- Migration Plugin (Developer, Private Access, Contributor, 01/14/2020)
Activity
01/21/2021
01/20/2021
-
[noissue]
(cherry picked from commit 922fe5c6eead35ff72730976d7138734fdd255be) Revision affdc8f4: Added release notes for pulp-2.21.5 release. -
[noissue]
(cherry picked from commit 2a1b28b72b2517f7aac9dc3a05e650457aa81ffa) Revision 4fb240bd (pulp): Added release notes for pulp-2.21.5 release. -
-
-
01/19/2021
-
-
Issue #7549 (ASSIGNED): 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...
01/18/2021
-
Applied in changeset pulp:commit:pulp-2to3-migration|cfec44afef40ac844ca64c45e5f115ce30a5f8df. Issue #7781 (MODIFIED): In case of any issues in the middle of pre-migration, migration re-run doesn't pick up all the needed content.If I cancel a task at pre-migration stage or if there is a failure at pre-migration time, the next migration re-run won't continue properly. It will skip content based on its last_updated timestamp.
We need to pre-migrate content orde...
Also available in: Atom