Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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:
Hey Saikumar,
The only workarounds that currently exist so far are the ones mentioned above. We are looking into more permanent solutions and alternative workarounds currently.
-John
Comment 15Satellite Program
2017-07-26 18:12:12 UTC
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.
https://access.redhat.com/errata/RHBA-2017:2803
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 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: