Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1084604

Summary: cannot start infiniband connection as dhcp failing
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: aloughla, danw, dcbw, dledford, jklimes, thaller, vbenes
Target Milestone: rc   
Target Release: 7.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-15 10:12:19 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:    
Bug Blocks: 1110708    
Attachments:
Description Flags
messages with failure
none
DEBUG enabled messages none

Description Vladimir Benes 2014-04-04 19:33:35 UTC 
Description of problem:
I am seeing issue with dhcp when NM is trying to start infiniband connection. When I restart NM service it's working again. It was caused by some disconnection or profile delete, not really sure. I can reproduce it 100% in my automated tests.
It is usually broken until NM service restart. Still the same error. 

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.1-11.git20140326.4dba720.el7.x86_64
Comment 1 Vladimir Benes 2014-04-04 19:35:18 UTC 
Created attachment 882831 [details]
messages with failure
Comment 2 Dan Williams 2014-04-04 19:40:04 UTC 
Apr  4 09:38:58 rdma-qe-11 NetworkManager[12139]: <info> dhclient started with pid 12719
Apr  4 09:38:58 rdma-qe-11 NetworkManager[12139]: <info> Activation (mlx4_ib1) Stage 3 of 5 (IP Configure Start) complete.
Apr  4 09:38:58 rdma-qe-11 dhclient[12719]: Internet Systems Consortium DHCP Client 4.2.5
Apr  4 09:38:58 rdma-qe-11 NetworkManager[12139]: <info> (mlx4_ib1): DHCPv4 client pid 12719 exited with status -1
Apr  4 09:38:58 rdma-qe-11 NetworkManager[12139]: <warn> DHCP client died abnormally

Vlad, can you run with --log-level=debug or set the log level in NetworkManager.conf so we can see exactly what NM is passing to dhclient here?
Comment 3 Vladimir Benes 2014-04-04 21:48:14 UTC 
Dan, it's quite funny race condition. Thomas advised me to enlarge journald limits by running:
    sed -i 's/^#\?\(RateLimitInterval *= *\).*/\10/' /etc/systemd/journald.conf
    sed -i 's/^#\?\(RateLimitBurst *= *\).*/\10/' /etc/systemd/journald.conf
    systemctl restart systemd-journald.service

but this journald restart causes it. When I restart NM after that it works again. See DEBUG logs attached.
Comment 4 Vladimir Benes 2014-04-04 21:48:39 UTC 
Created attachment 882880 [details]
DEBUG enabled messages
Comment 5 Dan Williams 2014-04-08 15:23:13 UTC 
Hmm, the logs don't make things clearer to me unfortunately.  Can you try something for me?  Just leave everything up at that point, and:

1) nmcli dev disconnect mlx4_ib1
2) dhclient -v -d -1 mlx4_ib1

and lets see what dhclient says when it fails.  If it actually crashes, would you be able to install gdb on that machine and then 'gdb dhclient' and 'run -v -d -1 mlx4_ib1' to get a backtrace?  Then we can figure out whether this is a dhclient bug or an NM bug.
Comment 6 Dan Williams 2014-06-17 23:42:20 UTC 
Vlad, any chance you could grab the info requested in comment 5?  Thanks!
Comment 8 Vladimir Benes 2014-09-15 10:12:19 UTC 
(In reply to Vladimir Benes from comment #3)
> Dan, it's quite funny race condition. Thomas advised me to enlarge journald
> limits by running:
>     sed -i 's/^#\?\(RateLimitInterval *= *\).*/\10/'
> /etc/systemd/journald.conf
>     sed -i 's/^#\?\(RateLimitBurst *= *\).*/\10/' /etc/systemd/journald.conf
>     systemctl restart systemd-journald.service
> 

^^^^ this says it quite clearly a duplicate of 1136836

I reproduced, then updated NM to -35 version and it just works since then

*** This bug has been marked as a duplicate of bug 1136836 ***