From 076a44268fcc9e235fef448d7e3c11bf09d6f7b6 Mon Sep 17 00:00:00 2001 From: Kobi Samoray Date: Tue, 13 Apr 2021 14:52:31 +0300 Subject: [PATCH] NSXV: LB-on-router bug release note Add a RN to describe an issue with LB on router case. Change-Id: I3e225afa1f3d32c691d7ac654cd9fc4a2349c295 --- ...b-on-router-multirouter-85b6ae24913cb0c5.yaml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 releasenotes/notes/issue-lb-on-router-multirouter-85b6ae24913cb0c5.yaml diff --git a/releasenotes/notes/issue-lb-on-router-multirouter-85b6ae24913cb0c5.yaml b/releasenotes/notes/issue-lb-on-router-multirouter-85b6ae24913cb0c5.yaml new file mode 100644 index 0000000000..7e917570cf --- /dev/null +++ b/releasenotes/notes/issue-lb-on-router-multirouter-85b6ae24913cb0c5.yaml @@ -0,0 +1,16 @@ +--- +prelude: > + With NSXV plugin, deleting a router interface of a tenant subnet, which has + multiple routers attached, with use_routers_as_lbaas_platform enabled, in + the configuration may result with an error. +issues: + - | + The configuration flag use_routers_as_lbaas_platform enables reuse NSXV + edge appliances which are allocated to routers, for load balancing. + When this flag is enabled, and a loadbalancer is created on a tenant + network which has multiple attached routers, an error may occur while + deleting a router interface on the subnet. This could happen even though + the loadbalancer is hosted on a different router than the one which is used + by the loadbalancer. + To work around this, the loadbalancer should be removed prior to the + deletion of the router interface.