Project

Profile

Help

Issue #1008

closed

Package Missing from repo metadata

Added by Ben.Stanley over 7 years ago. Updated almost 4 years ago.

Status:
CLOSED - WONTFIX
Priority:
High
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.6.1
Platform Release:
OS:
RHEL 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

I have a problem with syncing
http://elrepo.org/linux/elrepo/el7/x86_64

It seems that the package
nvidia-x11-drv-304xx-304.125-1.el7.elrepo.x86_64.rpm
is not included in my yum metadata. However, it is published in my local
repo.

[root stig ]# yum list nvidia-x11-drv-304xx
Loaded plugins: langpacks, product-id, subscription-manager
Available Packages
nvidia-x11-drv-304xx.x86_64
304.123-2.el7.elrepo elrepo

Only the older version 304.123-2 of the package is found, despite the newer 304.125-1 being published in the repo.

When I change my /etc/yum.repos.d/elrepo.repo to point to upstream instead
of my local pulp server, yum finds the correct nvidia-x11-drv-304xx (after
yum clean metadata).

I have recently run a sync, but it has not fixed the problem. There is
nothing interesting in the log (no exceptions or errors).

I am running pulp 2.6.1 (package versions below).

I have found that I can fix this kind of problem by deleting the repo and
re-creating it, but I need to get to the bottom of this so that it stops
happening. I have complained about something like this previously in
pulp-2.5.1 at [0] . I created my elrepo in pulp-2.6.1, so it is not
possible to blame an older version of pulp this time.

I need to get to the bottom of this, and hopefully get this resolved
properly. Otherwise, I look like a goose when my local copy doesn't work.

I need to know that after I have completed a sync, that everything really
is OK, before I sync to my disconnected system. Performing a complete
internet sync takes a long time, and a disconnected sync is going to be
even worse. I want to prove that everything is right before I do the
disconnected sync.

Questions:
1) Is there a tool that I can use to compare the metadata of two repos and
determine equivalence (at least to the point of validating the sync)? Such
a tool would allow me to proactively detect such problems, and attempt to
correct them. It would also provide more test cases for you...

2) Is there some way of investigating why this particular file isn't
appearing in the metadata?

================= rpm -qa | grep pulp ==========================
python-pulp-common-2.6.1-1.el7.noarch
pulp-rpm-admin-extensions-2.6.1-1.el7.noarch
pulp-server-2.6.1-1.el7.noarch
python-pulp-client-lib-2.6.1-1.el7.noarch
python-pulp-puppet-common-2.6.1-1.el7.noarch
pulp-puppet-plugins-2.6.1-1.el7.noarch
pulp-admin-client-2.6.1-1.el7.noarch
python-isodate-0.5.0-4.pulp.el7.noarch
python-kombu-3.0.24-5.pulp.el7.noarch
pulp-rpm-plugins-2.6.1-1.el7.noarch
python-pulp-bindings-2.6.1-1.el7.noarch
pulp-puppet-admin-extensions-2.6.1-1.el7.noarch
python-pulp-rpm-common-2.6.1-1.el7.noarch
pulp-selinux-2.6.1-1.el7.noarch
================================================================

[0] https://pulp.plan.io/issues/942


Files

Also available in: Atom PDF