The way this is defined, cinder-volume-manager will be set up on every node in the environment when Cinder LVM volume backend is sected in storage settings.
This error is relatively harmless since cinder scheduler is smart enough to ignore cinder-volume-manager instances on nodes that don't have cinder VG and create volumes on cinder nodes. Downgrading to low.
There's a faulty logic in this condition:
https:/ /github. com/stackforge/ fuel-library/ blob/e3ea44c3b6 07f37401a268a91 956c9d222a81bab /deployment/ puppet/ osnailyfacter/ manifests/ cluster_ ha.pp#L143
The way this is defined, cinder- volume- manager will be set up on every node in the environment when Cinder LVM volume backend is sected in storage settings.
This error is relatively harmless since cinder scheduler is smart enough to ignore cinder- volume- manager instances on nodes that don't have cinder VG and create volumes on cinder nodes. Downgrading to low.