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

Whenever a remote execution job runs the 'yum check-update' command the job will result in a 'failed' status

Here is an example job (take from the webui of the failed job):
---
   1: Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id,
   2: : search-disabled-repos, subscription-manager
   3: Not using downloaded rhel-7-server-optional-rpms/repomd.xml because it is older than what we have:
   4: Current : Mon Mar 4 03:54:07 2019
   5: Downloaded: Fri Mar 1 23:17:20 2019
   6: Not using downloaded rhel-7-server-rpms/repomd.xml because it is older than what we have:
   7: Current : Sun Mar 3 05:22:38 2019
   8: Downloaded: Fri Mar 1 23:41:28 2019
   9: java-1.8.0-openjdk.x86_64 1:1.8.0.201.b09-0.el7_6 rhel-7-server-rpms
  10: java-1.8.0-openjdk-headless.x86_64 1:1.8.0.201.b09-0.el7_6 rhel-7-server-rpms
  11: mesa-libwayland-egl.x86_64 18.0.5-4.el7_6 rhel-7-server-optional-rpms
  12: Uploading Enabled Repositories Report
  13: Loaded plugins: langpacks, product-id, subscription-manager
  14: Exit status: 100
---

The command is seen here:
---
{"ssh_user"=>"root", "effective_user"=>"root", "effective_user_method"=>"sudo", "cleanup_working_dirs"=>true, "sudo_password"=>"", "ssh_port"=>22, "hostname"=>"10.12.212.64", "script"=>"yum check-update", "execution_timeout_interval"=>nil, "connection_options"=>{"retry_interval"=>15, "retry_count"=>4}, "proxy_url"=>"https://iridium.usersys.redhat.com:9090", "proxy_action_name"=>"ForemanRemoteExecutionCore::Actions::RunScript", "locale"=>"en", "current_user_id"=>4}
---

'yum check-update' reliably reproduces this exit code every time and it would be great to not see this action as a failure in the Satellite when the command actually succeeds.