Skip to content
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

Open
mattmoor opened this issue Jul 14, 2020 · 7 comments
Open

Enabling HA and chaosduck for IMC yields failures #3590

mattmoor opened this issue Jul 14, 2020 · 7 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. proposal/1.0
Milestone

Comments

@mattmoor
Copy link
Member

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:

  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.
@mattmoor mattmoor added the kind/bug Categorizes issue or PR as related to a bug. label Jul 14, 2020
@mattmoor
Copy link
Member Author

Opened #3598 to start debugging this.

@lberk lberk added area/test-and-release Test infrastructure, tests or release priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 27, 2020
@grantr grantr added proposal/1.0 and removed area/test-and-release Test infrastructure, tests or release priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 27, 2020
@grantr grantr added this to the Backlog milestone Aug 24, 2020
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 23, 2020
@mattmoor
Copy link
Member Author

/lifecycle frozen

@vaikas worth trying this again after your recent changes?

@knative-prow-robot knative-prow-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 23, 2020
@vaikas
Copy link
Contributor

vaikas commented Nov 23, 2020

@mattmoor yeah, thought about that just haven't gotten around to it yet :)

@slinkydeveloper
Copy link
Contributor

AFAIK this one was solved with #4675, i'm going to close it, reopen if you need it

@pierDipi
Copy link
Member

No, #4579.

/reopen

@knative-prow-robot
Copy link
Contributor

@pierDipi: Reopened this issue.

In response to this:

No, #4579.

/reopen

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. proposal/1.0
Projects
None yet
Development

No branches or pull requests

7 participants