mmccune@redhat.com
- Login: mmccune@redhat.com
- Email: mmccune@redhat.com
- Registered on: 02/19/2015
- Last connection: 04/14/2021
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 7 | 7 |
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
04/14/2021
-
jsherril@redhat.com wrote:
> Today a user of pulp would have to manually request all tasks using a filter and then manually trigger a delete for each one. It would be much simpler if we could simply call an API and trigger a task that ... Story #8554: Provide easy task cleanup apiToday a user of pulp would have to manually request all tasks using a filter and then manually trigger a delete for each one. It would be much simpler if we could simply call an API and trigger a task that would bulk delete all tasks ma...
07/29/2019
-
nice work on the optimization. IMO, the memory consumption for this call is a worthy tradeoff for the performance increases we are getting with your optimization. If you were quoting numbers in the 2-10G consumption I'd be concerned.
Issue #4549: Removing docker manifests from a docker repository takes a long timeRemoving all docker manifests from a large docker repo seems to take a long time:
\~300 manifests takes \~2 minutes
\~2000 manifests takes \~30-40 minutes
Reproducer:
1\. Create and sync a docker repo such as: https://quay.io...
01/17/2018
-
RPM only is completely acceptable
Story #2619: Need a file-system integrity report for /var/lib/pulpIn certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
We have customers wh...
01/16/2018
-
@bmbouter yes, exactly that. verify that the metadata matches the set of files in the published repository to ensure none are missing, corrupt or don't match the size/checksum
Story #2619: Need a file-system integrity report for /var/lib/pulpIn certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
We have customers wh...
01/05/2018
-
\+1 to the above report.
Perhaps for the metadata corruption we could just list the path to each set of metadata that could be considered 'invalid' where it references things that don't exist or are corrupt.
..
"invalid_metadata": \[... Story #2619: Need a file-system integrity report for /var/lib/pulpIn certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
We have customers wh...
10/17/2017
-
Requirement: if we are going to be using a CLI tool, we will need to machine parse the output of the report in other tools so it would be required to have an option to output in JSON or CSV in the least. JSON preferable.
Story #2619: Need a file-system integrity report for /var/lib/pulpIn certain cases due to historical issues with Satellite or on-going problems during content manipulation, there are situations where various inconsistencies can exist with the files contained within /var/lib/pulp
We have customers wh...
10/11/2016
-
I'd like to bump the severity to High as it isn't obvious from the user perspective of the interaction between the two. Generally we would always recommend a full restart of Mongo goes down but it would be much more resilient if services... Issue #2331: The "unsafe_autoretry" feature does not retry with mongoengine.QuerySet codepathsIf on a running pulp deployment you stop mongod, pulp_celerybeat will eventually die and produce the following log output, including a traceback.
Instead, it should handle the connection failure gracefully and recover when mongod beco...
06/13/2016
-
Issue #2005 (CLOSED - WORKSFORME): unable to use pulp-admin to publish rpm repository created with APIAttempting to publish a repo via pulp admin results in error:
~~~
pulp.server.async.tasks:INFO: Task failed : [e967dad0-8565-4232-ae4d-43e1864d9878]
celery.worker.job:ERROR: (26888-89504) Task pulp.server.managers.repo.publish.publi...
05/26/2016
-
Issue #1950 (CLOSED - CURRENTRELEASE): module upload fails with IOError: [Errno 2] No such file or directoryUploading this module here: http://mmccune.fedorapeople.org/jfryman-selinux-0.3.1.tar.gz causes this stack trace:
~~~
pulp_puppet.plugins.importers.importer:ERROR: (15938-61184) [Errno 2] No such file or directory: u'/var/lib/pulp/up...
04/14/2016
-
this is fairly severe in that it breaks a good porting of RHEL provisioning. moved to High severity
Issue #1843: Pulp publishes invalid PULP_DISTRIBUTION.xml metadataIf a repository contains a PULP_DISTRIBUTION.xml metadata file, it is possible for Pulp to re-publish it with invalid data. This causes a second Pulp server syncing from the first to fail. Specifically, files are referenced in the PULP_D...
Also available in: Atom
.