-
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: add vm-console-proxy functional tests #498
Conversation
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.
Can you make 2 commits in this PR? One will fix some bugs from the previous PR, like missing UpdateFunc
s, and the other will add functional tests?
@akrejcir Thanks for the review, I'll take care of it on Sunday. Also I see this PR is affected by some issue:
|
/retest |
The CI is timeouting. I've created a PR to increase the timeout: openshift/release#36544 |
/retest |
@akrejcir Looks like it failed again because of timeout? I see it here [1]:
|
Let's try again, maybe it takes a while until the configuration is applied. /retest |
@akrejcir Okay. I see all *-apply jobs passed openshift/release@232d237. |
The timeout was probably not set correctly. I've created another PR to fix it: openshift/release#36609 |
/retest |
I think the timeout here is coming from ginkgo itself right? https://onsi.github.io/ginkgo/#recommended-continuous-integration-configuration
The fact we are still using
|
#504 - I wonder if this could help? |
Okay I'm pretty sure this is a change in behaviour in v2 thanks to the following docs: https://onsi.github.io/ginkgo/MIGRATING_TO_V2#timeout-behavior
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akrejcir The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Looks like it failed because of some internal error [1]:
|
/retest |
Another timeout issue:
And:
|
/test e2e-functests |
@codingben: No presubmit jobs available for kubevirt/ssp-operator@master In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
return common.CreateOrUpdate(request). | ||
ClusterResource(&serviceAccount). | ||
WithAppLabels(operandName, operandComponent). | ||
UpdateFunc(func(newRes, foundRes client.Object) { |
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 was mistaken about this change. The cluster adds a secret to the service account by default. This default field causes a reconciliation loop, and is removed again here in this function.
The loop means that SSP is always in a Deploying
state. Curiously, the functional tests should fail after 10 minutes if Deployed
state is not reached, but because of a race, sometimes the Deployed
state is seen and that is enough for the test to progress.
Please remove this UpdateFunc()
.
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.
Done.
/retest |
It's failing now because of some weird error:
|
/retest |
/retest-required |
Retest will not help. I'm looking into it. |
And just to be safe of unexpected changes, can you make a DeepCopy() of all the objects used in |
Add vm-console-proxy functional tests. Signed-off-by: Ben Oukhanov <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@akrejcir Thanks! |
/lgtm |
/retest |
1 similar comment
/retest |
/retest |
What this PR does / why we need it:
This PR will add vm-console-proxy functional tests.
Release note: