Plugins » Foreman Remote Execution

Remote execution has some checks that enforce that a host:
1) does not have more than 1 execution interface
2) If the host does not have an execution interface, the primary interface becomes the execution interface

For example let's take this host

# hammer host interface list --host flowing-escargot.example.com 
---|------------|-------------------------------------------|-------------------|-----------------|-----------------------------
ID | IDENTIFIER | TYPE                                      | MAC ADDRESS       | IP ADDRESS      | DNS NAME                    
---|------------|-------------------------------------------|-------------------|-----------------|-----------------------------
2  | eth0       | interface (primary, provision, execution) | 00:16:3e:10:8e:84 | 192.168.125.181 | flowing-escargot.example.com
3  | lo         | interface                                 |                   | 127.0.0.1       | localhost                   
---|------------|-------------------------------------------|-------------------|-----------------|-----------------------------

If I try to set lo to be the execution interface, it fails because eth0 is already an execution interface (see 1). If I try to unset eth0 as execution interface, it will immediately get re-marked as execution because it is also a primary interface.

As a workaround, we can perform both changes at once with curl

# cat <<EOF >/tmp/json
{"host": {
  "interfaces_attributes": [
    {"id": 2, "execution": false},
    {"id": 3, "execution": true}
  ]
}}
EOF

# curl -X PUT https://$SAT_FQDN/api/hosts/$HOST_ID -H 'Content-Type: application/json' -u $USER:$PASS -d @/tmp/json
-----B<-----SNIP-----B<-----

# hammer host interface list --host flowing-escargot.example.com 
---|------------|--------------------------------|-------------------|-----------------|-----------------------------
ID | IDENTIFIER | TYPE                           | MAC ADDRESS       | IP ADDRESS      | DNS NAME                    
---|------------|--------------------------------|-------------------|-----------------|-----------------------------
2  | eth0       | interface (primary, provision) | 00:16:3e:10:8e:84 | 192.168.125.181 | flowing-escargot.example.com
3  | lo         | interface (execution)          |                   | 127.0.0.1       | localhost                   
---|------------|--------------------------------|-------------------|-----------------|-----------------------------

I don't think this is currently doable with hammer.

From how I see it, we have 3 options:
1) Learn hammer to set other interfaces to execution=false when execution=true is being set for an interface
2) Make the change on Foreman's side (when execution flag is being set on an interface, remove it from all other interfaces of the same host)
3) Learn hammer to take parameters for multiple interfaces at once, something along the lines of hammer host interface update --host flowing-escargot.example.com --id 2 --execution false --id 3 --execution true

Proper fix for this is in #34452

This got fixed in foreman_remote_execution itself.