On Red Hat Satellite 6 client installing a package returns 404 error despite the package being in metadata

Solution Verified - Updated -

Issue

  • Installing or upgrading a package to a client machine fails with HTTPS Error 404 - Not Found
  • Inspecting relevant repository on Satellite 6 server's /var/lib/pulp/published:

    • Metadata contains expected information about the package that is really intended to be present in the repo
    • The symlink to /var/lib/pulp/content is broken, even for a repository with Immediate download policy
    • The /var/lib/pulp/content contains the package of given filename.
  • Is there automated way of fixing symlinks so in case there are more such instances?

Environment

  • Red Hat Satellite 6.4 and above.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content