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

AMQ operator upgraded automatically doesn't update Kafka version

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 2.0.1.GA
    • kafka-streams
    • None
    • False
    • None
    • False

      The AMQ operator was set to upgrade automatically but spec.kafka.version was not updated automatic keeping the old version 2.8 causing the following issue:

      "message":"Unsupported Kafka.spec.kafka.version: 2.8.0. Supported versions are: [3.0.0, 3.1.0]","reason":"UnsupportedKafkaVersionException","status":"True","type":"NotReady"
      

      After changing the version to 3.0.0, the logs shows:

      2022-06-20T13:11:04.683375195Z 2022-06-20 13:11:04,676 ERROR [Worker clientId=connect-1, groupId=connect-cluster] Uncaught exception in herder work thread, exiting:  (org.apache.kafka.connect.runtime.distributed.DistributedHerder) [DistributedHerder-connect-1-1]
      2022-06-20T13:11:04.683375195Z org.apache.kafka.common.config.ConfigException: Topic 'connect-cluster-configs' supplied via the 'config.storage.topic' property is required to have 'cleanup.policy=compact' to guarantee consistency and durability of connector configurations, but found the topic currently has 'cleanup.policy=delete'. Continuing would likely result in eventually losing connector configurations and problems restarting this Connect cluster in the future. Change the 'config.storage.topic' property in the Connect worker configurations to use a topic with 'cleanup.policy=compact'.
      

      It seems that new version requires the topics to be created with the compact cleanup policy, so after adding that property it started correctly but showing the following WARNs:

      message: >-
              log.message.format.version does not match the Kafka cluster version,
              which suggests that an upgrade is incomplete.
            reason: KafkaLogMessageFormatVersion
            status: 'True'
            type: Warning
      message: >-
              inter.broker.protocol.version does not match the Kafka cluster version,
              which suggests that an upgrade is incomplete.
            reason: KafkaInterBrokerProtocolVersion
            status: 'True'
            type: Warning
      

      The automatic upgrade process should not consider the above? or in the other side would be better not have enabled the automatic update in the operator?

            Unassigned Unassigned
            emunoz@redhat.com Elkin Dario Munoz Duarte
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: