After rhnpush or clone errata to custom channel, satellite cache generation takes a long time

Solution Verified - Updated -

Issue

  • After upgrading to RHN Satellite 5.3 or later, yum is slow to see new packages on client systems.
  • RHN Satellite slow to make packages available
  • After rhnpush or clone errata to custom channel, cache generation on Satellite 5.3 or later is taking a long time
  • Installation of a updated package version is scheduled in Satellite for a system.
    rhn_check checks, does not install the new version but the event is marked as successful

Environment

  • Red Hat Network Satellite 5.3 or later

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.