Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When installing a new system thanks to a kickstart, we use the network directive with the --noipv6 option, which leads to a IPV6INIT=no in the ifcfg file. inet6 is active on this interface anyway. If this property is deprecated, the bug is in anaconda.

Version-Release number of selected component (if applicable):
NetworkManager-1.14.0-14.el8.x86_64

How reproducible:
Just setup a new server with the following ks directive:
network --bootproto=dhcp --nodns --device=ens3 --onboot=on --noipv6 --activate

It is maybe the same if you set IPV6INIT to no in your ifcfg file.

Actual results:
[root@foo ~]# ip -6 a sh dev ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 fe80::5054:ff:fe52:c9ec/64 scope link 
       valid_lft forever preferred_lft forever
[root@foo ~]# cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6 
0

Expected results:
[root@foo ~]# ip -6 a sh dev ens3
[root@foo ~]# cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6 
1

Additional info:
echo net.ipv6.conf.ens3.disable_ipv6=1 >> /etc/sysctl.d/50-noipv6.conf
in the ks %post section fixes the issue for me.

Since NM 1.20 it is possible to completely disable IPv6 on an interface by setting ipv6.method=disabled, which corresponds to

IPV6INIT=no
IPV6_AUTOCONF=yes

in the ifcfg-rh file. Only setting IPV6INIT=no is equivalent to ipv6.method=ignore which makes NM ignore the IPv6 configuration of the interface but doesn't prevent the kernel from doing IPv6 autoconf.

If the intent of '--noipv6' in the kickstart file is to completely disable IPv6, I think the installer should set both the keys above in the ifcfg-rh file. I'm reassigning this bug to anaconda for consideration.

Ops, the correct keys to set ipv6.method=disabled are:

IPV6INIT=no
IPV6_DISABLED=yes