Johannes Scheuermann

Ping @saintstack @sears @jleach4

Fixed in the PR above. Thanks again!

This was actually already implemented.

I change this from bug to documentation, this is currently a limitation of the design and changing the design will require more work.

I did a bit more debugging and it seems like the error code is not returned by the create database method and instead of a nil/null pointer an empty struct...

> > If you observed an issue and used DNS entries in the cluster file you might have hit: [apple/foundationdb#11222](https://github.com/apple/foundationdb/issues/11222). Especially in the case when the coordinators are not reachable....

I was busy with some other things. Thanks for providing that snippet, I'll give it a try. My plan is to get a core dump and see where things are...

After doing some further debugging and testing it seems the root cause of the issue was/is that the operator is currently build with the fdb bindings and header files for...

Could you please verify if there are any other processes/tools running in our setup? I was not able to reproduce the issue. Is it possible that you ran `fdbcli` from...

See: https://github.com/FoundationDB/fdb-kubernetes-operator/pull/1995