dnsmasq-flags option does not support non-kv flags

Bug #1999639 reported by Mustafa Kemal Gilor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Neutron Gateway Charm
New
Undecided
Unassigned

Bug Description

currently "dnsmasq-flags" charm option only supports flags in key-value pair format, like

dhcp-option=42,0.0.0.0

and it works fine for such values, but there are some dnsmasq options that have no value, e.g.:

log-queries
log-dhcp
no-negcache
dhcp-authoritative
dhcp-rapid-commit

to name a few. When such options are supplied as dnsmasq-flags, the rendered dnsmasq.conf file simply becomes invalid:

$ juju config neutron-gateway dnsmasq-flags="log-dhcp,dhcp-option=42,0.0.0.0,no-negcache,srv-host=_ldap._tcp.example.com,ldapserver.example.com,389"

# rendered /etc/neutron/dnsmasq.conf
log-dhcp,dhcp-option = 42,0.0.0.0,no-negcache
srv-host = _ldap._tcp.example.com,ldapserver.example.com,389

# expected /etc/neutron/dnsmasq.conf
log-dhcp
dhcp-option = 42,0.0.0.0
no-negcache
srv-host = _ldap._tcp.example.com,ldapserver.example.com,389

Expectation: We should be able to supply non-kv config flags to dnsmasq, and the resulting dnsmasq.conf file must be a valid dnsmasq configuration file.

summary: - dnsmasq-flags option do not support non-kv flags
+ dnsmasq-flags option does not support non-kv flags
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.