Open VladLazar opened 1 year ago
Sounds like something we should block v23.2.1 for
Sounds like something we should block v23.2.1 for
I'm not sure. It's worked this way ever since redpanda.remote.write|read
was introduced. I think it's quite rare to use remove
with IncrementalRemoteConfigs
. I'd expect users to set it explicitly most times. Not saying we shouldn't fix this;
it's a bug, but trying to provide some colour here.
Got it, thanks!
This issue hasn't seen activity in 3 months. If you want to keep it open, post a comment or remove the stale
label – otherwise this will be closed in two weeks.
This issue was closed due to lack of activity. Feel free to reopen if it's still relevant.
We should keep this open and action.
Version & Environment
Redpanda version: (use
rpk version
): v23.1.11What went wrong?
A user sent an IncrementalAlterConfigs with the
remove
op code forredpanda.remote.write
. Redpanda incorrectly interprets this as a request to disable remote writes.What should have happened instead?
IncrementalAlterConfigs with
remove
op codes fromredpanda.remote.write|read
should set the properties back to their default value (from the cluster config).How to reproduce the issue?
JIRA Link: CORE-1354