So - as a summary - this is 'works as designed' approach to this bug? ;-)
Maybe we should default to an empty configuration? as per https://docs.openstack.org/cinder/train/configuration/block-storage/backup-drivers.html and add a mention in the docs, that cinder-backup is deployed by default when cinder is enabled, but if you don't configure a backend - it will be unconfigured?
It wouldn't break existing installations I guess. Question if cinder-backup will start with empty backup_* config...
So - as a summary - this is 'works as designed' approach to this bug? ;-) /docs.openstack .org/cinder/ train/configura tion/block- storage/ backup- drivers. html and add a mention in the docs, that cinder-backup is deployed by default when cinder is enabled, but if you don't configure a backend - it will be unconfigured?
Maybe we should default to an empty configuration? as per https:/
It wouldn't break existing installations I guess. Question if cinder-backup will start with empty backup_* config...