-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.14
-
Quality / Stability / Reliability
-
False
-
-
8
-
Moderate
-
No
-
None
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
IHAC who wants to add below points to the documentation of EngressIP and/or in SDN to OVN migration document. a) EgressIP is not present in node's interface in OVN and present in SDN. b) EgressIP cannot be pinged and need ARP to check connectivity. c) arping won't be responding in case there is no Pod active behind the EgressIP.
Version-Release number of selected component (if applicable):
4.x
How reproducible:
Document needs improvement so that customer can understand how EgressIP in OVN is reachable and if it's present on interface.
Steps to Reproduce:
1. Document correction is needed for EgressIP.
Actual results:
EgressIP documentation is not very clear.
Expected results:
Documentation must be clear enough and hold below points in it: a) EgressIP is not present in node's interface in OVN and present in SDN. b) EgressIP cannot be pinged and need ARP to check connectivity. c) arping won't be responding in case there is no Pod active behind the EgressIP.
Additional info:
NA