Bug #19179

New packages are not synced from the katello to capsule even after a successful capsule sync.

Added by John Mitsch 23 days ago. Updated 3 days ago.

Status:New
Priority:High
Assigned To:John Mitsch
Category:Foreman Proxy Content
Target version:Team Brad - Iteration 14
Difficulty: Pull request:
Bugzilla link:1432649
Story points-
Velocity based estimate-
ReleaseBacklogRelease relationshipAuto

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:

History

#1 Updated by John Mitsch 23 days 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 Team Brad - Iteration 13

#2 Updated by Eric Helms 22 days ago

  • Release set to Backlog

#3 Updated by Brad Buckingham 3 days ago

  • Target version changed from Team Brad - Iteration 13 to Team Brad - Iteration 14

Also available in: Atom PDF