Oops, sorry for the noise: The problem could have been me...
The host that I used to create the hosted appliance might have been running a local
gluster at the time the wizard ran (leftover from a single node install).
And that might explain why the wizard would then expand that pool with new nodes and not
notice that storage and compute node point to different glusters...
I'll break down, rebuild and report.