winstone, could you please quickly check if you can reproduce it? If not, no need to spend much time.

it's missing /my.cnf.d/server.cnf configuration, firewall configuration and OS info

winstone,
It's missing everything, that's why it's a "draft" (a stub for a bug report filed by a former employee for further working on it). The question was whether you can "reverse-engineer" it and see if you can get the same problem.

@Elena Stepanova ,
elenst ,
1. that issue which is of type bug but labeled by 'draft' looks like more an 'errata'
for draft --those are missing motivations , the problem is not clearly outlined regarding the missing input criteria
and nor there is proposed solution ;
more flexible would be if have an other yet custom jira issue type – it's allowed to define custom issue type fields values in Jira
2. to recreate – yes , but the variable bind-address has very shrunk scope — e.g you cannot enumerate
the addresses of the provisioned maridb galera cluster there , for that reason it would be better to set bind-address=0.0.0.0 — that would prevent cluster from being node isolated and
may play with firewall settings;
in addition should pay attention that the variable mariadb bind-address works in conjunction with the variable skip-networking ;
and also regarding the maridb galera cluster it's found that the wsrep_provider_option – gmcast.listen_addr takes precedence
over the bind-address variable ; so talking about bind-address and listening on 0.0.0.0:4567 – yes it's appears while by default gmcast.listen_addr is set to tcp://0.0.0.0:4567 ;

sachin.setiya.007,
According to winstone's comment above, if there is anything you want to fix, please do, otherwise feel free to close it as Not-a-bug. However, before doing so, please comment with explanation of the relation and precedence between the variables, or better still, have it documented in the KB.