We are running into this issue due to using quite an old version of Cinder (Mitaka), which does not set 'cluster_name" in its connection dict. We are looking at solving this by patching Cinder to include this (Cinder upgrade is TODO).
Having said that - defaulting to a cluster name of 'None' is *never* going to be correct, so the os0brick code behaviour is undesirable.
We are running into this issue due to using quite an old version of Cinder (Mitaka), which does not set 'cluster_name" in its connection dict. We are looking at solving this by patching Cinder to include this (Cinder upgrade is TODO).
Having said that - defaulting to a cluster name of 'None' is *never* going to be correct, so the os0brick code behaviour is undesirable.