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.

Bug 1842900

Summary: ERROR! the role 'satellite-receptor' was not found in ...
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: RH Cloud - Cloud ConnectorAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: aruzicka, egolov
Target Milestone: 6.8.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_ansible-5.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:03:08 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:

Description Lukáš Hellebrandt 2020-06-02 11:08:14 UTC
Description of problem:
When running "Connect red hat receptor controller" job (used to be "configure cloud connector" in 6.7), I get:

```
ERROR! the role 'satellite-receptor' was not found in /tmp/d20200602-64618-hrsoqy/project/roles:/etc/ansible/roles:/usr/share/ansible/roles:/tmp/d20200602-64618-hrsoqy/project
The error appears to have been in '/tmp/d20200602-64618-hrsoqy/project/playbook.yml': line 6, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
  roles:
    - satellite-receptor
      ^ here
Exit status: 1
```

The role is present in /usr/share/ansible/roles/project-receptor.satellite_receptor_installer but the job template asks for "satellite-receptor". This is a regression from 6.7 where the job template asked for:

```
  roles:
    - project-receptor.satellite_receptor_installer
```


Version-Release number of selected component (if applicable):
Sat 6.8, tested on snap 2.1.

How reproducible:
Deterministic

Steps to Reproduce:
1. Have foreman-proxy key installed to root@<satellite>
2. Run "Connect red hat receptor controller" against <satellite>

Actual results:
Error message shown above

Expected results:
Receptor installed

Comment 1 Adam Ruzicka 2020-06-02 11:15:48 UTC
It was fixed in upstream as foreman_ansible#333[1], moving to POST.

[1] - https://github.com/theforeman/foreman_ansible/pull/333

Comment 2 Lukáš Hellebrandt 2020-07-09 14:59:44 UTC
Verified with Sat 6.8 snap 8.0. Installed Receptor successfully using the job template.

Comment 5 errata-xmlrpc 2020-10-27 13:03:08 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 (Important: Satellite 6.8 release), 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:4366