Description of problem: By default, trove-guestagent.conf doesn't contain the backup configuration. Currently using Swift for backups is the default for Trove for all datastores. Is this is not configured, backups creation will fail without too much information (logs for this are stored inside the guest instance and the user cannot access to those) The missing configuration is: ######### [DEFAULT] swift_url = http://<host>:8080/v1/AUTH_ # define host for Swift storage_strategy = SwiftStorage storage_namespace = trove.guestagent.strategies.storage.swift # ========== Default Storage Options for backup ========== backup_swift_container = database_backups backup_use_gzip_compression = True backup_use_openssl_encryption = True backup_aes_cbc_key = "default_aes_cbc_key" backup_use_snet = False backup_chunk_size = 65536 backup_segment_max_size = 2147483648 ######### How reproducible: Reproducible on a Centos 7 environment with a Packstack AIO deploy Steps to Reproduce: 1. Deploy Trove with Packstack AIO 2. Launch a mariadb/mysql instance 3. Try to create a backup Actual results: Trove fails to create a backup for the datastore because fails to locate the Swift endpoint. Expected results: Trove should have the configuration for this by default since is the only strategy for backups ATM for all the datastores. Additional info:
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.