Bug 1810417

Summary: Ship a template that automates receptor configuration
Product: Red Hat Satellite Reporter: Marek Hulan <mhulan>
Component: Ansible - Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: egolov, ehelms
Target Milestone: 6.7.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_ansible-4.0.3.3, tfm-rubygem-foreman_ansible_core-3.0.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:38:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1763884    

Description Marek Hulan 2020-03-05 08:22:15 UTC
Description of problem:

For the FiFi we need to ship a job template people can use to deploy receptor on satellite box through REX. Such job template will require user to specify satellite user and password to use when calling using its API.


Steps to Reproduce:
1. go to Host -> Job templates
2. find "Connect Red Hat receptor controller" and click Run
3. fill in username and password of a user and run against satellite host


Expected results:

the run should succeed, you should be able to see at least one receptor process running afterwards


Additional info:

There must be at least one organization with valid manifest imported. The user needs to have required permissions.

Comment 8 Lukáš Hellebrandt 2020-03-26 10:24:11 UTC
Verified with Sat 6.7 snap 17. Receptor installation/configuration job template shipped as "Configure Cloud Connector".

Comment 10 Bryan Kearney 2020-04-14 13:38:49 UTC
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/RHSA-2020:1454