-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oscap longrun tests parametrized for client rhel versions #15531
Conversation
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
a406629
to
7b627ba
Compare
trigger: test-robottelo |
trigger: test-robottelo |
PRT Result
|
|
sorry for a bit of a sidetrack, I was asked to review theforeman/foreman_openscap#575 and as I'd like to use tests from this pr, I'm using the above prt construct. The results shouldn't be used primarily to judge this pr, see the prt success above. |
PRT Result
|
|
PRT Result
|
back from PTO, I'll be looking into the proposed changes, just FYI, these tests are affected by SAT-26726 |
trigger: test-robottelo |
PRT Result
|
tests/foreman/longrun/test_oscap.py
Outdated
'repo': settings.repos.satclient_repo.rhel9, | ||
'akname': ak_name['rhel9'], | ||
'cvname': cv_name['rhel9'], | ||
}, | ||
{ | ||
'repo': settings.repos.satclient_repo.rhel8, | ||
'akname': ak_name['rhel8'], | ||
'cvname': cv_name['rhel8'], | ||
}, | ||
{ | ||
'repo': settings.repos.satclient_repo.rhel7, | ||
'akname': ak_name['rhel7'], | ||
'cvname': cv_name['rhel7'], | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this being too smart?
'repo': settings.repos.satclient_repo.rhel9, | |
'akname': ak_name['rhel9'], | |
'cvname': cv_name['rhel9'], | |
}, | |
{ | |
'repo': settings.repos.satclient_repo.rhel8, | |
'akname': ak_name['rhel8'], | |
'cvname': cv_name['rhel8'], | |
}, | |
{ | |
'repo': settings.repos.satclient_repo.rhel7, | |
'akname': ak_name['rhel7'], | |
'cvname': cv_name['rhel7'], | |
}, | |
'repo': getattr(settings.repos.satclient_repo, rhel), | |
'akname': ak_name[rhel], | |
'cvname': cv_name[rhel], | |
} for rhel in ('rhel9', 'rhel8', 'rhel7') |
profile = OSCAP_PROFILE['ospp8'] | ||
@pytest.fixture | ||
def scap_prerequisites(module_org, default_proxy, target_sat): | ||
# TODO: add support for RHEL9 (it doesn't have scap content in Sat by default) and parametrize distro |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC the problem is that we install scap-security-guide
on Satellite, but if that's on RHEL 8 then it doesn't have RHEL 9 content. AFAIK this is why we upload the content from the content host (which you do in upload_scap_content_for_host
). Though if the Satellite is on RHEL 9 then it should have the content available.
Would it be better to match the distro to the Satellite distro?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
eh, further complication, this part got in with #15491 while this PR was open, I just rearranged stuff after I pulled in changes. Clearly we should consolidate the approches form thes PRs, but I don't want to touch it within this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair. I'd just ask you to address 13fef98#r1691678387 since that does feel in line with this PR (you're introducing profiles
in this PR).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ekohl ah that's right, comitted!
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
Co-authored-by: Ewoud Kohl van Wijngaarden <[email protected]>
…E#15531) * oscap longrun tests parametrized for client rhel versions * feedback from review * further refactoring * Update tests/foreman/longrun/test_oscap.py Co-authored-by: Ewoud Kohl van Wijngaarden <[email protected]> --------- Co-authored-by: Ewoud Kohl van Wijngaarden <[email protected]>
Problem Statement
Adjusting existing oscap longrun tests to run on multiple client rhel versions (to increase coverage, make them available for pit-client testing etc.)
Solution
Few notes:
Related Issues