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.

Currently, either IPv4 or IPv6 dynamic configuration may timeout (may-fail), but not both without the connection is deactivated.
There should be a way to configure NetworkManager, that both, IPv4 and IPv6 dynamic configuration may timeout, without that the connection is deactivated.
This would be useful, if the connection is useful even without layer 3 networking, e.g. a bridge.

The infinity timeout is the current solution for this problem as described in: https://bugzilla.redhat.com/show_bug.cgi?id=1791624#c2
It does not seem to be necessary to keep both bugs open since the next step in the other bug is probably also adressing this issue. Therefore I close this one as a duplicate.

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