Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-3346

KafkaMirrorMaker 2 - connections timeouts after forcing cluster cert renewal annotation on target kafka cluster (source works)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 1.8.0.GA
    • security
    • None
    • False
    • False

    Description

      When deployed simple Kafka source/target cluster with MirrorMaker 2 - forcing annotation on target kafka cluster results in bringing down source target, rolling kmm2 pod (unable to contact source kafka?).
      Seems like the whole connection is broken.

      Interestingly, when forcing renewal of cluster certs on source cluster works fine.
      In both cases correct (renewed) certs were present in kmm2 pod(s).

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. ENTMQST-3249 [QE] KafkaConnect and KafkaMirrorMaker2 should roll when certificates or user credentials are updated

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: