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.
Created attachment 1652495[details]
terminal log
Description of problem:
Even if ipv4.dhcp-timeout is set to infinity, the connection is deactivated if the DHCP server does not respond on renewal.
Version-Release number of selected component (if applicable):
NetworkManager-1.20.0-3.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Setup bridge with dhcp and ipv4.dhcp-timeout=infinity
2. Activate the bridge, bridge will get an IP address via DHCP
3. Kill the dhcp server
Actual results:
NetworkManager deactivates the connection and removes the bridge.
Expected results:
NetworkManager keeps the connection active and the bridge can still work on layer 2.
Additional info:
Comment 2Beniamino Galvani
2020-01-29 10:01:50 UTC
Comment 7Beniamino Galvani
2020-02-04 09:49:40 UTC
Hi, it seems to work fine here:
# nmcli connection modify veth0+ ipv4.dhcp-timeout infinity
# nmcli connection up veth0+ &
[1] 17007
# journalctl -u NetworkManager -e
...
Feb 04 10:46:11 fedora NetworkManager[16447]: <info> [1580809571.7718] device (veth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 04 10:46:11 fedora NetworkManager[16447]: <info> [1580809571.7721] dhcp4 (veth0): activation: beginning transaction (no timeout)
# nmcli --version
nmcli tool, version 1.22.6
Are you sure the connection was reactivated after you changed the timeout?
It is working fine when specified on connection profile. It does not work in /etc/NetworkManager/conf.d/*.conf but int32 max is doing so this is fine by me.
> It is working fine when specified on connection profile. It does not work in /etc/NetworkManager/conf.d/*.conf but int32 max is doing so this is fine by me.
Please share the exact configuration file that you used. Did you reload the configuration after editing the file? Did you leave the corresponding setting in the profile at "0", so that the default can take effect?
We might need a level=TRACE log to understand this issue.
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://access.redhat.com/errata/RHBA-2020:1847
Created attachment 1652495 [details] terminal log Description of problem: Even if ipv4.dhcp-timeout is set to infinity, the connection is deactivated if the DHCP server does not respond on renewal. Version-Release number of selected component (if applicable): NetworkManager-1.20.0-3.el8.x86_64 How reproducible: 100% Steps to Reproduce: 1. Setup bridge with dhcp and ipv4.dhcp-timeout=infinity 2. Activate the bridge, bridge will get an IP address via DHCP 3. Kill the dhcp server Actual results: NetworkManager deactivates the connection and removes the bridge. Expected results: NetworkManager keeps the connection active and the bridge can still work on layer 2. Additional info: