Hide Forgot
Created attachment 478878 [details] Reproducer kickstart file Description of problem: After a kickstart installation that does not use IPv6, the resulting system has IPv6 support disabled. This was not the case with RHEL5.5. Version-Release number of selected component (if applicable): anaconda-11.1.2.224-1.x86_64.rpm How reproducible: 100% Steps to Reproduce: 1. Install a RHEL 5.6 VM using the attached kickstart file. Actual results: Installed system ends up with the following at the end of /etc/modprobe.conf: alias net-pf-10 off alias ipv6 off options ipv6 disable=1 Expected results: Installed system has IPv6 support.
Created attachment 478880 [details] Sosreport for RHEL 5.5 installation resulting from the kickstart file
Created attachment 478881 [details] Sosreport for RHEL 5.6 installation resulting from the kickstart file
This is probably result of patches fixing bug #537887.
That was my suspicion as well (which is why I added that bug under See Also). It is described in <http://rhn.redhat.com/errata/RHBA-2011-0030.html> as follows: > * Anaconda alters modprobe.conf to ensure that kernel IPv6 modules are no > longer loaded if the kickstart --noipv6 option is used (BZ#537887) This sounds like a very reasonable thing to do. What we have in this bug though, is something else: there is no "--noipv6" in the kickstart file, yet IPv6 ends up disabled. As such, I think that what we have here is more like an "unintended side effect" rather than a regular "result" of the patches from bug #537887.
Didn't you disable ipv6 with boot option noipv6 or in UI?
No, I did not. In my testing, I'm using a RHEL5.6 host environment and I'm installing in KVM guests. I have attached the RHEL5.[56] ISO as a CD-ROM that I'm booting the guest from, and I've attached a FAT-formatted floppy image to it that holds the kickstart file. The kernel command line I used was "linux ks=floppy", and the only input provided interactively was skipping entering of an installation number.
Ah, thanks for the info, finally I reproduced it - it concerns specifically media installs.
Created attachment 479088 [details] Patch with fix. Patch with fix attached. This updates image containing the patch should fix the issue: http://rvykydal.fedorapeople.org/updates.677653.img It can be applied by adding updates=http://rvykydal.fedorapeople.org/updates.677653.img to boot options.
I could not make it work using "updates=http://rvykydal.fedorapeople.org/updates.677653.img", but after combining the contents of this image and the kickstart file into a new floppy image and using "updates ks=floppy", the resulting VM did not have IPv6 disabled so the patch is fine as far as I can tell. Nice work!
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
This should be fixed in anaconda-11.1.2.229-1.
Successfully reproduced on RHEL5.6 running in KVM, installing from cdrom and kickstart stored on disk. Retested on build RHEL5.7-Server-20110525.0 with anaconda-11.1.2.236-1.x86_64.rpm: [root@system1 ~]# cat /etc/modprobe.conf alias scsi_hostadapter ata_piix alias eth0 virtio_net alias scsi_hostadapter1 virtio_blk [root@system1 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.0.11/24 brd 10.0.0.255 scope global eth0 inet6 fd16::5054:ff:fe12:3456/64 scope global dynamic valid_lft 86355sec preferred_lft 14355sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever 3: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 Moving to VERIFIED.
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-0984.html
minor nit: even with this fix, if a 'network' entry isn't present in the kickstart file, the ipv6 modules will continue to be disabled.
(In reply to comment #16) > minor nit: even with this fix, if a 'network' entry isn't present in the > kickstart file, the ipv6 modules will continue to be disabled. This should be fixed in 5.8 with bug 713120.