Description of problem:
When security profile is selected during installation through anaconda, report of the hardening run exists in `/root/eval_remediate_report.html`. This report is full of `error` results that seemingly make no sense. This is tue to the way how service checking OVAL and remediations work. For check `service_XXX_enabled`, OVAL and remediation checks not only enablement, but also that the service is running.

As anaconda remediation runs in chroot, systemd won't allow checks of service runtime, resulting in fails. Fail after remediation is reported as error. This is but a display bug, though, as if you run the scan after reboot, these rules are passing.
 
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.40-5.el7

How reproducible:
reliably

Steps to Reproduce:
1. install through anaconda (for example profile `stig-rhel7-disa`) 
2. open `/root/eval_remediate_report.html`
3.

Actual results:
Errors for basic checks like `rule_service_sshd_enabled`

Expected results:
No errors in general, but in this particular case no errors for service related rules.

Additional info:
This idea behind checking runtime as well is to make sure that service can run at all. To catch situation as such as service is enabled, but because of malformed configuration does not start.