Description of problem:
New packages are not synced from the satellite to capsule even after a successful capsule sync.
Version-Release number of selected component (if applicable):
Satellite 6.2.7 and capsule 6.2.7
Was not able to reproduce locally
Steps to Reproduce:
Sync completes with out any error but no new content is available on capsule server.
Name: Synchronize capsule content
Execution type: Delayed
Start at: 2017-02-14 16:26:53 UTC
Start before: -
Started at: 2017-02-14 16:26:54 UTC
Ended at: 2017-02-14 16:37:00 UTC
In capsule sync task, if we open any "Actions::Pulp::Consumer::SyncCapsule (success) " task we canclearly see that the sync is succesfully but no new packages are copied over the capsule server.
For example -
rpm_total: 0 <<--- Count Remains 0 even there are new packages are available to sync
rpm_done: 0 <<--- Count Remains 0 even there are new packages are available to sync
If we check the /var/lib/pulp/published/yum/master/yum_distributor/ the repository name is identical on both side. But if we check the symlinks and the metadata on capsule server, we can see that the directory still contains the old data.
Also, locate or find command for package search on file system does not yield any result.
Should sync the latest content on the capsule server.
Created redmine issue http://projects.theforeman.org/issues/19179 from this bug
The only workarounds that currently exist so far are the ones mentioned above. We are looking into more permanent solutions and alternative workarounds currently.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19179 has been resolved.
Verifed on satellite-6.2.12-1.0.el7sat.noarch. After syncing the capsule content, the packages synced in the associated LC env can be found in /var/lib/pulp... repositories on capsule.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.