-
Notifications
You must be signed in to change notification settings - Fork 33
DNM - Cleanup kuttl tests #386
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
Conversation
/test manila-operator-build-deploy-kuttl |
1 similar comment
/test manila-operator-build-deploy-kuttl |
This is interesting, from the existing events log we can see:
It succeed at some point, but it's not clear why db-sync fails at the beginning (this seem a consistent behavior). |
2f432e3
to
73f4f48
Compare
The bad news is that I'm not able to reproduce the same error locally, where everything passes as expected:
|
47f4236
to
a96c64b
Compare
/test manila-operator-build-deploy-kuttl |
I think now I have a more clear idea of what's going on.
Clearly, after a few minutes (when we reach
and we get no logs. |
Looks like the problem is in the image used by the job:
and this explains why we had working tests until 3 days ago. In my local environment I get by default an image based on the working tag, and that's why I wasn't able to reproduce it. |
After doing a few more tests, we can see that after downgrading
|
Kuttl blocked by this bug: https://issues.redhat.com/browse/RHEL-78362 |
e7c94f3
to
f00b915
Compare
Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. |
f00b915
to
fbbdfa6
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: fmount 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 |
The existing
kuttl
tests match the wholeManila CR
spec (including sub resources spec), including parameters that are not meaningful to make the test pass or not.This patch removes a lot of fields that are not required in the main assertion. For example, matching the status is often sufficient to assert the status of the reconciliation, conditions, and to check if a resource has been properly deployed; images are not tested via kuttl, and we have jobs testing both the container image injection and a minor update with custom images.
This is the first step to reorganize kuttl tests into independent test suites.