Throw warning when ocp4 and rhcos4 content fail on scapval

[ggbecker]

Description:

• Throw warning when ocp4 content fail on scapval.

Rationale:

• At this moment, the content validation always fail because it contains the non-standardized content (yamlfilecontent_test). With a warning instead, we can keep the job always green and whenever a fail occurs, we can assume it's a legit one.

[pep8speaks]

Hello @ggbecker! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file tests/run_scapval.py:

Line 45:100: E501 line too long (103 > 99 characters)

Comment last updated at 2020-09-21 10:11:01 UTC

[mildas]

Changes identified:
Others:
 Python abstract syntax tree change found in tests/run_scapval.py.

Recommended tests to execute:
 (cd build && cmake ../ && ctest -j4)