jsherril@redhat.com
jsherril@redhat.com- Email: jsherril@redhat.com
- Registered on: 02/19/2015
- Last connection: 06/20/2017
Issues
- Assigned issues: 0
- Reported issues: 43
Projects
- Pulp (Private Access, 02/19/2015)
- RPM Support (Private Access, 02/19/2015)
- Puppet Support (Private Access, 02/19/2015)
- Docker Support (Private Access, 02/19/2015)
- Python Support (Private Access, 02/19/2015)
- Packaging (Private Access, 02/19/2015)
- Crane (Private Access, 02/19/2015)
- Puppet Deployment [deprecated] (Private Access, 02/19/2015)
- OSTree Support (Private Access, 02/19/2015)
- Debian Support (Private Access, 02/19/2015)
- Nectar (Private Access, 02/19/2015)
- OpenStack Support (Private Access, 02/19/2015)
- External (Private Access, 03/21/2017)
Activity
06/16/2017
-
The user in this case did do a force sync, skipping the metadata check. This did not seem to resolve the issue (and honestly given the issue I wouldn't expect it to).
I agree there isn't enough information to reproduce. Most every i... Issue #2820: No such file or directory: pkgtags.sqlite.gz on repository publishKatello user reported on pulp 2.9.3 hitting the following issue after syncing epel 7. Publishing the repo resulted in:
[Errno 2] No such file or directory: '/var/lib/pulp/content/units/yum_repo_metadata_file/72/c32e71f97dee222a4106ca...
06/14/2017
-
... Issue #2820: No such file or directory: pkgtags.sqlite.gz on repository publishKatello user reported on pulp 2.9.3 hitting the following issue after syncing epel 7. Publishing the repo resulted in:
[Errno 2] No such file or directory: '/var/lib/pulp/content/units/yum_repo_metadata_file/72/c32e71f97dee222a4106ca... -
Katello user reported on pulp 2.9.3 hitting the following issue after syncing epel 7. Publishing the repo resulted in:· Created issue
[Errno 2] No such file or directory: '/var/lib/pulp/content/units/yum_repo_metadata_file/72/c32e71f97dee222a4106ca...
06/06/2017
-
Issue #2797 (CLOSED - CURRENTRELEASE): Single consumer aplicability generation does not work unle...Recently the pulp team advised the katello team to start using the single consumer applicability generation api here:
POST /pulp/api/v2/consumers/UUID/actions/content/regenerate_applicability/
however this does not seem to work unl...
06/05/2017
-
Issue #2793 (NEW): applicable rpms only show up if at least one errata is applicableSteps to reproduce:
1) Register a consumer
2) create and sync a yum repository without errata (such as centos7 updates http://mirror.centos.org/centos/7/updates/x86_64/)
3) bind the consumer to repo 2)
4) ensure that at least one ...
04/25/2017
-
Issue #2727 (NEW): Updating importer with ssl_* options along with other options fails "Cannot up...Trying to update a repository's importer:
put "https://dev.example.com/pulp/api/v2/repositories/e7f93d88-a382-437f-a4d1-b48e6160c916/importers/yum_importer//"
and specifying some options such as remove_missing along with ssl_client...
03/06/2017
02/15/2017
-
Reopening as this is still an issue (tested on 2.10.3), i believe https://pulp.plan.io/issues/494 only really fixed it for syncs Issue #1389 (NEW): Disallow re-uploading the same package twicewhen pulp-admin is used for uploading rpm package that already published with same name, version and package version, but different sha and size, then yum install returns following error: ...
-
Katello is okay with this change. The result would be any tasks in katello that are assigned to a worker would no longer show as 'cancell'ed' forcing the user to resume them (or moving them to an errored state). I think this is better ... Issue #489: When a worker dies or restarts, work assigned to that worker is cancelledDescription of problem:
When a worker restarts (or dies) the tasks assigned to that worker get marked as cancelled. The cancelled state is correct, but users who dispatch work don't expect random cancelling of tasks so this isn't a gr...
12/21/2016
-
I wouldn't necessarily disagree if its argued that this is an invalid errata, however it shouldn't break applicability generation for the entire repo.
I could see arguments being made that it should be ignored or skipped during sync. Issue #2504: errata applicability fails if errata packagelist doesn't existIf you sync a repo with an errata that does not have a package list such as this one here:
https://github.com/Katello/runcible/blob/master/test/fixtures/repositories/zoo5/updateinfo.xml#L3-L9
and then try to generate applicability...
Also available in: Atom
.