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 1402432 - Prefer fqdn instead of IP when tracking if remote execution is enabled for the host
Summary: Prefer fqdn instead of IP when tracking if remote execution is enabled for th...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks: 1417083
TreeView+ depends on / blocked
 
Reported: 2016-12-07 14:40 UTC by Michal Dekan
Modified: 2021-06-10 11:44 UTC (History)
12 users (show)

Fixed In Version: tfm-rubygem-foreman_remote_execution-0.3.0.14-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1417083 (view as bug list)
Environment:
Last Closed: 2017-03-06 08:35:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
verification screenshot (26.23 KB, image/png)
2017-02-16 19:44 UTC, jcallaha 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17603 0 High Closed Prefer fqdn instead of IP when tracking if remote execution is enabled for the host 2020-05-15 13:13:13 UTC
Red Hat Product Errata RHBA-2017:0447 0 normal SHIPPED_LIVE Satellite 6.2.8 Async Bug Release 2017-03-06 13:23:41 UTC

Description Michal Dekan 2016-12-07 14:40:45 UTC 
Description of problem:

Customer has nodes within RAC cluster where IP addresses are changing quite often. This might result in jobs to be executed on the different host

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

Satellite 6.2.4

$ egrep 'remote|tfm-rubygem-katello' installed_packages 
tfm-rubygem-smart_proxy_remote_execution_ssh_core-0.1.2-1.el7sat.noarch
rubygem-smart_proxy_remote_execution_ssh-0.1.2-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5.3-1.el7sat.noarch
tfm-rubygem-foreman_remote_execution-0.3.0.12-1.el7sat.noarch
tfm-rubygem-katello-3.0.0.82-1.el7sat.noarch

How reproducible:

100%

Steps to Reproduce:

Taken from the case:

On my test system I have eth0 and eth1:

# facter
ipaddress => 10.12.213.48
ipaddress_eth0 => 10.12.213.48
ipaddress_eth1 => 10.12.212.180

So now, if I supply a puppet report of facts, the Satellite now knows my IP of my RE interface (eth0) and the other interface.
If I bring down eth0 now, and send a new puppet report the Satellite will report the IP as blank for the RE interface and the RE Job will fail to connect via SSH.
If we sent a new puppet report (puppet agent -tv), the Satellite will receive the new 'ipaddress' fact which has changed to the IP of eth1. Now when we attempt a job, even though that interface is NOT checked for RE, the job will succeed..

Actual results:

Network interface with RE NOT enabled successfully executes the jobs. 

Expected results:

Job should not be marked as successfully if new changed interface with IP was not marked for RE.

Additional info:

Can we use fqdn instead of ip address as a source of remote execution activation?
Comment 2 Ivan Necas 2016-12-07 15:18:41 UTC 
Created redmine issue http://projects.theforeman.org/issues/17603 from this bug
Comment 3 Ivan Necas 2016-12-07 17:41:38 UTC 
Proposed solution https://github.com/theforeman/foreman_remote_execution/pull/213
Comment 4 Bryan Kearney 2016-12-07 19:03:20 UTC 
Upstream bug assigned to inecas
Comment 5 Bryan Kearney 2016-12-07 19:03:23 UTC 
Upstream bug assigned to inecas
Comment 8 Satellite Program 2017-01-24 21:04:08 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17603 has been resolved.
Comment 9 Ivan Necas 2017-02-06 17:04:03 UTC 
Steps to verify:

1. set ip address on host primary interface to other value
2. run the execution job against the host

Expected result:

Primarily, the host fqdn should be used for addressing the host

To switch to the original behavior (which might be useful, when DNS present in the infrastructure), set 'remote_execution_connect_by_ip' to true in Remote Execution settings
Comment 12 jcallaha 2017-02-16 19:43:56 UTC 
Verified in Satellite 6.2.8 Snap 2.

Steps:
1. Enable remote execution on a remote host.
2. Change the ipaddress of the host's interface(s)
3. Run a job against the host.

Result:
The job completed successfully, as expected.

Negative test steps:
1. Use the host setup above
2. Navigate to Administer -> Settings
3. Click on the RemoteExecution tab
4. Change "remote_execution_connect_by_ip" to "true"
5. Run a job against the host

Result:
The job failed, as expected.
Errno::ETIMEDOUT Connection timed out - connect(2) for "10.19.34.1" port 22

See attached image to see the first job succeed and the second job fail.
Comment 13 jcallaha 2017-02-16 19:44:41 UTC 
Created attachment 1250936 [details]
verification screenshot
Comment 15 errata-xmlrpc 2017-03-06 08:35:19 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/RHBA-2017:0447
Note You need to log in before you can comment on or make changes to this bug.