Correctly handle an empty dnsmasq --domain
Bug #1161506 reported by
Pádraig Brady
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Pádraig Brady | ||
Grizzly |
Fix Released
|
Wishlist
|
Pádraig Brady |
Bug Description
https:/
Through quick code inspection this seems incorrect as the quotes will then become part of the domain name.
dnsmasq does handle _double_ quotes, but only in dnsmasq conf files and there they have special meaning for \t etc.
Note I've not actually tested the new code and would be very happy to be proved wrong here.
tags: | added: grizzly-rc-potential |
tags: |
added: grizzly-backport-potential removed: grizzly-rc-potential |
tags: | removed: grizzly-backport-potential |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Just verified, for sure, that using the quotes on domain work fine. I expect that dnsmasq is actually filtering out the '' because they aren't valid dns domain values, so it's working fine, though probably not on purpose from a dnsmasq perspective.
I think the idea of fixing this more cleanly for havana to just drop that param to dnsmasq makes sense. would be a good clean up.