Uploaded image for project: 'Managed Service - Connectors'
  1. Managed Service - Connectors
  2. MGDCTRS-1630

Connector stuck in provisioning state instead of failing when it can't access Kafka

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • cos-fleetshard-camel
    • None
    • Very Likely
    • 0

      When a connector has error handling set to stop and it can't access Kafka it'll get into provisioning state and fail after the access to Kafka is regained. This can be simulated with network control policy.

      mctr.json

      networkpolicy.yaml

      I left a connector setup on https://api.rhoc-411-stage.fuse.integration-qe.com:6443, mctr-cdd53uub1up7iimi8ih0-f998c57d7-z55wk (connector-id: cdd53utm1afo0kcgnt00) will be stuck in provisioning state until oc delete networkpolicy cdd53utm1afo0kcgnt00 is ran, only then will the connector get into stopped/failed state.

        1. networkpolicy.yaml
          0.6 kB
        2. mctr.json
          1 kB

              vajain Vaibhav Jain
              mmuzikar Martin Muzikar
              Archiver:
              ranumula@redhat.com Raju Anumula

                Created:
                Updated:
                Resolved:
                Archived: