Bug 708409

Summary: ifup-eth cannot handle GATEWAY0
Product: [Fedora] Fedora Reporter: Than Ngo <than>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: aj.werkman, anaconda-maint-list, dcbw, iarlyy, initscripts-maint-list, ipilcher, jklimes, jonathan, kvolny, notting, plautrba, rvokal, rvykydal, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 771673 (view as bug list) Environment:
Last Closed: 2013-02-13 19:30:31 UTC Type: ---
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: 771673    
Attachments:
Description Flags
Take default route from either GATEWAY,GATEWAY0,GATEWAY1 or GATEWAY2 none

Description Than Ngo 2011-05-27 15:10:33 UTC
Description of problem:

the ifcfg-eth0 which is created from anaconda, includes wrong GATEWAY0 variable. It cannot be handled in ifup-eth script.

Steps to Reproduce:
set NM_CONTROLLED="no" in /etc/sysconfig/network-scripts/ifcfg-eth0
  
Actual results:
default route is not activated

Expected results:
default route should be activated

Additional info:
change GATEWAY0 to WATEWAY resolves this issue

Comment 1 Radek Vykydal 2011-05-27 15:28:00 UTC
Please attach installation logs from /var/log/anaconda directory of installed system (files anaconda.log, anaconda.syslog, anaconda.ifcfg.log).

The log files can be also found in installer environment in /tmp directory in shell on tty2 (Ctrl-Alt-F2) (anaconda.log, syslog, ifcfg.log).

Comment 2 Radek Vykydal 2011-09-22 11:11:38 UTC
(In reply to comment #1)
> Please attach installation logs from /var/log/anaconda directory of installed
> system (files anaconda.log, anaconda.syslog, anaconda.ifcfg.log).
> 
> The log files can be also found in installer environment in /tmp directory in
> shell on tty2 (Ctrl-Alt-F2) (anaconda.log, syslog, ifcfg.log).

Not needed anymore. It happens when using NetworkManager Connection Editor. I
am passing the bug to NM. Might be a duplicate of bug 739403.

Comment 3 Jirka Klimes 2011-09-26 13:35:25 UTC
*** Bug 739403 has been marked as a duplicate of this bug. ***

Comment 4 Jirka Klimes 2011-09-26 13:41:16 UTC
The bug 633984 changed handling of multiple addresses via IPADDRn. But the setting of default gateway in ifup-eth is still according to GATEWAY. It has to be fixed to make the script work together with the the mentioned changes.

Comment 5 Jirka Klimes 2011-09-26 13:45:01 UTC
Created attachment 524910 [details]
Take default route from either GATEWAY,GATEWAY0,GATEWAY1 or GATEWAY2

Look for default route in multiple variables to make it in accord with the changes for bug 633984 and to work for ifcfg files created by NM.

Comment 6 Bill Nottingham 2011-09-26 21:00:34 UTC
Hm, why would anaconda support multiple GATEWAY settings for a particular device? That doesn't make sense.

Comment 7 Ian Pilcher 2011-12-22 17:26:43 UTC
This issue still exists in Fedora 16.

Comment 8 Bill Nottingham 2012-01-03 19:08:43 UTC
Is it anaconda or NM that's writing GATEWAY<N>? Either way, that should likely be fixed.

Comment 9 David Cantrell 2012-01-03 20:15:12 UTC
anaconda writes a GATEWAY line if you provide a gateway= boot parameter or one in a kickstart file.  It also preserves any GATEWAY lines that exist in the ifcfg-ethX file.

Comment 10 Bill Nottingham 2012-01-03 22:24:22 UTC
'GATEWAY' is fine. GATEWAY0/GATEWAY1/GATEWAY2/GATEWAY3 is arguably invalid, since you can only ever have one.

Comment 11 Radek Vykydal 2012-01-04 09:52:16 UTC
(In reply to comment #8)
> Is it anaconda or NM that's writing GATEWAY<N>? Either way, that should likely
> be fixed.

It is NM (NetworkManager Connection Editor, which is used in installer GUI), see comment #2.

Comment 12 Bill Nottingham 2012-01-04 15:12:28 UTC
OK, cloning.

Comment 13 Bill Nottingham 2012-05-24 13:00:19 UTC
*** Bug 824808 has been marked as a duplicate of this bug. ***

Comment 14 Frode Tennebø 2012-05-24 19:30:37 UTC
(In reply to comment #10)
> 'GATEWAY' is fine. GATEWAY0/GATEWAY1/GATEWAY2/GATEWAY3 is arguably invalid,
> since you can only ever have one.

Please also update docs:

http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/s1-networkscripts-static-routes.html

Comment 15 Fedora End Of Life 2013-01-16 16:07:29 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 Fedora End Of Life 2013-02-13 19:30:38 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.