Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1388696 - Failed to initialize command: Dynflow::ExecutionPlan::Steps::Error - undefined method `ip' for nil:NilClass
Failed to initialize command: Dynflow::ExecutionPlan::Steps::Error - undefine...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Remote Execution (Show other bugs)
6.2.2
All All
urgent Severity urgent (vote)
: 6.2.8
: Unused
Assigned To: Adam Ruzicka
jcallaha
: PrioBumpGSS, Triaged
Depends On:
Blocks: 1417074
  Show dependency treegraph
 
Reported: 2016-10-25 19:15 EDT by Marcelo Moreira de Mello
Modified: 2017-03-06 03:33 EST (History)
7 users (show)

See Also:
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 03:33:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
re interface change (80.25 KB, image/png)
2017-02-16 15:33 EST, jcallaha
no flags Details
verification screenshot (77.93 KB, image/png)
2017-02-16 15:33 EST, jcallaha
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2726731 None None None 2016-10-25 19:19 EDT
Foreman Issue Tracker 14008 None None None 2016-10-25 19:15 EDT
Red Hat Product Errata RHBA-2017:0447 normal SHIPPED_LIVE Satellite 6.2.8 Async Bug Release 2017-03-06 08:23:41 EST

  None (edit)
Description Marcelo Moreira de Mello 2016-10-25 19:15:15 EDT
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 19:19:28 EDT
Created article https://access.redhat.com/solutions/2726731
Comment 3 Bryan Kearney 2016-10-25 20:20:25 EDT
Upstream bug assigned to aruzicka@redhat.com
Comment 4 Bryan Kearney 2016-10-25 20:20:27 EDT
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 11:45:19 EST
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 15:32:36 EST
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 15:33 EST
Created attachment 1250940 [details]
re interface change
Comment 10 jcallaha 2017-02-16 15:33 EST
Created attachment 1250941 [details]
verification screenshot
Comment 12 errata-xmlrpc 2017-03-06 03:33:42 EST
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.