Project

General

Profile

Bug #29933

Cannot see why redhat repo scanning failed

Added by Justin Sherrill 6 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Currently our redhat repo scanning uses Futures to spawn threads to scan the listing files for repositories. If this fails for some unknown reason, the future gobbles up the exception and we can't see what went wrong anywhere.

Associated revisions

Revision 394c8b6a (diff)
Added by Justin Sherrill 6 months ago

Fixes #29933 - log error when repo scan errors

with an unexpected exception

History

#1 Updated by The Foreman Bot 6 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/8728 added

#2 Updated by The Foreman Bot 6 months ago

  • Fixed in Releases Katello 4.0.0 added

#3 Updated by Justin Sherrill 6 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Justin Sherrill 6 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello 4.0.0

#5 Updated by Chris Roberts 4 months ago

  • Target version changed from Katello 4.0.0 to Katello 3.17.0

#6 Updated by Ian Ballou about 2 months ago

  • Target version changed from Katello 3.17.0 to Katello 3.16.1

Also available in: Atom PDF