+++ This bug was initially created as a clone of Bug #698738 +++
Created attachment 493918 [details]
really accept IPADDR0 in ifcfg file
Description of problem:
When I give static address to eth1 via NM,
switch NM off and try to use network service
I end up with no address assigned to eth1.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure eth1 with NetworkManager to statically assign IP address/prefix
2. Check that eth1 has its address
2. stop NM (or set NM_CONTROLLED="no" in ifcfg-eth1)
3. ifdown eth1; ifup eth1
eth1 is up but has no IP address
eth1 is up and has configured IP address
adds support for IPADDRn variable
ifup-eth is still unable to use for example
written to ifcfg-eth1 by NM.
Attached patch fixes the problem in my environment.
--- Additional comment from email@example.com on 2011-04-21 12:26:23 EDT ---
Created attachment 493919 [details]
Polish the code little bit
This patch only fixes the indentation of the code, nothing more.
--- Additional comment from firstname.lastname@example.org on 2011-04-25 15:04:12 EDT ---
Can you attach your config?
--- Additional comment from email@example.com on 2011-04-26 04:50:53 EDT ---
Created attachment 494835 [details]
ifcfg-eth1 created by NM
I only added
--- Additional comment from firstname.lastname@example.org on 2011-04-26 16:34:42 EDT ---
Created attachment 495033 [details]
Maybe I'm missing something, but this patch seems to be simple enough and works for me?
--- Additional comment from email@example.com on 2011-04-27 07:00:38 EDT ---
Yes, that does actually the same as my patch, so +1 for your patch.
--- Additional comment from firstname.lastname@example.org on 2011-04-27 13:11:16 EDT ---
OK, pushed in git, will be in a future build.
--- Additional comment from email@example.com on 2011-04-27 13:11:47 EDT ---
... pushed as git commit 318d859b9df0131a80cdfa7b6a12066bd5212965.
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.