Updated doc to account for limtations in COSNOSCR-540

Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>

1 files changed, 21 insertions, 11 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 c5fbfbb..9494eae 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
@@ -9,7 +9,7 @@
   upstream, and remaining issues are listed below.<remark>INFO: The <emphasis
   role="bold">Release-Specific Problems</emphasis> section further down is
   generated from JIRA with gen_known_issues.py, but that script is HARDCODED
-  with affectedversion "Enea NFV 1.0" and needs to be adapted when a release
+  with affectedversion "Enea NFV 1.0.1" and needs to be adapted when a release
   info for another ENFV version changes.</remark></para>
 
   <section id="bugs-limitations-gen">
@@ -17,26 +17,35 @@
 
     <orderedlist>
       <listitem>
-        <para>Live migration fails on ThunderX NUMA nodes</para>
+        <para>Live migration fails on ThunderX nodes with different CPU
+        Revision</para>
 
         <itemizedlist>
           <listitem>
             <para>Description and Impact:</para>
 
-            <para>Rally Nova tests are failing for the
-            <filename>nosdn-vlan_doctor_dpdk-ha</filename> scenario on
-            ThunderX NUMA nodes. The issue is not reproducible on the x86
-            architecture nor on aarch64 (for non dpdk scenarios).</para>
+            <para>For aarch64 architecture qemu describes a CPU in terms of
+            Vendor, Model and Revision number in contrast with x86
+            architecture where CPU supported features (e. g. instruction set
+            supported) are used.</para>
+
+            <para>Due to lack of support in qemu for describing a cpu in terms
+            of features for aarch64 architecture (e. g. instruction set
+            supported) there will be impossible to migrate VMs between hosts
+            with different revision CPUs.</para>
           </listitem>
 
           <listitem>
-            <para>Workaround: N/A.</para>
+            <para>Workaround:</para>
+
+            <para>In the deployment pod use compute nodes with the same
+            Vendor, Model, and Revision number CPUs.</para>
           </listitem>
         </itemizedlist>
       </listitem>
 
       <listitem>
-        <para> Instances fail to boot when using a direct port (SR-IOV) on
+        <para>Instances fail to boot when using a direct port (SR-IOV) on
         ThunderX</para>
 
         <itemizedlist>
@@ -268,7 +277,7 @@
             <para>Workaround:</para>
 
             <para>Starting the <literal>systemd</literal> service manually
-            makes it run successfully. Enea NFV Core 1.0 will be shipped
+            makes it run successfully. Enea NFV Core 1.0.1 will be shipped
             without Openstack Resource Agents, therefore this issue should not
             affect the user.</para>
           </listitem>
@@ -328,8 +337,9 @@
           <listitem>
             <para>Workaround:</para>
 
-            <para>Enea NFV Core 1.0 will be shipped without Openstack Resource
-            Agents, therefore this issue should not affect the user.</para>
+            <para>Enea NFV Core 1.0.1 will be shipped without Openstack
+            Resource Agents, therefore this issue should not affect the
+            user.</para>
           </listitem>
         </itemizedlist>
       </listitem>