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 950568 - Cannot start default network
Summary: Cannot start default network
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dnsmasq
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomáš Hozza
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-10 12:30 UTC by Matěj Cepl
Modified: 2014-01-24 12:07 UTC (History)
3 users (show)

Fixed In Version: dnsmasq-2.66-1.rc5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-24 12:07:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matěj Cepl 2013-04-10 12:30:22 UTC 
Description of problem:
wycliff:~# virsh net-start default
error: Failed to start network default
error: internal error Child process (/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf) unexpected exit status 2: 
dnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not available


Version-Release number of selected component (if applicable):
libvirt-1.0.4-1.el7.x86_64
qemu-kvm-1.4.0-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.try to start a virtual machine
2.OK, so that failed because of missing network
3.try to start network
  
Actual results:
fails with the above error

Expected results:
it shouldn't fail, and in fact the default network should be running on its own

Additional info:
Comment 1 Jiri Denemark 2013-04-10 12:35:43 UTC 
dnsmasq is complaining it cannot set SO_REUSE{ADDR|PORT}, which seems like something's wrong between dnsmasq and the kernel.
Comment 4 Tomáš Hozza 2013-04-10 18:24:32 UTC 
Tested dnsmasq-2.65-1.el7 with

libvirt-1.0.4-1.el7
qemu-kvm-1.4.0-2.el7

on RHEL7 (kernel 3.7.0-0.36.el7.x86_64)

and everything works just fine.

# virsh net-info default
Name            default
UUID            104d068f-56d2-4fa3-b070-bd25aab87066
Active:         yes
Persistent:     yes
Autostart:      yes
Bridge:         virbr0

# ps aux | grep dnsmasq
nobody    1099  0.0  0.0  13188   696 ?        S    20:19   0:00 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf

Do you have any more specific steps to reproduce?
Comment 5 Matěj Cepl 2013-04-11 15:04:12 UTC 
Hmm,

wycliff:~# virsh net-info default
Name            default
UUID            abcbc106-c2de-4212-8aa2-4e43ffcdb142
Active:         no
Persistent:     yes
Autostart:      yes
Bridge:         virbr0
wycliff:~# virsh net-dumpxml default
<network>
  <name>default</name>
  <uuid>abcbc106-c2de-4212-8aa2-4e43ffcdb142</uuid>
  <forward mode='nat'/>
  <bridge name='virbr0' stp='on' delay='0' />
  <mac address='52:54:00:69:88:BD'/>
  <ip address='192.168.122.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.122.2' end='192.168.122.254' />
    </dhcp>
  </ip>
</network>

wycliff:~# brctl show
bridge name	bridge id		STP enabled	interfaces
wycliff:~#
Comment 6 Tomáš Hozza 2013-04-11 18:46:39 UTC 
Please include exact dnsmasq version, kernel version, RHEL-7 snapshot version
so I can reproduce it.

Thank you!
Comment 7 Matěj Cepl 2013-04-12 06:01:00 UTC 
matej@wycliff: beaker-job-XMLs (master *)$ cat /etc/redhat-release 
Red Hat Enterprise Linux Workstation release 7.0 Alpha3 (Maipo)
matej@wycliff: beaker-job-XMLs (master *)$ rpm -q dnsmasq kernel
dnsmasq-2.66-1rc1.el7.x86_64
kernel-3.8.0-0.40.el7.x86_64
matej@wycliff: beaker-job-XMLs (master *)$ uname -a
Linux wycliff.ceplovi.cz 3.8.0-0.40.el7.x86_64.debug #1 SMP Thu Feb 28 17:49:06 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
matej@wycliff: beaker-job-XMLs (master *)$
Comment 8 Tomáš Hozza 2013-04-12 06:52:45 UTC 
Finally I see the problem with the newest dnsmasq. It seems to be already fixed in dnsmasq-2.66rc5. I'll rebase the package and let you know so you can test it.
Comment 9 Tomáš Hozza 2013-04-12 08:10:50 UTC 
I just tested dnsmasq-2.66-1.rc5.el7 [1] and it works OK. Please test it and let
me know so I can close this Bug.

Thanks!

[1] https://brewweb.devel.redhat.com/buildinfo?buildID=266444
Comment 10 Matěj Cepl 2013-04-12 09:03:24 UTC 
Yes, this has been fixed.

Thank you
Comment 11 Tomáš Hozza 2013-04-12 09:11:04 UTC 
Fixed in dnsmasq-2.66-1.rc5.el7.
Note You need to log in before you can comment on or make changes to this bug.