Project

Profile

Help

Issue #7105

closed

Applicability misreporting as [] for exactly one EL7 consumer

Added by iballou over 3 years ago. Updated over 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello, Pulp 2
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulp_rpm/2251":https://github.com/pulp/pulp_rpm/issues/2251


Related issue: https://pulp.plan.io/issues/6851

I had a number of Katello users fix their applicability issues by applying the patch that resulted from the issue above. However, a couple users are now reporting that there is always one client that isn't reporting applicability properly. The users report that the applicability changes over time. One host might start showing applicability again, but then another fails. Full details are in the following thread, starting at the linked message: https://community.theforeman.org/t/katello-3-15-doesnt-show-available-package-updates-anymore/18948/89

I suspect the issue is in Pulp because the package profiles and bound repositories are correct on the consumers that are exhibiting the applicability issue.

Pulp versions in use: pulp-server-2.21.2-1.el7.noarch pulp-rpm-plugins-2.21.2-1.el7.noarch (Plus https://github.com/pulp/pulp/pull/3990 patched in)

Actions #1

Updated by iballou over 3 years ago

I noticed there are more applicability-related fixes coming in 2.21.3, perhaps this could be fixed in that release? Maybe this bug fixes my issue https://pulp.plan.io/issues/6724

Actions #2

Updated by iballou over 3 years ago

One of the upstream users applied the patch, re-uploaded the package profile, and regenerated applicability. There is still one host with missing applicability, so I think this is a separate issue from the applicability ones within 2.21.3.

Actions #4

Updated by iballou over 3 years ago

This issue might be difficult to reproduce since the user recently reported that applicability started working again as new updates arrived. Seems like a transient problem. However, the user's (mainly @gvde) comments in the community thread should prove useful since the problems they've encounter are clearly documented.

Actions #5

Updated by fao89 over 3 years ago

  • Project changed from Pulp to RPM Support
Actions #6

Updated by ttereshc over 3 years ago

  • Triaged changed from No to Yes
Actions #7

Updated by pulpbot over 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF