Bug 1861740 - [backup-and-restore] role fails to setup ReaR locally - local.conf.j2 template can't render
Summary: [backup-and-restore] role fails to setup ReaR locally - local.conf.j2 templat...
Keywords:
Status: CLOSED DUPLICATE of bug 1860439
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-29 12:40 UTC by Eliad Cohen
Modified: 2020-07-29 12:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-29 12:47:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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