-
Notifications
You must be signed in to change notification settings - Fork 592
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
Feature: upgrade & downgrade tests #2388
Feature: upgrade & downgrade tests #2388
Conversation
Prober will be used to it's own package to enable running it from within e2e tests and upgrade tests.
Implemented receiver deployment and removal with getting service node port, to later be able to connect and fetch results.
* ksvc ready * triggers ready * pod ready * ksvc scales to zero
Hi @cardil. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/uncc @yt3liu |
23e6067
to
823bdf6
Compare
/retest |
1a75336
to
4739de5
Compare
spec: | ||
containers: | ||
- name: wathola-receiver | ||
image: ko://knative.dev/eventing/test/test_images/wathola-receiver |
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.
thanks!!
@@ -0,0 +1,83 @@ | |||
# Upgrade Tests |
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.
omg thanks for this documentation.
Thank you so much for the hard work, I think this is great and we can start with this and as we ramp up the knative-wide testing repo, this test will play a key role. /lgtm Ville to approve |
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.
Thanks for doing this!!!
@@ -0,0 +1,6 @@ | |||
# logLevel = 5 # DEBUG(5) | |||
[sender] | |||
address = 'http://default-broker.{{- .Namespace -}}.svc.cluster.local' |
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.
This will only work for soon to be removed ChannelBasedBroker. Can you file an issue to actually fetch the URL from the Broker.Status instead of hardcoding it?
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.
ACK
| | | | | | ||
+--------+ +---------+ | | ||
(default) +----------+ | ||
``` |
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.
This documentation is great, I'd like to see a section on what the output is, where to look for debug hints, look like you dump a bunch of logs, etc. For example you report that there are double events, my first knee jerk reaction is, are there for example double-subscriptions being created somehow. Not quite sure how I'd go about figuring it out. Please create an issue to follow up so we don't have to hold / rebase, etc.
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.
In the e2e tests we dump the objects / k8s events on test failures so something like that would be nice. But again, fine as a followup.
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.
Now, we are not failing even that we found errors. If we switch https://github.com/cardil/eventing/blob/feature/upgrade-tests/test/upgrade/probe_test.go#L55 then we will have default fail dump after this test. Maybe that is sufficient?
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 line L55 gives me 404. I guess it's this: https://github.com/knative/eventing/pull/2388/files#diff-38e78729550b76fecdd458bc3146c1c3R55 ?
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.
Yup. I've removed the source branch, sorry. But, now it's merged it's on master: https://github.com/knative/eventing/blob/master/test/upgrade/probe_test.go#L55
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cardil, vaikas 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 |
Node exporter image pulloff failure? Odd... Other two came up just fine...
|
/test pull-knative-eventing-integration-tests |
1 similar comment
/test pull-knative-eventing-integration-tests |
Might be a quay outage issue? |
Quay is now up. Retesting. /test pull-knative-eventing-integration-tests |
Fixes #2271
Proposed Changes
For more verbose description see:
test/upgrade/README.md
in changed files.Release Note