Red Hat Bugzilla – Bug 1024351
Neutron dhcp again says the dnsmasq is too old.
Last modified: 2016-04-26 22:12:14 EDT
What exactly you expect from me to do about it? Don't expect I'll rebase dnsmasq
to 2.59 in RHEL-6 just because some dhcp (client/server) prints warning.
I'm curious why is dnsmasq component tracked in RHOS product. AFAIK dnsmasq is
part of RHEL product and all issues are tracked there. Also any updates to
dnsmasq have to go through RHEL update workflow. So untill dnsmasq is packaged
separately and distributed with RHOS only I don't see any reason why it should
According to this bug https://bugs.launchpad.net/neutron/+bug/1170793 prior the the 0.59 version, multiple bugs can occur related to the dnsmasq.
I would recommend to upgrade dnsmasq >=0.59 in the openstack repositories, if all related bug fix is backported, the warning should be removed.
(In reply to Attila Fazekas from comment #4)
> According to this bug https://bugs.launchpad.net/neutron/+bug/1170793 prior
> the the 0.59 version, multiple bugs can occur related to the dnsmasq.
> I would recommend to upgrade dnsmasq >=0.59 in the openstack repositories,
> if all related bug fix is backported, the warning should be removed.
1. I don't have any knowledge WHERE and HOW to update dnsmasq for RHOS. RHOS
is using dnsmasq without me knowing the use case, where and how I can maintain
it in the RHOS product. Next time RHOS is deciding on using some component it
would be good to notify the particular maintainer so they at least know about
it and know how to deal with issues in the product.
2. If the version available in RHEL-6 has some bugs, as you are saying, please
create new Bugs with proper description for them in the RHEL product. Saying
that there are multiple bugs without clearly knowing what they are is not
useful at all.
From my point of view, I don't see anything that needs to be fixed in dnsmasq
at the moment. Once you know what are those real issues, feel free to open bugs
for them. I'm changing the component to neutron, since this is the source of the
warning this bug is about.
There is a requirement in u/s to use dnsmasq version > 2.59.
There is also a patch that eliminates the need to get support in 'tag' and 'set' in dnsmasq which enables Neutron to run with 2.48 which is the version available in RHEL 6.4 and 6.5.
The warning is there because of the formal requirement in u/s but until we get any concrete issue with dnsmasq 2.48 I don't see a good reason to handle the overhead of shipping a special dnsmasq version in RHOS channels.
(In reply to lpeer from comment #6)
> The warning is there because of the formal requirement in u/s but until we
> get any concrete issue with dnsmasq 2.48 I don't see a good reason to handle
> the overhead of shipping a special dnsmasq version in RHOS channels.
As a dnsmasq maintainer I totally agree with you. I'm also prepared to discuss
possibility to fix specific bugs in dnsmasq or to include newer version as a
different package (in RHEL or RHOS) or to package dnsmasq using RHSCL.
Thanks for your very reasonable comment.