Bug 977555

Summary:	dnsmasq: failed to set SO_REUSE{ADDR\|PORT} on DHCP socket: Protocol not available
Product:	[Fedora] Fedora	Reporter:	Suren Karapetyan <suren>
Component:	dnsmasq	Assignee:	Tomáš Hozza <thozza>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	18	CC:	aquini, berrange, clalancette, derekh, itamar, jdenemar, jdulaney, jforbes, jyang, laine, libvirt-maint, markmc, plarsen, suren, thozza, veillard
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	dnsmasq-2.65-7.fc18	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	950755	Environment:
Last Closed:	2013-08-04 00:03:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	950755
Bug Blocks:

Description Suren Karapetyan 2013-06-24 22:00:31 UTC

+++ This bug was initially created as a clone of Bug #950755 +++

Description of problem:
Libvirt fails to start virtual networks with DHCP enabled.

Version-Release number of selected component (if applicable): dnsmasq-2.65-6.fc18.x86_64

How reproducible:
Always

Steps to Reproduce:
1.  Start libvirtd with default config.
  
Actual results:
"default" virtual network doesn't start

Expected results:
"default" virtual network starts

More info:
rebuilding the dnsmasq-2.66-3.fc19 src.rpm for fc18 does indeed fix the problem for me. Can we please have it built and pushed to stable?

--- Additional comment from Jiri Denemark on 2013-04-12 05:30:54 EDT ---

As far as I know, this should be fixed in dnsmasq-2.66rc5

--- Additional comment from Fedora Update System on 2013-04-12 06:08:20 EDT ---

dnsmasq-2.66-1.rc5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/dnsmasq-2.66-1.rc5.fc19

--- Additional comment from Fedora Update System on 2013-04-18 13:24:33 EDT ---

Package dnsmasq-2.66-2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnsmasq-2.66-2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5540/dnsmasq-2.66-2.fc19
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-04-22 13:19:49 EDT ---

Package dnsmasq-2.66-3.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnsmasq-2.66-3.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5540/dnsmasq-2.66-3.fc19
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-05-03 21:46:06 EDT ---

dnsmasq-2.66-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from Suren Karapetyan on 2013-06-24 03:13:57 EDT ---

Can we have this fixed on Fedora 18?

--- Additional comment from Tomas Hozza on 2013-06-24 03:19:04 EDT ---

(In reply to Suren Karapetyan from comment #6)
> Can we have this fixed on Fedora 18?

Sure, can you please create F18 Bug? Thanks!

Comment 1 Derek Higgins 2013-07-16 11:51:47 UTC

+1 to fixing this, I started hitting it today on F18 (looks like its ever since dnsmasq-2.65-6.fc18 was push to updates)

Comment 2 Tomáš Hozza 2013-07-16 13:40:46 UTC

Can you please test the following build?

http://koji.fedoraproject.org/koji/taskinfo?taskID=5612726

Thanks!

Comment 3 Derek Higgins 2013-07-17 00:08:29 UTC

works for me

Comment 4 Fedora Update System 2013-07-17 06:39:28 UTC

dnsmasq-2.65-7.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/dnsmasq-2.65-7.fc18

Comment 5 Fedora Update System 2013-07-18 06:04:37 UTC

Package dnsmasq-2.65-7.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnsmasq-2.65-7.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-13204/dnsmasq-2.65-7.fc18
then log in and leave karma (feedback).

Comment 6 Peter Larsen 2013-07-21 13:59:44 UTC

Had the exact same problem - the updates-testing does fix it. Thanks for fixing this so quickly!

Comment 7 Fedora Update System 2013-08-04 00:03:59 UTC

dnsmasq-2.65-7.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.