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.

Description of problem:
dhcpd service will not start on boot when bridge interface is configured

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

How reproducible:
happens on reboot of the system

Steps to Reproduce:
1. configure bridge device
2. install and configure dhcpd scope
3. reboot

Actual results:
dhcpd fails to start on reboot.

Expected results:
dhcpd should start properly

Additional info:
if i add this "After=network.service" this seems to be related to NetworkManager based on the fix listed.

Example:

[Unit]
Description=Network Manager
Wants=network.target
Before=network.target network.service
After=network.service  <---this is what has been added

[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
ExecStart=/usr/sbin/NetworkManager --no-daemon
# NM doesn't want systemd to kill its children for it
KillMode=process

[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service

Fedora has a similar bug "771009"

Could you try to use:
Wants=network-online.target
After=network-online.target

instead of
After=network.target

that's what we've done on Fedora recently:
http://pkgs.fedoraproject.org/cgit/dhcp.git/commit/?id=0b1fc62ff4128534f86220030a023ae68c77ee2d

Hi Jiri

Can confirm the above works as expected. dhcpd starts on reboot properly with bridge configured. after i make the above changes you posted.

I was not able to reproduce this bug, thus based on patches present both in srpm and specfile I'm setting a SanityOnly flag.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0450.html