Bug 537887 - patch - honor --noipv6 within modprobe.conf
Summary: patch - honor --noipv6 within modprobe.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.5
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: David Cantrell
QA Contact: Release Test Team
URL:
Whiteboard:
: 649019 (view as bug list)
Depends On:
Blocks: 600484
TreeView+ depends on / blocked
 
Reported: 2009-11-16 17:14 UTC by Adam Stokes
Modified: 2018-11-14 20:27 UTC (History)
10 users (show)

Fixed In Version: anaconda-11.1.2.218-1
Doc Type: Bug Fix
Doc Text:
Previously, the network --noipv6 kickstart command configured /etc/sysconfig/network but did not alter modprobe.conf. Therefore, even when --noipv6 was specified, modprobe would still load the kernel IPv6 modules. The --noipv6 option now disables IPv6 in modprobe.conf too, so the IPv6 kernel modules do not load. (#537887)
Clone Of:
Environment:
Last Closed: 2011-01-13 21:53:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch to alter modprobe.conf (1.00 KB, patch)
2009-11-16 17:14 UTC, Adam Stokes
no flags Details | Diff
anaconda.syslog (15.05 KB, text/plain)
2010-10-05 16:21 UTC, Alexander Todorov
no flags Details
anaconda.log (280.09 KB, text/plain)
2010-10-05 16:22 UTC, Alexander Todorov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 677653 0 medium CLOSED IPv6 support is disabled when IPv6 is not used during installation 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2011:0030 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2011-01-12 15:59:28 UTC

Internal Links: 677653

Description Adam Stokes 2009-11-16 17:14:08 UTC
Created attachment 369749 [details]
patch to alter modprobe.conf

Description of problem:
When using noipv6 it only places a configuration option in /etc/sysconfig/network but modprobe.conf also needs to be altered as well.

Version-Release number of selected component (if applicable):
anaconda-11.x

How reproducible:
100%

Steps to Reproduce:
1. run with --noipv6
2.
3.
  
Actual results:
modprobe.conf still enables ipv6 modules

Expected results:
system should not load ipv6 

Additional info:

Comment 1 Adam Stokes 2009-11-16 18:50:28 UTC
Also I have a question as to if we want to disable ip6tables through the same route rather than accessing it through ksdata.services?

Thanks,
Adam

Comment 2 joshua 2009-11-18 18:58:54 UTC
I'm not sure this is the right approach.  If kickstart or anything else makes /etc/sysconfig/network contain NETWORKING_IPV6=no, it should be considered finished.

Shouldn't the ip6tables and network script then behave appropriately?

Seems like once that is in /etc/sysconfig/network, the network script shouldn't load or activate ipv6 functionality.  The bug to my mind at least isn't that kickstart didn't add a bunch of lines to modprobe.conf

Comment 10 Alexander Todorov 2010-10-05 16:20:34 UTC
Installed with network --device eth0 --bootproto dhcp --noipv6
and the resulting modprobe.conf was:

alias scsi_hostadapter ata_piix
alias eth0 virtio_net
alias scsi_hostadapter1 virtio_blk
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
options snd-intel8x0 index=0
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0


Not even near comment #7

/etc/sysconfig/network contains NETWORKING_IPV6=no


MOving back to ASSIGNED, will attach logs.

Comment 11 Alexander Todorov 2010-10-05 16:21:52 UTC
Created attachment 451719 [details]
anaconda.syslog

Comment 12 Alexander Todorov 2010-10-05 16:22:16 UTC
Created attachment 451720 [details]
anaconda.log

Comment 13 joshua 2010-10-05 17:45:35 UTC
It might make sense to make the network initialization scripts simply not activate IPV6 per an entry in the /etc/sysconfig/network file or something, instead of relying on anaconda to itself tweak files.

Comment 15 David Cantrell 2010-11-10 16:26:40 UTC
*** Bug 649019 has been marked as a duplicate of this bug. ***

Comment 16 Alexander Todorov 2010-12-01 08:52:12 UTC
Tested with snapshot #3 and
network --device eth0 --bootproto dhcp --noipv6

modprobe.conf now matches comment #7 and the patch from comment #0. Moving to VERIFIED.

Comment 17 Ruediger Landmann 2011-01-07 05:17:50 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the network --noipv6 boot option configured 
/etc/sysconfig/network but did not alter modprobe.conf. Therefore, even 
when --noipv6 was specified, modprobe would still load the kernel IPv6
modules. The --noipv6 option now disables IPv6 in modprobe.conf too, so
the IPv6 kernel modules do not load. (#537887)

Comment 18 Ruediger Landmann 2011-01-07 05:18:48 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,4 @@
-Previously, the network --noipv6 boot option configured 
+Previously, the network --noipv6 kickstart command configured 
 /etc/sysconfig/network but did not alter modprobe.conf. Therefore, even 
 when --noipv6 was specified, modprobe would still load the kernel IPv6
 modules. The --noipv6 option now disables IPv6 in modprobe.conf too, so

Comment 20 errata-xmlrpc 2011-01-13 21:53:26 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0030.html


Note You need to log in before you can comment on or make changes to this bug.