Skip to content

Add test enabling all feature flags with exchange logger#15294

Merged
michaelklishin merged 1 commit intomainfrom
ff-exchange-logger
Jan 19, 2026
Merged

Add test enabling all feature flags with exchange logger#15294
michaelklishin merged 1 commit intomainfrom
ff-exchange-logger

Conversation

@ansd
Copy link
Copy Markdown
Member

@ansd ansd commented Jan 18, 2026

Add a test enabling all stable feature flags with exchange logging enabled.

This is a more general test case for #11652 that should catch all future feature flag issues when rabbit_ff_controller publishes a message.

Relates
#11652 #14069 #14796

@ansd
Copy link
Copy Markdown
Member Author

ansd commented Jan 18, 2026

This test should be backported to v4.2.x, v4.1.x, and v4.0.x.
This test is already part of VMware Tanzu RabbitMQ v3.13.x.

Add a test enabling all stable feature flags with exchange logging enabled.

This is a more general test case for #11652
that should catch all future feature flag issues when `rabbit_ff_controller` publishes a message.

Relates
#11652
#14069
#14796
@ansd ansd force-pushed the ff-exchange-logger branch from 7d283b3 to e50a6bf Compare January 18, 2026 14:48
@gomoripeti
Copy link
Copy Markdown
Contributor

thank you
(we only test with log exchange after a release is out and only on info level, so #14069 was only caught on a customer's cluster. great to now have a test case to catch anything like this early)

@michaelklishin michaelklishin added this to the 4.3.0 milestone Jan 19, 2026
@michaelklishin michaelklishin merged commit eca6c56 into main Jan 19, 2026
291 checks passed
@michaelklishin michaelklishin deleted the ff-exchange-logger branch January 19, 2026 04:13
michaelklishin added a commit that referenced this pull request Jan 19, 2026
Add test enabling all feature flags with exchange logger (backport #15294)
michaelklishin added a commit that referenced this pull request Jan 19, 2026
Add test enabling all feature flags with exchange logger (backport #15294) (backport #15295)
@ansd
Copy link
Copy Markdown
Member Author

ansd commented Jan 19, 2026

we only test with log exchange after a release is out and only on info level

Thank you. Enabling feature flag message_containers_deaths_v2 on the OSS v3.13.x branch with the log exchange at info level also gets stuck. Did you catch this during your manual testing?

@michaelklishin
Copy link
Copy Markdown
Collaborator

michaelklishin commented Jan 19, 2026

Note that backporting #14796 makes the new test pass.

So that fix will be available to paying RabbitMQ customers in the next round of releases, 4.0.18 and 3.13.12 (but not in this repo).

#14796 was also backported to v4.1.x for 4.1.8.

@gomoripeti
Copy link
Copy Markdown
Contributor

we only test with log exchange after a release is out and only on info level

Thank you. Enabling feature flag message_containers_deaths_v2 on the OSS v3.13.x branch with the log exchange at info level also gets stuck. Did you catch this during your manual testing?

I think my colleagues might have noticed it, but we already noted the workaround that we had to disable the log exchange when enabling FFs after an upgrade to 3.13.x so that stopped any further investigation.

dumbbell added a commit that referenced this pull request Jan 19, 2026
This corresponds to the comments I would have made to #15294, but this
pull request was merged before I had a chance to review it.

* Break long lines. This applies to a few long lines that were already
  there before #15294.
* Do not -import() functions as this makes the code more difficult to
  read and maintain.

While here, fix the copyright line: the initial year was incorrect and
the line was also too long.
@ansd
Copy link
Copy Markdown
Member Author

ansd commented Jan 19, 2026

I think my colleagues might have noticed it, but we already noted the workaround that we had to disable the log exchange when enabling FFs after an upgrade to 3.13.x so that stopped any further investigation.

Thank you for letting us know. Yes, disabling the log exchange temporarily is a valid workaround (as long as some other form of logging, e.g. to stdout or to a file is configured).

mergify bot pushed a commit that referenced this pull request Jan 19, 2026
This corresponds to the comments I would have made to #15294, but this
pull request was merged before I had a chance to review it.

* Break long lines. This applies to a few long lines that were already
  there before #15294.
* Do not -import() functions as this makes the code more difficult to
  read and maintain.

While here, fix the copyright line: the initial year was incorrect and
the line was also too long.

(cherry picked from commit fcd5e9b)

# Conflicts:
#	deps/rabbit/test/logging_SUITE.erl
mergify bot pushed a commit that referenced this pull request Jan 19, 2026
This corresponds to the comments I would have made to #15294, but this
pull request was merged before I had a chance to review it.

* Break long lines. This applies to a few long lines that were already
  there before #15294.
* Do not -import() functions as this makes the code more difficult to
  read and maintain.

While here, fix the copyright line: the initial year was incorrect and
the line was also too long.

(cherry picked from commit fcd5e9b)
michaelklishin pushed a commit that referenced this pull request Feb 24, 2026
This corresponds to the comments I would have made to #15294, but this
pull request was merged before I had a chance to review it.

* Break long lines. This applies to a few long lines that were already
  there before #15294.
* Do not -import() functions as this makes the code more difficult to
  read and maintain.

While here, fix the copyright line: the initial year was incorrect and
the line was also too long.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants