You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was being incorrectly mapped to an authorization failure instead of
the kafka error corresponding to a unknown topic or partition.
Fixes: redpanda-data#3079Fixes: redpanda-data#3382
Signed-off-by: Noah Watkins <noahwatkins@gmail.com>
Controller topic delete error code incorrectly mapped to an
authorization failure instead of the kafka error corresponding to a
unknown topic or partition.
Fixes: redpanda-data#3079Fixes: redpanda-data#3382
Signed-off-by: Noah Watkins <noahwatkins@gmail.com>
Controller topic delete error code incorrectly mapped to an
authorization failure instead of the kafka error corresponding to a
unknown topic or partition.
Fixes: redpanda-data#3079Fixes: redpanda-data#3382
Signed-off-by: Noah Watkins <noahwatkins@gmail.com>
(cherry picked from commit 312e767)
Version & Environment
Redpanda version: (use
rpk version
): dev at SHA d90114bWhat went wrong?
Deleting a non-existent topic produces an "authorization error".
This is on a totally vanilla cluster created only with
rpk config bootstrap
, and no other settings changed.The same error occurs with
kcl
so I think we can assume it is RP returning this error.What should have happened instead?
An error about the topic not existing.
How to reproduce the issue?
rpk --brokers <broker IP>:<port> topic delete xyz
(where xyz is an arbitrary topic name that doesn't exist)The text was updated successfully, but these errors were encountered: