Description of problem:

If a host is not part of any hostgroup but I am assigning a scap policy at host level, then after the ansible role gets executed, the "/etc/foreman_scap_client/config.yaml" on the host has all the necessary information except the server name i.e. openscap capsule name.

~~
# Foreman proxy to which reports should be uploaded
:server: 
:port: 9090

~~


Version-Release number of selected component (if applicable):
satellite-6.8.0-0.7.beta.el7sat.noarch

How reproducible:
Always on a newly registered host without associating it with any hostgroup

Steps to Reproduce:
1. Register a host to satellite but don't associate any hostgroup.
2. Ensure that the host has openscap capsule selected and assign the "theforeman.foreman_scap_client" role for the host.
3. Assign a policy to that host using the Bulk Action from All Hosts page.
4. Run the "theforeman.foreman_scap_client" role on the host.
5. Check the "/etc/foreman_scap_client/config.yaml" file on the host.
6. Assign the same host to a hostgroup where same policy and scap capsule is selected and then re-run the same job. 
7. Check the "/etc/foreman_scap_client/config.yaml" file on the host.

Actual results:

1. At step 5, The entire content of the "/etc/foreman_scap_client/config.yaml" file is OK but the "server" parameter is missing the openscap capsule name.
~~
# Foreman proxy to which reports should be uploaded
:server: 
:port: 9090
~~

2. At Step 7, the content of "/etc/foreman_scap_client/config.yaml" file is complete now i.e. openscap capsule name is populated now in the config file along with port.
~~
# Foreman proxy to which reports should be uploaded
:server: satellite.example.com
:port: 9090

~~

Expected results:

At step 5 i.e. when the host is not assigned with hostgroup, the content of "/etc/foreman_scap_client/config.yaml" should contain the smart-proxy name as long as correct openscap capsule is assigned at host level.


Additional info:

I can reproduce it on Satellite 6.8 Beta for any new host registered without hostgroup.