Enabling HA and chaosduck for IMC yields failures
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 631
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
In the context of [this PR](https://github.com/knative/eventing/pull/3565) 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:
1. `./test/config/chaosduck.yaml`: Comment/Remove the `-disable=imc-controller` and `-disable=imc-dispatcher` flags.
2. `./test/e2e-common.sh`: Uncomment the line `scale_controlplane imc-controller imc-dispatcher`.
Contributor guide
Research direction
Reproduce the failures after syncing past PR #3565, using test/config/chaosduck.yaml and test/e2e-common.sh with the IMC controller and dispatcher enabled for HA and chaos testing. Start with the linked Prow e2e log, then compare the failing behavior against the configuration changes; done means the relevant e2e tests pass under this setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, shell
- Domain
- distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100