-
Notifications
You must be signed in to change notification settings - Fork 630
Enabling HA and chaosduck for MT Broker yields failures #3591
Copy link
Copy link
Closed
Labels
area/test-and-releaseTest infrastructure, tests or releaseTest infrastructure, tests or releasekind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.proposal/1.0
Metadata
Metadata
Assignees
Labels
area/test-and-releaseTest infrastructure, tests or releaseTest infrastructure, tests or releasekind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.proposal/1.0
In the context of this PR I tried enabling HA of the mt-broker-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/1283139079159943170
To reproduce things, sync past #3565 landing (or pull in the PR) and change:
./test/config/chaosduck.yaml: Comment/Remove the-disable=mt-broker-controllerflag../test/e2e-common.sh: Uncomment the linescale_controlplane mt-broker-controller.