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.
Bug 1991495 - Capsule is not synced automatically after repo sync/publish
Summary: Capsule is not synced automatically after repo sync/publish
Keywords:
Status: CLOSED DUPLICATE of bug 1982344
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.10.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-09 09:42 UTC by Vladimír Sedmík
Modified: 2021-08-09 16:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-09 16:51:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vladimír Sedmík 2021-08-09 09:42:36 UTC 
Description of problem:
The capsule is not synced automatically after new repo is created and synced despite the Administer > Settings > Content > Sync Capsules after Content View promotion is set to Yes.


Version-Release number of selected component (if applicable):
6.10.0 snap 10


How reproducible:
always


Steps to Reproduce:
1. Have a Satellite and a Capsule in the Library LCE
2. Create a new product and repo and sync it.


Actual results:
The repo is not synced to the capsule. I can see the "Sync Repository on Capsule(s)" task with 0 duration, but it is not followed by any "Synchronize capsule '<CAPS-FQDN>'" task and the content is not synchronized.


Expected results:
Content being automatically synchronized to the capsule.


Additional info:
Seems to be a regression since 6.9, where this works as expected.
Comment 2 Justin Sherrill 2021-08-09 16:51:58 UTC 

*** This bug has been marked as a duplicate of bug 1982344 ***
Note You need to log in before you can comment on or make changes to this bug.