Hi community, I've found what I believe to be a bug. The datahub actions container is failing with the following error log:

KafkaException: KafkaError{code=_INVALID_ARG,val=-186,str="Failed to create consumer: No provider for SASL mechanism GSSAPI: recompile librdkafka with libsasl2 or openssl support. Current build options: PL ││ AIN SASL_SCRAM OAUTHBEARER"}                                                                                                                                                                                  ││ 2022/03/02 13:30:11 Command exited with error: exit status 1

We don't use GSSAPI, but PLAIN, so there is some setting that the container does not pick up correctly. However, when I look at the deployment manifest for the actions container, it has these variables set:

spec:
      containers:
      - env:
        - name: GMS_HOST
          value: dfds-datahub-datahub-gms
        - name: GMS_PORT
          value: "8080"
        - name: KAFKA_BOOTSTRAP_SERVER
          value: REDACTED
        - name: SCHEMA_REGISTRY_URL
          value: <http://datadelivery-schema-registry:8081>
        - name: KAFKA_AUTO_OFFSET_POLICY
          value: latest
        - name: ACTION_FILE_NAME
          value: executor.yaml
        - name: KAFKA_PROPERTIES_KAFKASTORE_SECURITY_PROTOCOL
          value: SASL_SSL
        - name: KAFKA_PROPERTIES_SASL_JAAS_CONFIG
          value: org.apache.kafka.common.security.plain.PlainLoginModule required
            username="REDACTED" password="REDACTED";
        - name: KAFKA_PROPERTIES_SASL_MECHANISM
          value: PLAIN
        - name: KAFKA_PROPERTIES_SASL_PASSWORD
          value: REDACTED
        - name: KAFKA_PROPERTIES_SASL_USERNAME
          value: REDACTED
        - name: KAFKA_PROPERTIES_SECURITY_PROTOCOL
          value: SASL_SSL
        image: public.ecr.aws/datahub/acryl-datahub-actions:v0.0.1-beta.8
        imagePullPolicy: IfNotPresent
        name: acryl-datahub-actions
        ports:
        - containerPort: 9093
          name: http
          protocol: TCP
        resources:
          limits:
            cpu: 500m
            memory: 512Mi
          requests:
            cpu: 300m
            memory: 256Mi
        securityContext: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File

So the SASL_MECHANISM should be set to PLAIN, no? It is also set to PLAIN in the global values in the helm chart, see our values file here: https://github.com/dfds-data/datahub-infrastructure/blob/master/datahub/dfdsvals.yaml Is it a bug?

Yep, something similar happens to me. Look at this