Bug #19179
New packages are not synced from the katello to capsule even after a successful capsule sync.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1432649
Description of problem:
New packages are not synced from the katello to capsule even after a successful capsule sync.
How reproducible:
Was not able to reproduce locally
Steps to Reproduce:
Actual results:
Sync completes with out any error but no new content is available on capsule server.
~~
Id: 933e3a70-0f0d-47f0-852a-5bec45004f34
Label: Actions::Katello::CapsuleContent::Sync
Name: Synchronize capsule content
Owner: admin
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
State: stopped
Result: success
~~
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 -
~~
pulp:repository:DIB-Install-Meta_Capsule_7-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server
- pulp:action:sync
.
.
<SNIP>
.
.
details:
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
drpm_total: 0
drpm_done: 0
size_total: 0
size_left: 0
items_left: 0
~~
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.
Expected results:
Should sync the latest content on the capsule server.
Additional info:
Associated revisions
History
#1
Updated by John Mitsch about 5 years ago
- Subject changed from New packages are not synced from the katello to capsule even after a successful capsule sync. to New packages are not synced from the katello to capsule even after a successful capsule sync.
- Target version set to 181
#2
Updated by Eric Helms about 5 years ago
- Legacy Backlogs Release (now unused) set to 114
#3
Updated by Brad Buckingham about 5 years ago
- Target version changed from 181 to 187
#4
Updated by Brad Buckingham about 5 years ago
- Target version changed from 187 to 193
#5
Updated by Brad Buckingham about 5 years ago
- Target version changed from 193 to 196
#6
Updated by Brad Buckingham almost 5 years ago
- Target version changed from 196 to 202
#7
Updated by The Foreman Bot almost 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/6869 added
#8
Updated by Brad Buckingham almost 5 years ago
- Target version changed from 202 to 205
#9
Updated by John Mitsch almost 5 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|7fddb44d8b013a6b3e7ab0f5195ea5d05bc37398.
#10
Updated by Brad Buckingham almost 5 years ago
- Legacy Backlogs Release (now unused) changed from 114 to 281
#11
Updated by Eric Helms almost 5 years ago
- Legacy Backlogs Release (now unused) changed from 281 to 295
Fixes #19179 - Add force full sync to proxy syncs
This allows users to force full syncs on foreman proxies with
content. This is helpful when the packages on the katello
server do not match the packages on the fpc and the user
wants to force a sync of the repos