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

Bug 2103177

Summary: disabling ipv6 router advertisements using "all" does not disable it on secondary interfaces
Product: OpenShift Container Platform Reporter: Douglas Smith <dosmith>
Component: NetworkingAssignee: Douglas Smith <dosmith>
Networking sub component: multus QA Contact: Weibin Liang <weliang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: dornelas, dosmith, nagrawal, ncocker, tsweeney, weliang
Version: 4.7   
Target Milestone: ---   
Target Release: 4.11.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2103175
: 2103178 (view as bug list) Environment:
Last Closed: 2022-08-10 11:19:39 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: 2103178    
Bug Blocks: 2103175    

Description Douglas Smith 2022-07-01 15:34:52 UTC 
+++ This bug was initially created as a clone of Bug #2103175 +++

+++ This bug was initially created as a clone of Bug #2101664 +++

Description of problem:
OCP 4.7, and 4.9 

Trying to disable the use of SLAAC within a container consuming an SRIOV vf using the net.ipv6.conf.all.accept_ra":  0

does not appear to disable it on the secondary interface in the pod

we set the following sysctl

net.ipv6.conf.all.accept_ra = 0

and looking at the secondary interface (nabeel1) see:

net.ipv6.conf.nabeel1.accept_ra = 1


We are still working to gather some more information and data but we were alerted to the following and not sure if that is what is affecting us:

https://github.com/containernetworking/plugins/pull/669

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Tom Sweeney on 2022-06-30 00:30:53 UTC ---

This seems like an OCP issue to me, assigning to Peter to take a look .  @dornelas if you have thoughts on other landing spots, please let me know.

--- Additional comment from Douglas Smith on 2022-06-30 13:16:29 UTC ---

Looks like a fix to the container networking plugins. Assigning to me.
Comment 1 Douglas Smith 2022-07-01 16:00:35 UTC 
For verification, use this YAML:

```
---
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: example-tuning-conf
spec:
  config: >
    {
      "cniVersion": "0.4.0",
      "name": "example-tuning-conf",
      "plugins": [{
        "type": "bridge",
        "bridge": "test1234",
        "ipam": {
          "type": "host-local",
          "subnet": "192.168.1.0/24",
          "rangeStart": "192.168.1.200",
          "rangeEnd": "192.168.1.216",
          "routes": [
            { "dst": "0.0.0.0/0" }
          ],
          "gateway": "192.168.1.1"
        }
      },
        {
          "type": "tuning",
          "sysctl": {
            "net.ipv6.conf.IFNAME.accept_ra": "0"
          }
        }
      ]
    }
---
apiVersion: v1
kind: Pod
metadata:
  name: samplepod
  annotations:
    k8s.v1.cni.cncf.io/networks: example-tuning-conf
spec:
  containers:
  - name: samplepod
    command: ["/bin/ash", "-c", "trap : TERM INT; sleep infinity & wait"]
    image: alpine
```

The resulting pod should have accept_ra set to zero, such as:

```
$ oc exec -it samplepod -- cat /proc/sys/net/ipv6/conf/net1/accept_ra
0
```
Comment 3 Weibin Liang 2022-07-14 15:22:32 UTC 
Tested and verified in 4.11.0-rc.2

[weliang@weliang Test]$ oc exec -it samplepod -- cat /proc/sys/net/ipv6/conf/net1/accept_ra
0
[weliang@weliang Test]$ oc get clusterversion
NAME      VERSION       AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-rc.2   True        False         165m    Cluster version is 4.11.0-rc.2
[weliang@weliang Test]$
Comment 4 errata-xmlrpc 2022-08-10 11:19:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069