Bug 1861740

Summary: [backup-and-restore] role fails to setup ReaR locally - local.conf.j2 template can't render
Product: Red Hat OpenStack Reporter: Eliad Cohen <elicohen>
Component: tripleo-ansibleAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Sasha Smolyak <ssmolyak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16.1 (Train)CC: jbadiapa
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-29 12:47:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eliad Cohen 2020-07-29 12:40:29 UTC
[Please assign to Cloudops/Backup and restore
Description of problem:
When attempting to setup ReaR on the undercloud, the execution of the role fails due to issues with the jinja2 template at 
/usr/share/ansible/roles/backup-and-restore/templates/local.conf.j2

Version-Release number of selected component (if applicable):
[1]


How reproducible:
100%

Steps to Reproduce:
*(Using an automated build)
1.Call upon the role "backup-and-restore" with tag: bar_setup_rear
Example:
- become: true
  hosts: Undercloud
  name: Install ReaR
  roles:
  - role: backup-and-restore

Actual results:
[2] 

Expected results:
Two issues here:
1. This template should render with the defaults. All values should be lists. not strings, not AnsibleUnicode
2. The template is using the "tripleo_backup_and_restore_exclude_paths" which doesn't exist. However, even when using "tripleo_backup_and_restore_exclude_paths_common" the rendering fails, possibly an issue with join(' ') on the map?

Additional info:
[1] http://pastebin.test.redhat.com/888732
[2] http://pastebin.test.redhat.com/888736

Comment 2 Juan Badia Payno 2020-07-29 12:47:27 UTC

*** This bug has been marked as a duplicate of bug 1860439 ***