Skip to content

All controllers log with controllerKind "SuperStream" #404

Closed
@ChunyiLyu

Description

@ChunyiLyu

Describe the bug

{"level":"info","ts":1655722814.3733497,"msg":"Successfully declared queue","controller":"superstream","controllerGroup":"rabbitmq.com","controllerKind":"SuperStream","queue":{"name":"qq-example","namespace":"rabbitmq-system"},"namespace":"rabbitmq-system","name":"qq-example","reconcileID":"a17695c7-8dc2-4b4c-a254-bb7b4a74606f","queue":"qq"}
{"level":"info","ts":1655722814.3779905,"msg":"Finished reconciling","controller":"superstream","controllerGroup":"rabbitmq.com","controllerKind":"SuperStream","queue":{"name":"qq-example","namespace":"rabbitmq-system"},"namespace":"rabbitmq-system","name":"qq-example","reconcileID":"a17695c7-8dc2-4b4c-a254-bb7b4a74606f"}

Impacted version: 1.7.0. All previous versions log in a slightly different format and are not impacted.

To Reproduce

Deploy latest 1.7.0 operator, create a non SuperStream CR and see the log line

Expected behavior

ControllerKind should be the actual controller kind name

Fix

This is currently fixed in controller-runtime master branch kubernetes-sigs/controller-runtime#1907. We can wait til their next release. I will mark this issue as blocked for now and leave it open as a reminder for us.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions