[R3.0-32]: disable policy behaviour with FIP

Bug #1582677 reported by alok kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Opinion
Undecided
Unassigned
R3.0
Opinion
Undecided
Unassigned

Bug Description

Listing out the behaviour found in testing, when policy is disable on the VMI where floating IP is associated. If needed, this can be mentioned in release note.

when Floating IP is associated to the VM and that VMI's policy is disabled, we can still send/receive traffic from FIP in below cases:

case 1.
steps:
1. connect VN2 and VN3 with any-any policy
2. associate FIP from VN1 to VM in VN2
3. send/recv traffic to/from FIP works in this case.

case 2.
steps:
1. create 2 VMs sender and receiver.
2. associate FIP to receiver VM and remove SG
3. able to receive traffic from FIP subnet to FIP.

Tags: vrouter
alok kumar (kalok)
Changed in juniperopenstack:
milestone: none → r3.0.2.0
Jeba Paulaiyan (jebap)
Changed in juniperopenstack:
milestone: r3.0.2.0 → none
information type: Proprietary → Public
Changed in juniperopenstack:
status: New → Opinion
Changed in juniperopenstack:
status: Opinion → Fix Committed
status: Fix Committed → Opinion
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.