jsherril@redhat.com
- Email: jsherril@redhat.com
- Registered on: 02/19/2015
- Last connection: 04/06/2021
Issues
- Assigned issues: 0
- Reported issues: 188
Projects
- Pulp (Developer, Private Access, Contributor, 02/19/2015)
- RPM Support (Developer, Private Access, Contributor, 02/19/2015)
- Puppet Support (Developer, Private Access, Contributor, 02/19/2015)
- Docker Support (Developer, Private Access, Contributor, 02/19/2015)
- Python Support (Developer, Private Access, Contributor, 02/19/2015)
- Packaging (Developer, Private Access, Contributor, 02/19/2015)
- Crane (Developer, Private Access, Contributor, 02/19/2015)
- OSTree Support (Developer, Private Access, Contributor, 02/19/2015)
- Debian Support (Developer, Private Access, Contributor, 02/19/2015)
- Nectar (Developer, Private Access, Contributor, 02/19/2015)
- File Support (Developer, Private Access, Contributor, 07/17/2017)
- Ansible Plugin (Developer, Contributor, 02/19/2019)
- Maven Plugin (Developer, 09/18/2019)
- 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
04/06/2021
-
Issue #8512 (CLOSED - DUPLICATE): deb repo - apt install - File has unexpected size - http pipelineA katello user opened this: https://projects.theforeman.org/issues/32178
I'm getting unexpected size error on ubuntu 18.04 when trying to install from a deb repository.
The problem seems to be caused by apt pipelining requests.
... -
Opened a bug for apt for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626
Managed to reproduce the issue with bionic, focal, and hirsute.
Turns out apt relies on "Size" field from "Packages" file... -
I'm getting unexpected size error on ubuntu 18.04 when trying to install from a deb repository.
The problem seems to be caused by apt pipelining requests.
... -
Issue #8511 (NEW): syncing deb repo with invalid/incorrect gpg key produces "No valid Release file found" errorA katello user reported this: https://projects.theforeman.org/issues/32145
which seemed like a purely pulp issue.
"Error doesn't make it clear that the issue with Release integrity check failing, or that key is invalid.
There is ...
03/25/2021
-
~~~
What if RepoVersion 0 is the only RepoVersion?
~~~
i would think a Repository should always have at least 1 version and instead of blocking deletion of version 0, we just block if there is only 1 version? Story #8454: As a user, I can't delete RepositoryVersion.number==0## Current State
You cannot delete version 0. That is enforced int the code [here](https://github.com/pulp/pulpcore/blob/348c654567067fb24bc13fa5105628433fb911fb/pulpcore/app/viewsets/repository.py#L222-L223).
## Proposal
Allow ...
03/11/2021
-
Issue #8393 (CLOSED - DUPLICATE): correlation id messages pollute log filesBy default when running pulpcore 3.9 or later, if you do not specify a correlation id in a request you will see in the log:
django_guid:INFO: Header `Correlation-ID` was not found in the incoming request. Generated new GUID: 2e1c2346...
03/09/2021
02/03/2021
-
The user did confirm that they deleted repos in between migrations Issue #8195: NoneType' object has no attribute 'cast on metadata_checksum_type~~~
NoneType' object has no attribute 'cast
"traceback": " File \"/usr/lib/python3.6/site-packages/rq/worker.py\", line 936, in perform_job
rv = job.perform()
File \"/usr/lib/python3.6/site-packages/rq/job.py\", line 684, ... -
This came from this katello support post https://community.theforeman.org/t/pulp-3-migration-fails-after-upgrade-to-katello-3-17/22192/8 Issue #8200: ValueError: invalid literal for int() with base 10 during migration (likely treeinfo related)~~~
ValueError: invalid literal for int() with base 10: '1601956550.79'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/rq/worker.py", line...
Also available in: Atom