Bug 1464305 - flannel in x390s can not get correct ip address as it is configured in etcd
flannel in x390s can not get correct ip address as it is configured in etcd
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: flannel (Show other bugs)
7.4
s390 Unspecified
high Severity high
: rc
: ---
Assigned To: Ben Bennett
atomic-bugs@redhat.com
: Extras
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-22 23:34 EDT by Joy Pu
Modified: 2017-08-08 12:07 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joy Pu 2017-06-22 23:34:19 EDT
Description of problem:

The ip address that flannel get in x390s system is not the same as we set it in etcd.


Version-Release number of selected component (if applicable):
[root@ibm-z-23 ~]# rpm -qa|grep flannel
flannel-0.7.1-2.el7.s390x


How reproducible:
100%


Steps to Reproduce:
1. set up a etcd server and set flannel config in it
2. start flanneld service
3. use systemctl status and ip addr to check the ip address it get 

Actual results:
the ip is different with the one we set


Expected results:
the ip should be the same as we set

Additional info:

I tried to change the atomic.io/network/config to several value: 10.20.0.0 , 10.30.0.0 or 172.10.0.0. But the flannel always get the same ip: 10.91.0.0. Also tried to get the config from another etcd server and it changed to 10.35.0.0 but still not fit the configuration which is 10.10.0.0.

flannel status info:

[root@ibm-z-23 ~]# systemctl status flanneld -l
● flanneld.service - Flanneld overlay address etcd agent
   Loaded: loaded (/usr/lib/systemd/system/flanneld.service; disabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-06-22 23:19:58 EDT; 5s ago
  Process: 64531 ExecStartPost=/usr/libexec/flannel/mk-docker-opts.sh -k DOCKER_NETWORK_OPTIONS -d /run/flannel/docker (code=exited, status=0/SUCCESS)
 Main PID: 64521 (flanneld)
   CGroup: /system.slice/flanneld.service
           └─64521 /usr/bin/flanneld -etcd-endpoints=http://127.0.0.1:2379 -etcd-prefix=/atomic.io/network

Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com systemd[1]: Starting Flanneld overlay address etcd agent...
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.241562   64521 main.go:132] Installing signal handlers
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.249998   64521 manager.go:136] Determining IP address of default interface
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.250228   64521 manager.go:149] Using interface with name enccw0.0.8000 and address 10.16.66.214
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.250239   64521 manager.go:166] Defaulting external address to interface address (10.16.66.214)
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.338381   64521 local_manager.go:134] Found lease (10.91.0.0/24) for current IP (10.16.66.214), reusing
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.346045   64521 manager.go:250] Lease acquired: 10.91.0.0/24
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.346327   64521 network.go:58] Watching for L3 misses
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com flanneld-start[64521]: I0622 23:19:58.346334   64521 network.go:66] Watching for new subnet leases
Jun 22 23:19:58 ibm-z-23.rhts.eng.bos.redhat.com systemd[1]: Started Flanneld overlay address etcd agent.


etcdctl output:
[root@ibm-z-23 ~]# etcdctl get atomic.io/network/config
{
  "Network": "172.10.0.0/16",
  "SubnetLen": 24,
  "Backend": {
    "Type": "vxlan",
    "VNI": 1
  }  
}

ip addr output:
[root@ibm-z-23 ~]# ip addr
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: enccw0.0.8000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 02:de:ad:be:ef:17 brd ff:ff:ff:ff:ff:ff
    inet 10.16.66.214/21 brd 10.16.71.255 scope global enccw0.0.8000
       valid_lft forever preferred_lft forever
    inet6 2001:db8:1:0:de:adff:febe:ef17/64 scope global noprefixroute dynamic 
       valid_lft 82085sec preferred_lft 10085sec
    inet6 2620:52:0:1040:de:adff:febe:ef17/64 scope global noprefixroute dynamic 
       valid_lft 2592000sec preferred_lft 604800sec
    inet6 fe80::de:adff:febe:ef17/64 scope link 
       valid_lft forever preferred_lft forever
5: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN 
    link/ether d2:df:4a:c6:ae:06 brd ff:ff:ff:ff:ff:ff
    inet 10.91.0.0/32 scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::d0df:4aff:fec6:ae06/64 scope link 
       valid_lft forever preferred_lft forever

Note You need to log in before you can comment on or make changes to this bug.