Crash in `partition_balancer_test`.`PartitionBalancerTest`

[jcsp]

Module: rptest.tests.partition_balancer_test Class: PartitionBalancerTest Method: test_fuzz_admin_ops

https://buildkite.com/redpanda/redpanda/builds/13548#018264d0-0df0-452d-a0ec-258fa674babe

rptest.services.utils.NodeCrash: <NodeCrash docker-rp-19: redpanda: /vectorized/include/seastar/core/future.hh:641: void seastar::future_state<seastar::internal::monostate>::set(A &&...) [T = seastar::internal::monostate, A = <>]: Assertion `_u.st == state::future' failed.
>

[mmaslankaprv]

addr2line: DWARF error: invalid or unhandled FORM value: 0x23
Backtrace:
[Backtrace #0]
__interceptor_backtrace at ??:?
void seastar::backtrace<seastar::backtrace_buffer::append_backtrace()::{lambda(seastar::frame)#1}>(seastar::backtrace_buffer::append_backtrace()::{lambda(seastar::frame)#1}&&) at reactor.cc:?
seastar::backtrace_buffer::append_backtrace() at reactor.cc:?
seastar::print_with_backtrace(seastar::backtrace_buffer&, bool) at reactor.cc:?
seastar::print_with_backtrace(char const*, bool) at reactor.cc:?
seastar::sigabrt_action() at reactor.cc:?
seastar::install_oneshot_signal_handler<6, (void (*)())(&seastar::sigabrt_action)>()::{lambda(int, siginfo_t*, void*)#1}::operator()(int, siginfo_t*, void*) const at reactor.cc:?
seastar::install_oneshot_signal_handler<6, (void (*)())(&seastar::sigabrt_action)>()::{lambda(int, siginfo_t*, void*)#1}::__invoke(int, siginfo_t*, void*) at reactor.cc:?
?? ??:0
/var/lib/buildkite-agent/builds/buildkite-amd64-xfs-builders-i-091867c9b7c89c49d-1/redpanda/redpanda/vbuild/debug/clang/dist/local/redpanda/lib/libc.so.6: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=6e3c087aca9b39549e4ba92c451f1e399b586e28, for GNU/Linux 3.2.0, not stripped

__GI_raise at :?
__GI_abort at :?
__assert_fail_base.cold at assert.c:?
__GI___assert_fail at :?
void seastar::future_state<seastar::internal::monostate>::set<>() at application.cc:?
void seastar::internal::promise_base_with_type<void>::set_value<>() at application.cc:?
void seastar::promise<void>::set_value<>() at application.cc:?
seastar::pollable_fd_state_completion::complete_with(long) at reactor_backend.cc:?
seastar::reactor_backend_aio::await_events(int, __sigset_t const*) at reactor_backend.cc:?
seastar::reactor_backend_aio::reap_kernel_completions() at reactor_backend.cc:?
seastar::reactor::reap_kernel_completions() at reactor.cc:?
seastar::reactor::reap_kernel_completions_pollfn::poll() at reactor.cc:?
seastar::reactor::poll_once() at reactor.cc:?
seastar::reactor::do_run()::$_79::operator()() const at reactor.cc:?
decltype ((static_cast<seastar::reactor::do_run()::$_79&>({parm#1}))()) std::__1::__invoke<seastar::reactor::do_run()::$_79&>(seastar::reactor::do_run()::$_79&) at reactor.cc:?
bool std::__1::__invoke_void_return_wrapper<bool, false>::__call<seastar::reactor::do_run()::$_79&>(seastar::reactor::do_run()::$_79&) at reactor.cc:?
std::__1::__function::__alloc_func<seastar::reactor::do_run()::$_79, std::__1::allocator<seastar::reactor::do_run()::$_79>, bool ()>::operator()() at reactor.cc:?
std::__1::__function::__func<seastar::reactor::do_run()::$_79, std::__1::allocator<seastar::reactor::do_run()::$_79>, bool ()>::operator()() at reactor.cc:?
std::__1::__function::__value_func<bool ()>::operator()() const at reactor.cc:?
std::__1::function<bool ()>::operator()() const at reactor.cc:?
seastar::reactor::do_run() at reactor.cc:?
seastar::reactor::run() at reactor.cc:?
seastar::app_template::run_deprecated(int, char**, std::__1::function<void ()>&&) at app-template.cc:?
seastar::app_template::run(int, char**, std::__1::function<seastar::future<int> ()>&&) at app-template.cc:?
application::run(int, char**) at ??:?
main at ??:?
__libc_start_main at ??:?
_start at ??:?

[dotnwat]

this is a tough one

[piyushredpanda]

Requesting @ztlpn to help chase this.

[mmaslankaprv]

I have analyzed last 30 days of CI failures and this one was never triggered. I will close this for now since there is no information on what caused the issue and there was a lot of code churn recently.