How to force a sync and validate the checksums of all content of a yum repository on Red Hat Satellite 6?

Environment

• Red Hat Satellite 6.9 and below versions
  • pulp-2

Issue

• Cannot obtain packages from Satellite and Capsule due to symbolic link issues.
• Getting 404 errors on clients connected to Satellite.

Resolution

• There are 2 ways to do this, via Satellite Web UI and using hammer CLI

  • From Red Hat Satellite WebUI

  Content →  Products →  <Product Name>  → Find the repository →  Click on the repository → Select Action  → 
  Advanced Sync → Choose Validate Content Sync →  Sync
  

  • To do the same using hammer CLI, run the command on Red Hat Satellite Server.:

  # hammer repository list 
  

  • Note the repository ID and then use it in the command below

  # hammer repository synchronize --async --validate-contents true --id  <ID>       <<< Replace the <ID> with the 
  numeric value of repository ID from the previous command 
  

• After the sync task finishes, a task to sync the new contents to Capsule is automatically triggered if not using any content view. However, it is possible to initiate a full sync manually.

• To sync the Capsule with all the content, Go to Satellite Web UI → Infrastructure → Capsules → Select the Capsule → Use the drop-down next to Synchronize → Run Complete Sync

For more KB articles/solutions related to Red Hat Satellite 6.x Repository Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Repository Issues.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.