This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2170858 - [RFE] Support for external capsule\smart-proxy sync via Satellite\Foreman Ansible Collection
Summary: [RFE] Support for external capsule\smart-proxy sync via Satellite\Foreman Ans...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.12.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-17 12:58 UTC by Amit Agarwal
Modified: 2024-06-06 16:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:08:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-16360 0 None Migrated None 2024-06-06 16:08:10 UTC

Description Amit Agarwal 2023-02-17 12:58:50 UTC 
1. Proposed title of this feature request.

   Support for external capsule\smart-proxy sync via Satellite\Foreman Ansible Collection 

2. What are the nature and description of the request?

   The end-user needs to perform capsule sync using an ansible playbook instead of manual sync and even though we can create a playbook with command\URI module + hammer\API, It would be great to have an support ansible module within the satellite ansible collection that reduces the manual effort.  

3. Why do you need this? (List the business requirements here).

   Content Views publication or promotion creates a set of Capsule syncs so the end wants to stop automated sync and create one single capsule sync task  at the end of all publications/promotions and perform capsule sync using Ansible play instead of manual sync


4. How would you like to achieve this?

  We expect to have a different module created for smart_proxy_sync and supported through https://console.redhat.com/ansible/automation-hub/redhat/satellite/docs

5. Expected results:

The developed module should be able to mimic any behavior that the "hammer capsule content synchronize" can i.e. we should be able to sync an LCE, CV or even a Repo [ when the ID\name is properly used ]

6. Would you be able to assist in testing this functionality if implemented?
   Yes
Comment 2 ir. Jan Gerrit Kootstra 2023-02-23 18:35:28 UTC 
To add to point 6.

We have facilities to do alpha/beta testing and pre-prod testing.
Comment 4 Eric Helms 2024-06-06 16:08:11 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.