Project

Profile

Help

Issues

Filters

Apply Clear

# Project Tracker Status Priority Severity Subject Author Assignee Triaged Tags
4190 Container Support Issue NEW Normal 2. Medium Tag names starting with `sha256:` could cause collisions amacdona@redhat.com Yes Actions
8564 File Support Issue NEW Normal 2. Medium The help text for repository on distribution doesn't make sense daviddavis Yes Documentation Actions
9231 RPM Support Issue POST Normal 2. Medium The interaction of skip_types and mirror=True is unintuitive dalley dalley Yes Actions
9533 NPM Plugin Issue NEW Normal 2. Medium The npm plugin is currently incompatible with dispatch call of pulpcore >= 3.15 mdellweg No Actions
6905 Pulp Issue NEW Normal 2. Medium The pr processor sets issues to POST that are associated with "ref" (eg "ref #1234") daviddavis Yes Actions
7892 Pulp Issue ASSIGNED Normal 2. Medium the task "Ensure pulp is part of group redis" doesn't need to create its home directory tsugimur@redhat.com mdepaulo@redhat.com No Actions
6683 Migration Plugin Issue NEW Normal 2. Medium treeinfo file missing from publication after a migrated kickstart is synced in pulp 3 dkliban@redhat.com Yes Actions
5842 Pulp Issue NEW Normal 2. Medium Trying to sync (and other operations) an X plugin repository with a Y plugin remote does not immediately fail dalley Yes Actions
6538 Debian Support Issue NEW Normal 2. Medium Unable to create ReleaseArchitecture or ReleaseComponent via the API lieter No Actions
5352 File Support Issue NEW Normal 2. Medium Unable to sync using SSL certs from distribution with cert-guards kersom Yes Actions
9048 Ansible Plugin Issue NEW Normal 2. Medium Update imports API in v3 newswangerd No GalaxyNG Actions
8791 Pulp Issue NEW Normal 2. Medium Usability of "fields" when querying rpm content types wibbit Yes Actions
6902 Debian Support Issue NEW Normal 2. Medium Use postgres deb version compare function quba42 No Actions
8000 Pulp Issue NEW Normal 2. Medium user improperly authenticated via valid cert gw0101 Yes Pulp 2 Actions
6130 Pulp Issue NEW Normal 2. Medium Users have a tendency to run /usr/local/bin/pulp-content in production mdepaulo@redhat.com Yes Actions
9211 Pulp Issue NEW Normal 2. Medium Vagrant devel installs have SELinux errors mdepaulo@redhat.com Yes Dev Environment, SELinux Actions
7734 Ansible Plugin Issue NEW Normal 2. Medium Validate the requirements.yml file daviddavis No Actions
9237 Debian Support Issue NEW Normal 2. Medium Very slowly publication and progress report wilful No Actions
489 Pulp Issue NEW Normal 2. Medium When an task worker dies or restarts, work assigned to that worker is cancelled bcourt Yes Actions
8055 Pulp Issue NEW Normal 2. Medium When SELinux is enabled, pulp_installer relabels all the files in /var/lib/pulp dkliban@redhat.com Yes Actions
4215 RPM Support Issue NEW Normal 2. Medium When uploading an invalid rpm such as a non utf8 RPM, users should get a friendly error message kersom Yes Actions
9527 Pulp Issue NEW Normal 2. Medium Wrong artifact storage path in the pulpcore docs quba42 Yes Documentation Actions
5346 Ansible Plugin Issue NEW Normal 2. Medium Wrong url resolution when path is the last component of prefix osapryki Yes Actions
8176 RPM Support Issue NEW Normal 2. Medium Yum groups in comps.xml broken jdjeffers Yes Pulp 2 Actions
9205 RPM Support Issue NEW Normal 2. Medium yum_distributor publish succeeds even when signing fails rmcgover Yes Pulp 2 Actions
(701-725/738) Per page: 25, 50, 100

Also available in: Atom CSV PDF

Please register to add an issue