designate.conf.j2 does not respect user configured designate database name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Medium
|
Guilherme Steinmuller Pimentel |
Bug Description
encountered this in 17.0.6, Queens/stable when i started testing openstack-ansible
in designate.conf.j2, the database name is hardcoded as 'designate':
[storage:
connection = mysql+pymysql://{{ designate_
Further to this, for the database name, all other openstack-ansible roles use variables that follow a pattern: <openstack-
os-designate, seems to prefer designate_
- include: common-
static: no
vars:
user_name: "{{ designate_
password: "{{ designate_
login_host: "{{ designate_
db_name: "{{ designate_
I therefore propose the 2 patches attached:
1 - to make os-designate respect custom database names:
diff /etc/ansible/
384c384
< connection = mysql+pymysql://{{ designate_
---
> connection = mysql+pymysql://{{ designate_
2 - To bring os-designate inline with othse openstack-ansible components wrt database naming pattern:
diff /opt/openstack-
59c59
< db_name: "{{ designate_
---
> db_name: "{{ designate_
#1 is a bug fix
#2 is a 'nice to have' change in the interest of consistency
tags: | added: low-hanging-fruit |
Changed in openstack-ansible: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Guilherme Steinmuller Pimentel (guilhermesp) |
Fix proposed to branch: master /review. openstack. org/585523
Review: https:/