Bug 877764

Summary: initscrits ignore ifcfg config files if /etc/sysconfig/network doesn't exist
Product: [Fedora] Fedora Reporter: Igor Lvovsky <ilvovsky>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: alonbl, anaconda-maint-list, dkenigsb, g.kaviyarasu, iarlyy, iheim, jonathan, lnykryn, lpeer, notting, plautrba, rvykydal, sbueno, vanmeeuwen+fedora, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-20 09:42:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
program.log none

Description Igor Lvovsky 2012-11-18 16:00:01 UTC
Description of problem:

After fresh installed F18 the  /etc/sysconfig/network doesn't exist.
On this point when I create ifcfg files for interface and for bridge on top of this interface and reboot the host the initscripts ignore my ifcfg files and bridge wouldn't be created.
But, if I'll just create an empty /etc/sysconfig/network file and reboot the host again the initscripts create all devices properly



Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Fresh install F18
2. Create 2 ifcfg files:

[root@f18-igor ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
BRIDGE=ovirtmgmt
ONBOOT=yes
NM_CONTROLLED=no
TYPE=Ethernet
HWADDR=52:54:00:22:96:73

[root@f18-igor ~]# cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt 
DEVICE=ovirtmgmt
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=dhcp
DELAY=0
NM_CONTROLLED=no

3. Reboot host
  
Actual results:
Bridge wouldn't be created

Expected results:
Bridge should be created

Additional info:

Comment 1 Igor Lvovsky 2012-11-18 16:07:09 UTC
My F18 has:
initscripts-9.42-1.fc18.2.x86_64

Comment 2 Lukáš Nykrýn 2012-11-19 09:51:30 UTC
This is actually desired behavior
/etc/init.d/network:
if [ ! -f /etc/sysconfig/network ]; then
    exit 6
fi

Anaconda should create this file during installation.

Comment 3 Radek Vykydal 2012-11-19 13:44:40 UTC
I am not able to reproduce the issue and I can't think of any case where anaconda wouldn't create /etc/sysconfig/network.

What kind of installation (LiveCD, DVD, netinst, PXE?) and version of anaconda or compose are you using?

Are you using any kickstart? If so, could you please attach it?

You can check whether the /etc/sysconfig/network file is created by anaconda at the end of installation by switching into tty2 and looking for /mnt/sysimage/etc/sysconfig/network.

Comment 4 Igor Lvovsky 2012-11-19 21:26:38 UTC
(In reply to comment #3)
> I am not able to reproduce the issue and I can't think of any case where
> anaconda wouldn't create /etc/sysconfig/network.
> 
> What kind of installation (LiveCD, DVD, netinst, PXE?) and version of
> anaconda or compose are you using?
> 
> Are you using any kickstart? If so, could you please attach it?
> 
> You can check whether the /etc/sysconfig/network file is created by anaconda
> at the end of installation by switching into tty2 and looking for
> /mnt/sysimage/etc/sysconfig/network.

I installed my F18 from regular DVD and /etc/sysconfig/network definitely wasn't created.
Unfortunately, I already removed it from the host, but I would try to reinstall it again and check anaconda version.

Comment 5 Igor Lvovsky 2012-11-19 21:28:22 UTC
Alon, maybe you can check it on your VM and reply to comment 3 ?

Comment 6 Alon Bar-Lev 2012-11-20 06:53:06 UTC
(In reply to comment #3)
> I am not able to reproduce the issue and I can't think of any case where
> anaconda wouldn't create /etc/sysconfig/network.
> 
> What kind of installation (LiveCD, DVD, netinst, PXE?) and version of
> anaconda or compose are you using?
> 
> Are you using any kickstart? If so, could you please attach it?
> 
> You can check whether the /etc/sysconfig/network file is created by anaconda
> at the end of installation by switching into tty2 and looking for
> /mnt/sysimage/etc/sysconfig/network.

Using: Fedora-18-Alpha-x86_64-DVD.iso
anacoda-18.6.8, text install
/etc/sysconfig/network is not created, there is  no reference for an attempt at /tmp/*.log.

Comment 7 Alon Bar-Lev 2012-11-20 06:56:27 UTC
Created attachment 648293 [details]
anaconda.log

Comment 8 Alon Bar-Lev 2012-11-20 06:57:08 UTC
Created attachment 648294 [details]
program.log

Comment 9 Radek Vykydal 2012-11-20 09:42:33 UTC
(In reply to comment #6)

> 
> Using: Fedora-18-Alpha-x86_64-DVD.iso
> anacoda-18.6.8, text install

You are probably using F18 Alpha, this should be fixed in F18 Beta. If you are still seeing it please reopen the bug.

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