-
Notifications
You must be signed in to change notification settings - Fork 115
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
[RFE]Updating RHCloud tests to SCA only #15694
Conversation
There doesn't seem to be many tests that use entitlements so this should be all the work. Additionally, Should we cherry-pick this into 6.15? I am open to suggestions |
@@ -4,10 +4,10 @@ | |||
|
|||
|
|||
@pytest.fixture(scope='module') | |||
def rhcloud_manifest_org(module_target_sat, module_extra_rhel_entitlement_manifest): |
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.
@ColeHiggins2 should we cleanup the code and remove module_extra_rhel_entitlement_manifest
fixture as it was only used by rhc tests? wdyt?
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.
also module_extra_rhel_entitlement_manifest_org
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.
Yes, we should remove all of the extra_rhel
fixtures for stream/6.16. There is no benefit to using more than 1 of each subscription on an SCA manifest. If the affected tests pass with SCA on earlier Satellite versions, we can cherrypick that change back as well.
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.
I have another jira ticket that cleans up all fixtures and code around sca. so I will do it then
I would recommend running the affected tests using SCA fixtures against 6.15, 6.14, and 6.13. If they're not affected by switching to SCA, I don't see a reason not to cherrypick all the way back to 6.13. |
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.
Requesting a couple of changes. Also, I see about a dozen tests that will be affected by this PR. Most of these tests are failing consistently in CI, so there may not be much value in testing them with PRT, but I would like to ensure that the passing tests continue passing with these changes. Please run a PRT job with these tests:
- tests/foreman/cli/test_http_proxy.py::test_insights_client_registration_with_http_proxy
- tests/foreman/ui/test_rhcloud_insights.py::test_insights_registration_with_capsule
- tests/foreman/ui/test_rhc.py::test_positive_configure_cloud_connector
"""A module level fixture to get organization with manifest.""" | ||
org = module_target_sat.api.Organization().create() | ||
module_target_sat.upload_manifest(org.id, module_extra_rhel_entitlement_manifest.content) | ||
module_target_sat.upload_manifest(org.id, module_extra_rhel_sca_manifest.content) |
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.
module_extra_rhel_sca_manifest
uses the extra_rhel_entitlement
manifest category [1], so this change will not reduce the subscription footprint of the rhcloud tests. Please use module_sca_manifest
with this fixture.
[1]
manifest_category=settings.manifest.extra_rhel_entitlement, simple_content_access="enabled" |
@@ -4,10 +4,10 @@ | |||
|
|||
|
|||
@pytest.fixture(scope='module') | |||
def rhcloud_manifest_org(module_target_sat, module_extra_rhel_entitlement_manifest): |
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.
Yes, we should remove all of the extra_rhel
fixtures for stream/6.16. There is no benefit to using more than 1 of each subscription on an SCA manifest. If the affected tests pass with SCA on earlier Satellite versions, we can cherrypick that change back as well.
8432879
to
abfae2e
Compare
trigger: test-robottelo |
PRT Result
|
* Adding pit marker for tests * Updating tests for rh cloud sca only * rh cloud sca only pick * rhcloud sca only pick2 * Addressing comments for sca org * removing cherrypicked Pr
Updating rhcloud related tests to run to be SCA only.