-
Notifications
You must be signed in to change notification settings - Fork 600
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
Enabling HA and chaosduck for IMC yields failures #3590
Comments
Opened #3598 to start debugging this. |
This issue is stale because it has been open for 90 days with no |
/lifecycle frozen @vaikas worth trying this again after your recent changes? |
@mattmoor yeah, thought about that just haven't gotten around to it yet :) |
AFAIK this one was solved with #4675, i'm going to close it, reopen if you need it |
No, #4579. /reopen |
@pierDipi: Reopened this issue. 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. |
In the context of this PR I tried enabling HA of the imc-controller process and "chaos".
It resulted in these failures during e2e: https://prow.knative.dev/view/gcs/knative-prow/pr-logs/pull/knative_eventing/3565/pull-knative-eventing-integration-tests/1283163740094599169
To reproduce things, sync past #3565 landing (or pull in the PR) and change:
./test/config/chaosduck.yaml
: Comment/Remove the-disable=imc-controller
and-disable=imc-dispatcher
flags../test/e2e-common.sh
: Uncomment the linescale_controlplane imc-controller imc-dispatcher
.The text was updated successfully, but these errors were encountered: