[R4.1-97]- IPv6 server session is having ipv4 ingress sg rule in place of ipv6 rule

Bug #1754582 reported by alok kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.1
New
Medium
sangarshan p
R5.0
New
Medium
sangarshan p
Trunk
New
Medium
sangarshan p

Bug Description

IPv6 server session logged in the agent log is having sg rule(sg_rule_uuid field in log) of ipv4 in place of ipv6.

server session as in log file:

SessionEndpointObject: session_data= [ [ [ vmi = default-domain:ctest-SecurityLoggingIpv6-54949336:4ade53b2-daef-4982-9c4c-ba77832f3bcd vn = default-domain:ctest-SecurityLoggingIpv6-54949336:ctest-vn-26728159 security_policy_rule = 00000000-0000-0000-0000-000000000001 remote_vn = default-domain:ctest-SecurityLoggingIpv6-54949336:ctest-vn-14266995 is_client_session = 0 is_si = 0 vrouter_ip = 10.204.217.102 sess_agg_info= [ [ [ local_ip = 3a2b:f391:71f7:5850::3 service_port = 129 protocol = 58 ] [ logged_forward_bytes = 104 logged_forward_pkts = 1 logged_reverse_bytes = 118 logged_reverse_pkts = 1 sessionMap= [ [ [ ip = 2a5e:25cf:3f02:6669::3 port = 1274 ] [ forward_flow_info= [ logged_bytes = 104 logged_pkts = 1 flow_uuid = ed014221-1bee-4ab3-b680-06d0ca95b962 tcp_flags = 0 setup_time = 1520582089795908 action = pass sg_rule_uuid = eaa66225-84d8-44b8-aec9-8d94f421acd9 nw_ace_uuid = 465290fe-18f9-4186-85c8-2e767440036d underlay_source_port = 54258 ] reverse_flow_info= [ logged_bytes = 118 logged_pkts = 1 flow_uuid = 657356a6-d077-4472-a38e-e333f905d0fa tcp_flags = 0 setup_time = 1520582089795908 action = pass sg_rule_uuid = eaa66225-84d8-44b8-aec9-8d94f421acd9 nw_ace_uuid = 465290fe-18f9-4186-85c8-2e767440036d underlay_source_port = 55870 ] vm = d318f7d9-0fa4-4748-a2f0-7114fe397881 other_vrouter_ip = 10.204.216.69 underlay_proto = 2 ], ] ] ], ] ] ], ] ]

here sg rule uuid is eaa66225-84d8-44b8-aec9-8d94f421acd9 which is actually ipv4 ingress rule.

Tags: vrouter
Revision history for this message
Sudheendra Rao (sudheendra-k) wrote :

moving it out to R5.0.2

Revision history for this message
Sivakumar Ganapathy (hotlava51) wrote :

Less critical bug, moving it out of 5.0.2 after agreement with Sudheendra.

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.