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 1136836 - dhcp: DHCP client exits abnormally when journald is restarted
Summary: dhcp: DHCP client exits abnormally when journald is restarted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Jirka Klimes
QA Contact: Desktop QE
URL:
Whiteboard:
: 1084604 (view as bug list)
Depends On:
Blocks: 1110708
TreeView+ depends on / blocked
 
Reported: 2014-09-03 12:04 UTC by Jirka Klimes
Modified: 2016-01-04 06:04 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-0.9.9.1-35.git20140326.4dba720.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:52:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
[PATCH] RHEL7 patch fixing the issue (6.83 KB, patch)
2014-09-03 12:17 UTC, Jirka Klimes
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 735962 0 None None None 2019-05-14 02:12:26 UTC
Red Hat Product Errata RHBA-2015:0311 0 normal SHIPPED_LIVE NetworkManager bug fix and enhancement update 2015-03-05 17:35:10 UTC

Description Jirka Klimes 2014-09-03 12:04:02 UTC
DHCP client exits abnormally when run by NetworkManager and thus the connection
cannot be properly activated.

The error can be triggered by restarting systemd-journald. After doing that,
DHCP client will not start properly, but exits with:
  <info> (enp0s25): DHCPv4 client pid 13959 exited with status -1
  <warn> DHCP client died abnormally

See upstream bug for details:
https://bugzilla.gnome.org/show_bug.cgi?id=735962

Comment 1 Jirka Klimes 2014-09-03 12:17:51 UTC
Created attachment 934067 [details]
[PATCH] RHEL7 patch fixing the issue

The upstream bug contains a fix for the problem. This patch is a rebase of the upstream fix for RHEL7 codebase.

Comment 3 Jirka Klimes 2014-09-12 19:17:13 UTC
Fixed upstream by:
e47235b dhcp: log DHCP client exit status better
b276696 dhcp: fix dhclient abnormal exit due to SIGPIPE (bgo #735962)

Comment 6 Vladimir Benes 2014-09-15 10:12:19 UTC
*** Bug 1084604 has been marked as a duplicate of this bug. ***

Comment 7 Trond H. Amundsen 2014-10-02 11:07:14 UTC
Hi,

This bug is hitting us pretty hard. Is the -35 rpm (or srpm) available somewhere?

-trond

Comment 10 errata-xmlrpc 2015-03-05 13:52:51 UTC
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-0311.html


Note You need to log in before you can comment on or make changes to this bug.