Bug 1739961

Summary: cannot find "static" IPAM module and IPAM support for the host-device module
Product: Red Hat Enterprise Linux 8 Reporter: Suhaas Bhat <subhat>
Component: containernetworking-pluginsAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: low Docs Contact:
Priority: medium    
Version: 8.0CC: ajia, dornelas, lsm5, pthomas
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 21:02:57 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:
Bug Depends On:    
Bug Blocks: 1186913, 1734574    

Description Suhaas Bhat 2019-08-12 01:56:34 UTC
Description of problem:
1. "static" IPAM module  (https://github.com/containernetworking/plugins/pull/136 and https://github.com/containernetworking/plugins/pull/165)

2. IPAM support for the host-device module (https://github.com/containernetworking/plugins/pull/220)

Version-Release number of selected component (if applicable):
containernetworking-plugins-0.8.1-2.module+el8.1.0+3888+8b36fd52.x86_64

Comment 4 Alex Jia 2019-09-27 09:33:07 UTC
This bug has been verified in containernetworking-plugins-0.8.1-2.module+el8.1.0+4081+b29780af.x86_64

[root@kvm-06-guest17 ~]# rpm -q containernetworking-plugins
containernetworking-plugins-0.8.1-2.module+el8.1.0+4081+b29780af.x86_64

[root@kvm-06-guest17 ~]# ip netns ls
cni-f84f15ab-c7c4-ec64-018f-791b45e7353c (id: 0)

[root@kvm-06-guest17 ~]# ip netns add mycninet

[root@kvm-06-guest17 ~]# ip netns ls
mycninet
cni-f84f15ab-c7c4-ec64-018f-791b45e7353c (id: 0)

[root@kvm-06-guest17 ~]# cat bridge.conf
{
  "cniVersion": "0.4.0",
  "name": "dbnet",
  "type": "bridge",
  "bridge": "cni0",
  "ipam": {
    "type": "host-local",
    "subnet": "10.1.0.0/16",
    "gateway": "10.1.0.1"
  },
  "dns": {
    "nameservers": [ "10.1.0.1" ]
  }
}

[root@kvm-06-guest17 ~]# ip netns exec mycninet ifconfig -a
lo: flags=8<LOOPBACK>  mtu 65536
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@kvm-06-guest17 ~]# CNI_COMMAND=ADD CNI_CONTAINERID=1234567890 CNI_NETNS=/var/run/netns/mycninet CNI_IFNAME=eth0 CNI_PATH=/usr/libexec/cni/ /usr/libexec/cni/bridge < bridge.conf 
{
    "cniVersion": "0.4.0",
    "interfaces": [
        {
            "name": "cni0",
            "mac": "2a:fe:85:73:a1:9c"
        },
        {
            "name": "vethff4df6f3",
            "mac": "4e:1c:fb:85:74:3b"
        },
        {
            "name": "eth0",
            "mac": "4a:a4:a8:bd:a5:a0",
            "sandbox": "/var/run/netns/mycninet"
        }
    ],
    "ips": [
        {
            "version": "4",
            "interface": 2,
            "address": "10.1.0.3/16",
            "gateway": "10.1.0.1"
        }
    ],
    "dns": {
        "nameservers": [
            "10.1.0.1"
        ]
    }
}[root@kvm-06-guest17 ~]#ip netns exec mycninet ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.1.0.3  netmask 255.255.0.0  broadcast 10.1.255.255
        inet6 fe80::48a4:a8ff:febd:a5a0  prefixlen 64  scopeid 0x20<link>
        ether 4a:a4:a8:bd:a5:a0  txqueuelen 0  (Ethernet)
        RX packets 7  bytes 586 (586.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 628 (628.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=8<LOOPBACK>  mtu 65536
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Comment 6 errata-xmlrpc 2019-11-05 21:02:57 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, 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-2019:3403