Bug 1388696

Summary: Failed to initialize command: Dynflow::ExecutionPlan::Steps::Error - undefined method `ip' for nil:NilClass
Product: Red Hat Satellite Reporter: Marcelo Moreira de Mello <mmello>
Component: Remote ExecutionAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.2CC: bbuckingham, bkearney, cwelton, ehelms, inecas, jcallaha, mmello
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: rubygem-foreman_remote_execution-0.3.0.14-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1417074 (view as bug list) Environment:
Last Closed: 2017-03-06 08:33:42 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: 1417074    
Attachments:
Description Flags
re interface change
none
verification screenshot none

Description Marcelo Moreira de Mello 2016-10-25 23:15:15 UTC 
Description of problem:

When trying to run a remote command it throws the error:

Failed to initialize command: Dynflow::ExecutionPlan::Steps::Error - undefined method `ip' for nil:NilClass

Please backport the issue http://projects.theforeman.org/issues/14008


Version-Release number of selected component (if applicable):
Red Hat Satellite 6.2.2

How reproducible:
100%
Comment 1 Marcelo Moreira de Mello 2016-10-25 23:19:28 UTC 
Created article https://access.redhat.com/solutions/2726731
Comment 3 Bryan Kearney 2016-10-26 00:20:25 UTC 
Upstream bug assigned to aruzicka
Comment 4 Bryan Kearney 2016-10-26 00:20:27 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/14008 has been resolved.
Comment 7 Ivan Necas 2017-02-06 16:45:19 UTC 
Steps to reproduce:

1. in a host, create second interface, check 'Remote Execution' flag, leave ip address blank

2. run a job against the host

Expected result: the execution interface is not considered for computation of ip address, and other interfaces are use for reaching the host
Comment 8 jcallaha 2017-02-16 20:32:36 UTC 
Verified in Satellite 6.2.8 Snap 2.

Steps:
1. Enable remote execution on a remote host.
2. Edit the host.
3. Uncheck remote execution from the primary interface.
4. Check remote execution for an alternate interface (see attached).
5. Run a job against the host.

Results:
The job completed successfully (see attached verification screenshot).
Comment 9 jcallaha 2017-02-16 20:33:03 UTC 
Created attachment 1250940 [details]
re interface change
Comment 10 jcallaha 2017-02-16 20:33:29 UTC 
Created attachment 1250941 [details]
verification screenshot
Comment 12 errata-xmlrpc 2017-03-06 08:33:42 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