From 2b4934d59544b307e8847cb77ff6948c8ba67f7d Mon Sep 17 00:00:00 2001 From: Nikolas Hermanns Date: Thu, 4 May 2017 16:02:28 +0200 Subject: Removing peering testcase for Apex Change-Id: Ifad3f84fcb0c5dfa07aca43d74a027e3522abb87 Signed-off-by: Nikolas Hermanns (cherry picked from commit c0080201984842b64b91ea3cb0fc96ca03fe303c) --- docs/release/release-notes/release-notes.rst | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/release/release-notes/release-notes.rst') diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst index 4fc01e3..f5e04cf 100644 --- a/docs/release/release-notes/release-notes.rst +++ b/docs/release/release-notes/release-notes.rst @@ -125,6 +125,7 @@ Documentation deliverables Known Limitations, Issues and Workarounds ========================================= + System Limitations ------------------ @@ -140,6 +141,9 @@ OpenStack NAT does not work. Instances created in subnets that are connected to the public network via a gateway should have external connectivity. This does not work and can be worked around by assigning a Floating IP to the instance [1]. +For Apex the peering with the virtual Peer is not working due to limitation +of apex networking. + Workarounds ----------- -- cgit 1.2.3-korg