[Mainline-Build 2704]: UI- changing protocol based flow aging timeout to 0 deletes the entry from agent

Bug #1539451 reported by alok kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.0
Won't Fix
Medium
jayaramsatya
R3.1
Won't Fix
Medium
jayaramsatya
Trunk
New
Medium
jayaramsatya

Bug Description

steps-
1. configure flow aging as below, it gets saved as expected and same is reflected is agent introspect.
Protocol: TCP, Port: 10000, Timeout: 10 seconds
2. now change the above entry timeout value to 0 and save. UI shows the configuration with timeout 0, but from agent actually it gets deleted.

similar issue is observed while adding new entry with timeout 0, it gets saved in UI but could not see this entry in agent.

Tags: vrouter
alok kumar (kalok)
tags: added: blocker
tags: removed: blocker
Revision history for this message
Biswajit Mandal (bmandal) wrote :

UI sends correct data and it is reflected in API Server also,

I set 0 from UI and I see the value is set properly,
{"flow_aging_timeout": [{"timeout_in_seconds": 0, "protocol": "tcp", "port": 678}]},

And whole dump for global-vrouter-config

root@nodeg16:~# curl -u admin:contrail123 localhost:8095/global-vrouter-config/3bc29af9-b0b2-4c75-b429-5d40ee6ce86f
{"global-vrouter-config": {"ecmp_hashing_include_fields": {"destination_ip": true, "ip_protocol": true, "source_ip": true, "source_mac": true, "source_port": true, "destination_port": true, "destination_mac": true}, "flow_aging_timeout_list": {"flow_aging_timeout": [{"timeout_in_seconds": 0, "protocol": "tcp", "port": 678}]}, "parent_uuid": "fdd701f2-bdca-4556-9a48-04e1fabf41e3", "display_name": "default-global-vrouter-config", "parent_href": "http://localhost:8095/global-system-config/fdd701f2-bdca-4556-9a48-04e1fabf41e3", "parent_type": "global-system-config", "href": "http://localhost:8095/global-vrouter-config/3bc29af9-b0b2-4c75-b429-5d40ee6ce86f", "id_perms": {"enable": true, "description": null, "created": "2016-01-31T05:23:08.496448", "creator": null, "uuid": {"uuid_mslong": 4306174590921624693, "uuid_lslong": 12982009934331570287}, "user_visible": true, "last_modified": "2016-01-31T07:36:11.543202", "permissions": {"owner": "admin", "owner_access": 7, "other_access": 7, "group": "KeystoneServiceAdmin", "group_access": 7}}, "vxlan_network_identifier_mode": "automatic", "name": "default-global-vrouter-config", "forwarding_mode": null, "fq_name": ["default-global-system-config", "default-global-vrouter-config"], "uuid": "3bc29af9-b0b2-4c75-b429-5d40ee6ce86f", "linklocal_services": {"linklocal_service_entry": [{"linklocal_service_name": "metadata", "ip_fabric_service_ip": ["10.204.217.56"], "linklocal_service_ip": "169.254.169.254", "ip_fabric_service_port": 8775, "ip_fabric_DNS_service_name": "", "linklocal_service_port": 80}]}, "encapsulation_priorities": {"encapsulation": ["MPLSoUDP", "MPLSoGRE", "VXLAN"]}, "perms2": {"owner": "0b9b1a255b9942f2af4bc231cea5370d", "owner_access": 7, "global_access": 0, "share": []}}}

alok kumar (kalok)
tags: added: config vrouter
Revision history for this message
alok kumar (kalok) wrote :

I see below config in agent introspect in ifmap_agent.xml but it's not configured:

flow-aging-timeout protocol:udp port:2222 timeout-in-seconds:0

complete global vrouter config from ifmap in agent introspect:
type:global-vrouter-config name:default-global-system-config:default-global-vrouter-config ecmp-hashing-include-fields source-mac:true destination-mac:true source-ip:true destination-ip:true ip-protocol:true source-port:true destination-port:true linklocal-services linklocal-service-entry linklocal-service-name:metadata linklocal-service-ip:169.254.169.254 linklocal-service-port:80 ip-fabric-service-port:8775 ip-fabric-service-ip:10.204.217.58 encapsulation-priorities encapsulation:MPLSoUDP encapsulation:MPLSoGRE encapsulation:VXLAN vxlan-network-identifier-mode:automatic flow-aging-timeout-list flow-aging-timeout protocol:tcp port:22 timeout-in-seconds:22 flow-aging-timeout protocol:udp port:2222 timeout-in-seconds:0 flow-aging-timeout protocol:1 port:0 timeout-in-seconds:2323 id-perms permissions owner:admin owner-access:7 group:admin group-access:7 other-access:7 uuid uuid-mslong:2888048809012183822 uuid-lslong:10343136958886191463 Uuid : 28146917-1b29-430e-8f8a-344389a02167 enable:true created:2016-01-25T15:33:25 last-modified:2016-01-31T07:37:45 user-visible:true perms2 owner:119412f18bc7426f9be236ae59dcee78 owner-access:7 global-access:0 display-name:default-global-vrouter-config Adjacencies: global-system-config default-global-system-config

adding vrouter tag to have a look.

tags: removed: config
Revision history for this message
Hari Prasad Killi (haripk) wrote :

Value 0 is invalid for timeout and hence agent ignores the configuration. A syslog message can be generated to indicate the same.

Reducing the severity as this is invalid configuration and nothing untoward is happening.

alok kumar (kalok)
information type: Proprietary → Public
Rahul (rahuls)
tags: removed: ui
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Bug update]

bug update...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.