Bug 1285897 - trove-guestagent.conf should define the configuration for backups
trove-guestagent.conf should define the configuration for backups
Status: CLOSED EOL
Product: RDO
Classification: Community
Component: openstack-puppet-modules (Show other bugs)
Liberty
Unspecified Unspecified
unspecified Severity unspecified
: ---
: Kilo
Assigned To: Ivan Chavero
Shai Revivo
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-26 17:44 EST by Victoria Martinez de la Cruz
Modified: 2016-05-19 11:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-19 11:34:03 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Victoria Martinez de la Cruz 2015-11-26 17:44:04 EST
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:
Comment 2 Chandan Kumar 2016-05-19 11:34:03 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.