Red Hat Bugzilla – Bug 829499
NetworkManager tries to enable an interface only once
Last modified: 2013-02-21 05:34:47 EST
After a network outage, NetworkManager-managed 6.2 machines lost their IP addresses and required manual operator intervention to restart the network.
This is surprising as 4.x and 5.x machines (before the NetworkManager) did not lose their IP addresses during similar network outages and continued to operate normally after network connectivity was restored.
This is the network diagram:
This is what happened:
- power was lost on SWITCH1 and SWITCH2
- NetworkManager detected link loss and disabled the network on MYHOST (as expected)
- power was restored on SWITCH1
- NetworkManager detected link presence, tried to acquire an IP address (with a 45 sec timeout) (as expected)
- since SWITCH2 was still down, there was no DHCP reply
- after the 45 sec timeout, NetworkManager disabled the interface, there was no further NetworkManager activity afterwards (wrong - expected the NetworkManager to try several times, if not forever, before giving up)
- power was restored to SWITCH2, but the NetworkManager on MYHOST cannot see this
Before suggesting that all network switches should have UPS power and should never ever be shutdown, consider the case of scheduled maintenance and power outages where *I* cannot control the order in which the switches are powered back up or reconnected.
Is it possible to configure the NetworkManager was a longer timeout? With an option to try again after 30 min or after 1 hour?
Created attachment 591159 [details]
[PATCH] retry auto-connection 3 more times when it fails and again in 5 minute intervals
The patch implements automatic connection retries (first attempt + 3 retries) when auto-activation failed. And, then it tries again 4 times after 5 minutes.
It is basically a re-implementation of the feature present in NM upstream master branch for RHEL 6.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
could we ask you to retest in case you have access to newest NetworkManager?
Thanks in advance
(In reply to comment #11)
> could we ask you to retest in case you have access to newest NetworkManager?
I am happy to retest, but you have to specify which "newest" NetworkManager you want me to test (and if it's a RH private test RPM, make it available for my download - you can send the secret URL to my email. I will not share the RPM file with anybody.) email@example.com, firstname.lastname@example.org
(In reply to comment #12)
> (In reply to comment #11)
> > could we ask you to retest in case you have access to newest NetworkManager?
> I am happy to retest, but you have to specify which "newest" NetworkManager
> you want me to test (and if it's a RH private test RPM, make it available
> for my download - you can send the secret URL to my email. I will not share
> the RPM file with anybody.) email@example.com, firstname.lastname@example.org
NetworkManager-0.8.1-39.el6 is available via RHN rhel-x86_64-server-6-beta (or client/workstation/... depends on your rhel variant) channel.
More info at https://rhn.redhat.com/rhn/software/channels/Beta.do
Or the direct link  to download via web UI might work as well.
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.