Default gw is not pinging, when service instance is attached to VN (name with a space)
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.22.x |
Won't Fix
|
Medium
|
Ranjeet R | |||
R3.0 |
Won't Fix
|
Medium
|
Ranjeet R | |||
R3.1 |
Won't Fix
|
Medium
|
Ranjeet R | |||
Trunk |
Fix Committed
|
Medium
|
Tapan Karwa |
Bug Description
Initially this bug was raised as a UI bug to block creating a VN name with a space in the end. Later its concluded that, name with a space in the end is valid, rather default gw ping issue shall be fixed
Create two VN with a name (name and space in the end) . Say "VnLeft " and "VnRight "
Attach a common policy "POL" on both VN
Launch VM1 on VnLeft and VM2 on VnRight. Ping from VM1 to VM2 is successful.
Create a service chain and associate SI to the same policy POL.
From SI default gw to VnLeft and VnRight is not pinging.
Same test with VN name without space in the end works fine.
Balaji,
Pls re-assign this bug to a Dev who can take a look at this issue.
Old description Start
Networking-
On creating a network name ending with space and attaching to policy which is used by service instance, the network gateway will not ping because routing instance name with space is not considered for routing.
Old description end
tags: | added: ui |
tags: |
added: soln removed: sol |
information type: | Proprietary → Public |
description: | updated |
summary: |
- UI : creating a network name ending with space shall not be allowed + Default gw is not pinging, when service instance is attached to VN + (name with a space) |
Should be ideally fixed in api server or schema.