in get_port_obj:
json_unpack will analyse dot as the symbol of different level nodes.
so This should be a jansson api issue, will check if there is a better api in jansson for this later.

update: actually jansson work fine. The true reason is in function __teamd_json_path_lite_va() the path looks like ".ports.eth1.2.queue_id" and we split it via ".", which make eth1.2 become two levels. I will check how to fix it.

upstream fix:
https://github.com/jpirko/libteam/commit/b30381795c691be9256c49616105d022a2884d1c

re-assigne back to Marcelo since we have the fix now.

Verified on- libteam-1.25-5.el7.x86_64

LOG-
[root@sam ~]# uname -r 
3.10.0-637.el7.x86_64
[root@sam ~]# rpm -q teamd libteam
teamd-1.25-5.el7.x86_64
libteam-1.25-5.el7.x86_64
[root@sam ~]# 
[root@sam ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp7s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq portid 0100000000000000000000333135384643 state UP qlen 1000
    link/ether 00:90:fa:8a:5b:fa brd ff:ff:ff:ff:ff:ff
3: enp7s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq portid 0200000000000000000000333135384643 state UP qlen 1000
    link/ether 00:90:fa:8a:5c:02 brd ff:ff:ff:ff:ff:ff
4: enp5s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether e4:11:5b:dd:e6:6c brd ff:ff:ff:ff:ff:ff
    inet 10.19.15.26/24 brd 10.19.15.255 scope global dynamic enp5s0f0
       valid_lft 85180sec preferred_lft 85180sec
    inet6 2620:52:0:130b:e611:5bff:fedd:e66c/64 scope global noprefixroute dynamic 
       valid_lft 2591778sec preferred_lft 604578sec
    inet6 fe80::e611:5bff:fedd:e66c/64 scope link 
       valid_lft forever preferred_lft forever
5: enp5s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether e4:11:5b:dd:e6:6d brd ff:ff:ff:ff:ff:ff
[root@sam ~]# ip link add link enp7s0f0 name enp7s0f0.3 type vlan id 3
[root@sam ~]# ip link add link enp7s0f1 name enp7s0f1.3 type vlan id 3
[root@sam ~]# 
[root@sam ~]# #team_json='{ "runner" : {  "name" : "activebackup" }, "link_watch" : {  "name" : "ethtool" } }'
[root@sam ~]# teamd -d -t team3 -c '{ "runner" : {  "name" : "activebackup" }, "link_watch" : {  "name" : "ethtool" } }'
This program is not intended to be run as root.
[root@sam ~]# teamdctl team3 port add enp7s0f0.3
[root@sam ~]# teamdctl team3 port add enp7s0f1.3
[root@sam ~]# 
[root@sam ~]# ip link set team3 up
[root@sam ~]# teamdctl team3 state view -v
setup:
  runner: activebackup
  kernel team mode: activebackup
  D-BUS enabled: no
  ZeroMQ enabled: no
  debug level: 0
  daemonized: yes
  PID: 2482
  PID file: /var/run/teamd/team3.pid
ports:
  enp7s0f0.3
    ifindex: 6
    addr: 00:90:fa:8a:5b:fa
    ethtool link: 0mbit/halfduplex/up
    link watches:
      link summary: up
      instance[link_watch_0]:
        name: ethtool
        link: up
        down count: 0
        link up delay: 0
        link down delay: 0
  enp7s0f1.3
    ifindex: 7
    addr: 00:90:fa:8a:5b:fa
    ethtool link: 0mbit/halfduplex/up
    link watches:
      link summary: up
      instance[link_watch_0]:
        name: ethtool
        link: up
        down count: 0
        link up delay: 0
        link down delay: 0
runner:
  active port: enp7s0f0.3
[root@sam ~]# teamdctl team3 state dump
{
    "ports": {
        "enp7s0f0.3": {
            "ifinfo": {
                "dev_addr": "00:90:fa:8a:5b:fa",
                "dev_addr_len": 6,
                "ifindex": 6,
                "ifname": "enp7s0f0.3"
            },
            "link": {
                "duplex": "half",
                "speed": 0,
                "up": true
            },
            "link_watches": {
                "list": {
                    "link_watch_0": {
                        "delay_down": 0,
                        "delay_up": 0,
                        "down_count": 0,
                        "name": "ethtool",
                        "up": true
                    }
                },
                "up": true
            }
        },
        "enp7s0f1.3": {
            "ifinfo": {
                "dev_addr": "00:90:fa:8a:5b:fa",
                "dev_addr_len": 6,
                "ifindex": 7,
                "ifname": "enp7s0f1.3"
            },
            "link": {
                "duplex": "half",
                "speed": 0,
                "up": true
            },
            "link_watches": {
                "list": {
                    "link_watch_0": {
                        "delay_down": 0,
                        "delay_up": 0,
                        "down_count": 0,
                        "name": "ethtool",
                        "up": true
                    }
                },
                "up": true
            }
        }
    },
    "runner": {
        "active_port": "enp7s0f0.3"
    },
    "setup": {
        "daemonized": true,
        "dbus_enabled": false,
        "debug_level": 0,
        "kernel_team_mode_name": "activebackup",
        "pid": 2482,
        "pid_file": "/var/run/teamd/team3.pid",
        "runner_name": "activebackup",
        "zmq_enabled": false
    },
    "team_device": {
        "ifinfo": {
            "dev_addr": "00:90:fa:8a:5b:fa",
            "dev_addr_len": 6,
            "ifindex": 8,
            "ifname": "team3"
        }
    }
}
[root@sam ~]#

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/RHBA-2017:2201