RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1176224 - dnsmasq-2.48-14.el6.x86_64 breaks neutron (failed to set SO_REUSE{ADDR|PORT})
Summary: dnsmasq-2.48-14.el6.x86_64 breaks neutron (failed to set SO_REUSE{ADDR|PORT})
Keywords:
Status: CLOSED DUPLICATE of bug 1154953
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dnsmasq
Version: 6.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 6.6
Assignee: Pavel Šimerda (pavlix)
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-19 18:07 UTC by Dmitry S. Makovey
Modified: 2016-01-06 09:23 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-06 09:23:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dmitry S. Makovey 2014-12-19 18:07:43 UTC 
Description of problem:

after fresh install of RDO on the box using https://github.com/AthabascaUniversity/openstack-ng things seem to be functional except for the networking: trying to assign external IP to an instance results in error in logs:

failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not available

downgrading back to dnsmasq-2.48-13.el6.x86_64 and rebooting machine fixes the issue.

Version-Release number of selected component (if applicable):

dnsmasq-2.48-14.el6.x86_64

How reproducible:

I have been able to reproduce this two times - first time on existing setup, second on fresh install.

Steps to Reproduce:
1. either use https://github.com/AthabascaUniversity/openstack-ng or follow http://docs.openstack.org/icehouse/install-guide/install/yum/content/index.html
2. create private network/subnet
3. create public network/subnet
4. create router and configure networks
5. create floating IP
6. create instance
7. try to associate floating IP with instance

Actual results:

/var/log/neutron/dhcp-agent.log:2014-12-19 10:39:42.214 2938 TRACE neutron.agent.dhcp_agent Stderr: '\ndnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not available\n'
/var/log/messages:Dec 19 10:39:42 foohost dnsmasq[7871]: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not available

and while nova list report IP as being assigned - it is not available to external connections.

Expected results:

ability to connect to floater IP

Additional info:

abovementioned playbook follows closely official OpenStack guide for install on RHEL.

redhat-release-server-6Server-6.6.0.2.el6.x86_64
Comment 3 Jan Ščotka 2015-01-19 13:42:49 UTC 
Hi,
Is it possible to add steps for reproducing without openstack?
like, config for dnsmasq. Options what are used at command line for dnsmasq (or how it is scheduled). network topology.
I've discussed with developer, and we are not sure that this is problem in dnsmasq or it is only accident.
    Thanks&Regards
    Honza
Comment 9 Dmitry S. Makovey 2015-01-28 16:59:08 UTC 
Jan, I am not sure I, personally can reproduce the problem without OpenStack - as I am not using dnsmasq directly. Invocation parameters would have to be fished out of Quantum code, which I haven't done and not sure if I will be able to do.
Comment 11 Pavel Šimerda (pavlix) 2015-03-16 11:22:20 UTC 
I don't think we can do anything until we have a proper reproducer. I also only see a trivial initscript difference between the version reported as working and the version reported as failing.
Comment 13 Pavel Šimerda (pavlix) 2016-01-06 09:23:26 UTC 
I believe that this is the very same issue bug #1154953. Same symptoms, same affected version. The above bug report now contains a reproducer and reference to an upstream commit.

*** This bug has been marked as a duplicate of bug 1154953 ***
Note You need to log in before you can comment on or make changes to this bug.