Bug 1868800 - [RFE]: Control for executing the job from the Satellite to the Satellite needs to be implemented in the process
Summary: [RFE]: Control for executing the job from the Satellite to the Satellite need...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Cloud Connector
Version: 6.7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.9.0
Assignee: Adam Ruzicka
QA Contact: Petr Pochop
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-13 20:18 UTC by Taft Sanders
Modified: 2023-10-06 21:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:17:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30648 0 Normal Closed Control for executing the job from the Satellite to the Satellite needs to be implemented in the process 2021-02-17 17:44:24 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:17:57 UTC

Description Taft Sanders 2020-08-13 20:18:19 UTC
Description of problem:
When trying to install the cloud connector on the Satellite with multiple external Capsule servers, it is possible that the Satellite's host profile is configured in such a way that a external Capsule will be selected to run the job opposed to the Satellite server. This will result in a failure of the installation due to the lookup template used in the /usr/share/ansible/roles/project-receptor.satellite_receptor_installer/templates/receptor.conf.j2:
node_id={{ lookup('file', receptor_config_dir+'/rh_'+sat_account_id+'/uuid') }}

as the lookup module is only used for local files and not run on the remote server.

Version-Release number of selected component (if applicable):
6.7.2

How reproducible:
Everytime

Steps to Reproduce:
1. Get to the step before running the cloud connector playbook
2. Ensure your Satellite host profile is configured in a way that the algorithm used to determine the execution capsule (https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7/html-single/managing_hosts/index#sect-Managing_Hosts-Choosing_a_Satellite_Capsule_for_Remote_Execution) will not be the Satellite server, but a external Capsule
3. 

Actual results:
Creation of the '/etc/receptor/rh_*/receptor.conf failes due to the missing uuid file on the external capsule

Expected results:
The playbook should ensure that the playbook can only be executed on the Satellite server from the Satellite server

Additional info:

Comment 1 Adam Ruzicka 2020-08-13 20:20:51 UTC
Or maybe the playbook shouldn't do local lookups https://bugzilla.redhat.com/show_bug.cgi?id=1824835

Comment 2 Taft Sanders 2020-08-14 14:14:00 UTC
(In reply to Adam Ruzicka from comment #1)
> Or maybe the playbook shouldn't do local lookups
> https://bugzilla.redhat.com/show_bug.cgi?id=1824835

Perhaps this would be solved by my other RFE to have a drop down selection for execution capsule as well https://bugzilla.redhat.com/show_bug.cgi?id=1868795 . Should we table this RFE for now until an outcome for 1868795 and 1824835 are determined?

Comment 3 Adam Ruzicka 2020-08-17 07:32:20 UTC
Created redmine issue http://projects.theforeman.org/issues/30648 from this bug

Comment 4 Adam Ruzicka 2020-08-17 07:40:12 UTC
> Perhaps this would be solved by my other RFE to have a drop down selection for execution capsule as well https://bugzilla.redhat.com/show_bug.cgi?id=1868795 . Should we table this RFE for now until an outcome for 1868795 and 1824835 are determined?

It would, but we already have a fix ready for BZ1824835 and implementing bz1868795 would be by orders of magnitude more work than fixing this one. Let's go after the low hanging fruits first

Comment 5 Bryan Kearney 2020-08-17 08:07:18 UTC
Upstream bug assigned to aruzicka

Comment 6 Bryan Kearney 2020-08-17 08:07:20 UTC
Upstream bug assigned to aruzicka

Comment 7 Bryan Kearney 2020-11-10 12:06:58 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30648 has been resolved.

Comment 13 errata-xmlrpc 2021-04-21 13:17:39 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 (Moderate: Satellite 6.9 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-2021:1313


Note You need to log in before you can comment on or make changes to this bug.