SCAP checks failing after upstream changes

[ehashman]

I think we just need to update the benchmarks to avoid these warnings: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-azure-vmimage-validate-osa311-latest/200#1:build-log.txt%3A269

[ehashman]

/kind test-flake
/assign

[ehashman]

Submitted https://bugzilla.redhat.com/show_bug.cgi?id=1823576 -- we have two rules failing and I don't think they should be.

[ehashman]

Fixed in version: scap-security-guide-0.1.49-5.el7

[ehashman]

0:0.1.46-11.el7 is still the one available in our builds. I'll wait until the correct version of the scanner rules are available.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[ehashman]

/lifecycle frozen
/remove-lifecycle rotten