Bug #31620: Package matching query does not exist - Katello - Foreman

Custom queries

All issues closed in the last 3 weeks
Assigned to me
Closed Issues without Release
Easy and Trivial Issues
Good first issues - Foreman core
Katello 4.14.1 TODO
Mine
My issues closed in the last 3 weeks
open docker issues 2.1
Open Features
Open Katello issues by target version
Open Pull Requests
Stale
Trackers
Untriaged
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #31620

closed

Package matching query does not exist

Added by Riaan Pretorius over 3 years ago. Updated over 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Repositories

Target version:

Katello Recycle Bin

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Katello 3.18.1

Red Hat JIRA:

Description

Good Day,

I keep getting this error using the katello plugin -> "*Package matching query does not exist*."

From what i can gather or guess is that the upstream provider has a missing package not part of their repo or repo index is messed up.

This has been asked before, but no one seems to know how to fix it. Is there any way this can be skipped and download the remainder of the packages instead of failing the task?

Al i can think of as a work around is to use reposync and create another local repo then import that into katello. But that would be duplication and a waste of disk space and defeats the purpose of katello.

Files

trace.log	trace.log	13.7 KB		Eric Fehr, 02/23/2021 04:18 AM
latest.log	latest.log	99 KB		Eric Fehr, 02/23/2021 05:17 AM

History
Notes
Property changes

Actions

Copy link

Updated by Lukas Zapletal over 3 years ago

Project changed from Foreman to Katello
Subject changed from Katello Plugin to Package matching query does not exist
Category deleted (~~Plugin integration~~)
Priority changed from High to Normal

Actions

Copy link

Updated by Jonathon Turel over 3 years ago

Category set to Repositories
Status changed from New to Need more information
Difficulty deleted (~~easy~~)

Hi Riaan,

Can you tell us which version of Katello you're running and point us to the repo URL so we can try to sync and see the problem you're running into?

Thank you

Actions

Copy link

Updated by Riaan Pretorius over 3 years ago

Category deleted (~~Repositories~~)

Jonathon Turel wrote:

Hi Riaan,

Can you tell us which version of Katello you're running and point us to the repo URL so we can try to sync and see the problem you're running into?

Thank you

Hi Jonathon,

These are my package versions:

katello-selinux-3.5.0-1.el7.noarch
katello-common-3.18.1-1.el7.noarch
katello-default-ca-1.0-1.noarch
katello-repos-3.18.1-1.el7.noarch
katello-certs-tools-2.7.3-1.el7.noarch
tfm-rubygem-katello-3.18.1-1.el7.noarch
katello-3.18.1-1.el7.noarch
foreman-installer-katello-2.3.1-1.el7.noarch
katello-client-bootstrap-1.7.5-1.el7.noarch
tfm-rubygem-hammer_cli_katello-0.24.2-1.el7.noarch
pulp-katello-1.0.3-1.el7.noarch
katello-debug-3.18.1-1.el7.noarch
katello-server-ca-1.0-1.noarch

OS: Centos 7

These are the repo's it fails on. I have the full centos list of repo's and they all sync no issues. Just these 2 don't. Been running this server for 2 weeks now testing the sync and these 2 fail consistently . The old repo server is using plain old reposync and does work. have not checked yet if there is issue there that we are not aware of when it syncs.

https://yum.oracle.com/repo/OracleLinux/OL7/9/base/x86_64/
https://yum.oracle.com/repo/OracleLinux/OL7/latest/archive/x86_64/

Actions

Copy link

Updated by Chris Roberts over 3 years ago

Category set to Repositories
Status changed from Need more information to New
Target version set to Katello 4.1.0
Triaged changed from No to Yes

Actions

Copy link

Updated by Eric Fehr over 3 years ago

Found in Releases Katello 3.18.1 added

Riaan Pretorius wrote:

OS: Centos 7

These are the repo's it fails on. I have the full centos list of repo's and they all sync no issues. Just these 2 don't. Been running this server for 2 weeks now testing the sync and these 2 fail consistently . The old repo server is using plain old reposync and does work. have not checked yet if there is issue there that we are not aware of when it syncs.

[...]

I am getting the same issue with these repos above (OL7 latest, OL7.9 Base), also on Centos 7 x86, katello-3.18.1-1.el7.noarch, foreman-2.3.2-1.el7.noarch

The issue is a blocker to the deployment of Foreman in my case and transitioning off of Spacewalk, as not being able to sync _latest defies the whole point of system management.

I would speculate that the repo metadata is corrupt in some way, but would suggest that in this scenario it should continue and skip the package in question, rather than terminating the sync.

Actions

Copy link

Updated by Eric Fehr over 3 years ago

File trace.log trace.log added

Actions

Copy link

Updated by Eric Fehr over 3 years ago

Collisions are occurring anywhere I have a _base repo in conjunction with a _latest repo. Speculation is that packages occur in both when the _latest is the same as the _base, and this is throwing the exception. Not sure how that should be handled by the back end, but probably better than failing to sync. I've removed all my _base repos and am re-creating the _latest and will re-run a sync and report back.

Actions

Copy link