HA Proxy LBaaS configuration is not pushed properly

[musharani]

This is all in one node setup brought up with the build master-centos7-ocata-bld-13 using micro services.
On that testing LBaaS using WebUI. For that, installed haproxy inside the vrouter_agent docker. Hitting the below issues after installing haproxy.

Seems haproxy lbaas configuration is not pushing properly. Getting below error message and nothing is there in haproxy.conf file.

[root@nodec41 haproxy]# cat /var/log/contrail/contrail-lbaas-haproxy-stdout.log
03/06/2018 12:38:31 MSG Starting haproxy for Loadbalancer-ID 1dd41fac-6daf-4759-a977-427cf288b6c8
03/06/2018 12:38:31 MSG RTNETLINK answers: Invalid argument

03/07/2018 07:36:48 MSG Stopping haproxy for Loadbalancer-ID 1dd41fac-6daf-4759-a977-427cf288b6c8
03/07/2018 07:38:12 MSG Starting haproxy for Loadbalancer-ID b98af04b-53e8-4760-88c7-5bf710d23aa4
03/07/2018 07:38:12 MSG [ALERT] 065/073812 (472) : parsing [/var/lib/contrail/loadbalancer/haproxy/b98af04b-53e8-4760-88c7-5bf710d23aa4/haproxy.conf:25] : unknown option 'forwardfo'.
[ALERT] 065/073812 (472) : Error(s) found in configuration file : /var/lib/contrail/loadbalancer/haproxy/b98af04b-53e8-4760-88c7-5bf710d23aa4/haproxy.conf
[ALERT] 065/073812 (472) : Fatal errors found in configuration.

After restarting the vrouter_agent docker ip netns list throwing invalid argument output and not able to login into the ip netns namespace.

[root@nodec41 haproxy]# ip netns list
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
vrouter-33a5e244-57ec-403b-b337-aab39f861d81:b98af04b-53e8-4760-88c7-5bf710d23aa4

[root@nodec41 haproxy]# ip netns exec vrouter-33a5e244-57ec-403b-b337-aab39f861d81:b98af04b-53e8-4760-88c7-5bf710d23aa4 bash
RTNETLINK answers: Invalid argument
setting the network namespace "vrouter-33a5e244-57ec-403b-b337-aab39f861d81:b98af04b-53e8-4760-88c7-5bf710d23aa4" failed: Invalid argument

Got below error message from vrouter-agent introspect.

http://nodec41.englab.juniper.net:8085/Snh_ServiceInstanceReq?uuid=
Traceback (most recent call last):
  File "/usr/bin/opencontrail-vrouter-netns", line 9, in <module>
    load_entry_point('opencontrail-vrouter-netns==0.1', 'console_scripts', 'opencontrail-vrouter-netns')()
  File "/usr/lib/python2.7/site-packages/opencontrail_vrouter_netns/vrouter_netns.py", line 493, in main
    vrouter_netns.args.func()
  File "/usr/lib/python2.7/site-packages/opencontrail_vrouter_netns/vrouter_netns.py", line 440, in create
    netns_mgr.destroy()
  File "/usr/lib/python2.7/site-packages/opencontrail_vrouter_netns/vrouter_netns.py", line 196, in destroy
    for device in self.ip_ns.get_devices(exclude_loopback=True):
  File "/usr/lib/python2.7/site-packages/opencontrail_vrouter_netns/linux/ip_lib.py", line 95, in get_devices
    self.root_helper, self.namespace)
  File "/usr/lib/python2.7/site-packages/opencontrail_vrouter_netns/linux/ip_lib.py", line 80, in _execute
    root_helper=root_helper)
  File "/usr/lib/python2.7/site-packages/opencontrail_vrouter_netns/linux/utils.py", line 86, in execute
    raise RuntimeError(m)
RuntimeError:
Command: ['sudo', 'ip', 'netns', 'exec', 'vrouter-33a5e244-57ec-403b-b337-aab39f861d81:b98af04b-53e8-4760-88c7-5bf710d23aa4', 'ip', '-o', '-d', 'link', 'list']
Exit code: 1
Stdout: ''
Stderr: 'RTNETLINK answers: Invalid argument\nsetting the network namespace "vrouter-33a5e244-57ec-403b-b337-aab39f861d81:b98af04b-53e8-4760-88c7-5bf710d23aa4" failed: Invalid argument\n'

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/40622
Submitter: Yuvaraja Mariappan

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/40622
Committed: http://github.com/Juniper/contrail-controller/commit/7bb525201923bffe82091e8f414eeef60f27bd7a
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 7bb525201923bffe82091e8f414eeef60f27bd7a
Author: Yuvaraja Mariappan <email address hidden>
Date: Tue Mar 13 22:46:02 2018 -0700

HA Proxy LBaaS configuration is not pushed properly

contrail-gui wont pass all the fields for the loadbalancer.
some places it is not handled well in the svc-monitor which
caused the issue.

Change-Id: I33c8936c4403a30cc0c4b5bb45e586a8bc0e2044
Closes-bug: #1754565