Bug 1463444

Description of problem:
Right now we can schedule a openscap scan but can't trigger one at will.

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


Actual results:
Once I have assigned a policy and [cronjob] schedule to a host, there's no way to trigger an adhoc scan. I currently have to ssh in to the client/host and run 

cat /etc/foreman_scap_client/config.yaml

to get the policy number. I then have to run

foreman_scap_client <policy number>

to get the scan to upload to my satellite server.

To make this more seamless in satellite, I just created a 'Run Command - SSH Default through SSH' with this command 'foreman_scap_client 1' and I can execute it against the machine without having to do the above. NOTE: This assumes '1' is the intended policy number.

Expected results:
There should be a openscap scan ACTION after assigning a policy(ies) to a host.



Additional info:
cat /etc/foreman_scap_client/config.yaml

it would be nice if the documentation told me I needed to open port 9090 on the satellite server to get this to work. Fortunately, the foreman_scap_client command will complain that the port isn't open and then I manually opened it.