Created redmine issue http://projects.theforeman.org/issues/20692 from this bug

Upstream bug assigned to aruzicka@redhat.com

Upstream bug assigned to aruzicka@redhat.com

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20692 has been resolved.

verified upstream with
foreman-1.18.0-0.develop.201803291734git682269f.el7.noarch
tfm-rubygem-foreman_remote_execution-1.4.6-1.fm1_18.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.1-1.fm1_18.el7.noarch

steps:

curl -X GET -u admin:changeme https://<host>/api/v2/job_invocations -k
{
  "total": 3,
  "subtotal": 3,
...

curl -X POST -u admin:changeme https://<host>/api/v2/job_invocations/3/rerun -k -H "Content-Type:application/json"
{"id":4,"targeting_id":4,"job_category":"Commands","task_id":"5f98d92c-d706-4418-9722-dae93a296ad9","task_group_id":4,"triggering_id":4,"description":"Run cat /etc/hosts","concurrency_level":null,"time_span":null,"execution_timeout_interval":null,"password":null,"key_passphrase":null,"remote_execution_feature_id":null} 

curl -X GET -u admin:changeme https://<host>/api/v2/job_invocations -k
{
  "total": 4,
  "subtotal": 4,
...

Verified on Sat 6.4 snap 10 using steps from c#7

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/RHSA-2018:2927