8000 Enabling HA and chaosduck for IMC yields failures · Issue #3590 · knative/eventing · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Enabling HA and chaosduck for IMC yields failures #3590
New issue
New issue
Open
Open
Enabling HA and chaosduck for IMC yields failures#3590
Labels
kind/bugCategorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.proposal/1.0
Milestone
 
Backlog
@mattmoor

Description

@mattmoor
mattmoor
opened on Jul 14, 2020

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.proposal/1.0

    Type

    No type

    Projects

    Knative Eventing

    Status

    Blocked

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      0