Adding documentation content for mixed arch pod deployment in ENC

Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>

1 files changed, 24 insertions, 0 deletions

diff --git a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
index 55e9be7..bc682ab 100644
--- a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
+++ b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
@@ -411,6 +411,30 @@
           </listitem>
         </itemizedlist>
       </listitem>
+
+      <listitem>
+        <para>On Mixed Arch Deployment, only the aarch64 TestVM Cirros image
+        will be installed by Fuel</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>Due to the fact that Fuel will only deploy the aarch64
+            image, Yardstick, Functest, and certain Health Check tests will
+            not work. These test suites are dependent on a single image name
+            at a time, and do not know on how to place instances on the
+            Compute for images that each require a different arch.</para>
+
+            <para>To have both testVM images, the user must add the x86_64
+            image manually.</para>
+          </listitem>
+
+          <listitem>
+            <para>There is no workaround for the test suites failures.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
     </orderedlist>
   </section>