-
Notifications
You must be signed in to change notification settings - Fork 47
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
test: remove part-of label expected #666
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @0xFelix |
IIUC, the label |
You're right, I think then we can remove that test, it's not really needed. |
Remove the test of expected part-of label from service tests because in upstream CI we don't set that label and it's empty. However, in downstream it's deployed by HCO and the part-of label is set. Jira Urls: 1. https://issues.redhat.com/browse/CNV-32226 2. https://issues.redhat.com/browse/CNV-32128 Signed-off-by: Ben Oukhanov <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
I removed that test of part-of label. In upstream CI we don't deploy SSP by HCO yet, but in downstream QE CI it's deployed by HCO so the label is set there, but we can't test the value here in upstream. The fact that we have part-of label set here: ssp-operator/tests/tests_suite_test.go Line 114 in 96302e1
Is wrong IMO, and should be removed. We shouldn't set the part-of label since we don't deploy the SSP by HCO here. |
/retest |
It is a feature of SSP to propagate the label from the SSP CR to resources created by SSP. So I think we should absolutely test this feature here. |
We have 2 controllers that responsible to reconcile different resources:
I think we shouldn't set the service object with labels that are defined in SSP CR, it's a different controller. [1] https://github.com/kubevirt/ssp-operator/blob/main/controllers/ssp_controller.go#L132-L239 |
Also @akrejcir mentioned it:
in #608 (comment). |
Yes, you are right. But I don't see how the part-of label is set in the I was under the impression that everything deployed by SSP needs to have a part-of label (if specified), but it looks like resources deployed by |
Ok, when looking at the correct branch I can see the code taking the
AFAIU there is no way to modify the deployment easily, so we can't test it US? |
Ah sorry about that, I updated the links with main branch.
I don't see how we can test it in upstream CI. I think in downstream CI we're okay, also the fact that only in downstream there is a requirement for those 4 required labels by HCO QE. Maybe @akrejcir, do you think we can populate the SSP deployment in upstream CI, when we know that |
Can you set a static value for |
What this PR does / why we need it:
Remove the test of expected part-of label from
service tests because in upstream CI we don't
set that label and it's empty.
However, in downstream it's deployed by HCO and
the part-of label is set.
Jira Urls:
Release note: