1 files changed, 127 insertions, 88 deletions

diff --git a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
index 81816a5..13a8c23 100644
--- a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
@@ -4,38 +4,59 @@
 <chapter id="bugs-limitations">
   <title>Known Issues and Limitations in this Release</title>
 
-  <para>This chapter lists the known general issues and limitations that
-  affect the current release.</para>
+  <note>
+    <para>All issues may also affect previous releases.</para>
+  </note>
 
   <itemizedlist>
     <listitem>
-      <para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
-      USB storage devices.</para>
+      <para><remark>ELCCR-1688, ELCCR-1809</remark>It is possible to end up
+      with a corrupted VM image from the download operation. If that happens,
+      the VNF instantiation will fail. The corrupted image has to be manually
+      removed from <literal>/var/odm/vm_images/startup/</literal>.</para>
     </listitem>
 
     <listitem>
-      <para><remark>LXCR-9799</remark>Proper boot order is not ensured if a
-      uCPE device has more than one HDD attached.</para>
+      <para><remark>ELCCR-1733</remark>Logging into the Enea Edge Management
+      application over HTTP can fail, producing the error <literal>You have
+      been automatically logged out</literal>. If this happens, the user
+      should clear the <literal>JSESSIONID</literal> browser's cookie or close
+      and restart the browser.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-527</remark>Cancelling a file upload in the Enea
-      Edge Management will require the user to close and reopen the upload
-      window for the next upload to work.</para>
+      <para><remark>ELCCR-1753</remark>When using tap interfaces for
+      communicating over the bridge, port numbers assigned to VM interfaces
+      can change when the VMs are restarted. The only currently known
+      workaround is rebooting the uCPE device.</para>
     </listitem>
-
+    
     <listitem>
-      <para><remark>ELCCR-577</remark>If the Enea Edge Management application
-      is restored from a backup made on a release version older than Enea NFV
-      Access 2.2.3, VNFs cannot be instantiated from the GUI.</para>
+      <para><remark>ELCCR-1999</remark>Attempting to upload multiple files 
+        simultaneously (e.g. a VNF image and custom scripts) in the Enea Edge
+        Management application will cause all upload operations to be canceled. 
+        In order to avoid this limitation, please wait until any previous 
+        upload finishes before initiating a new one.</para>
     </listitem>
-    
+
     <listitem>
-      <para><remark>ELCCR-1134</remark>In order to avoid an incorrect boot 
-        order after a failed upgrade, the user should remove the upgrade 
-        image before attempting again.</para>
+      <para><remark>LXCR-10922</remark>A very rare error on some Atom C3000
+      boards makes X553 SFP+ Ethernet ports unusable until a target cold reset
+      is performed. When the error occurs in Enea Edge Runtime 2.5.0, there
+      will be a warning printed into the console by the
+      <literal>ixgbe</literal> driver:</para>
+
+      <programlisting>[11.361580] ixgbe 0000:0a:00.0: Warning firmware error detected FWSM: 0x8010801A</programlisting>
+
+      <para>The only currently known workaround for this issue is a cold
+      reset.</para>
     </listitem>
+  </itemizedlist>
 
+  <para><emphasis role="bold">Limitations detected in previous releases, 
+    that still affect this release:</emphasis></para>
+
+  <itemizedlist>
     <listitem>
       <para><remark>ELCCR-474</remark>Deleting VNF instances with flows
       configured on the OVS bridges can be done only after removing the
@@ -43,12 +64,24 @@
     </listitem>
 
     <listitem>
+      <para><remark>ELCCR-527</remark>Canceling a file upload in the Enea Edge
+      Management application will require the user to close and reopen the
+      upload window for the next upload to work.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>ELCCR-572</remark>Sometimes when selecting and deleting
       more than one VNF instance simultaneously, an error message might be
       triggered, even if the delete operation succeeds.</para>
     </listitem>
 
     <listitem>
+      <para><remark>ELCCR-577</remark>If the Enea Edge Management application
+      is restored from a backup made on a release version older than Enea NFV
+      Access 2.2.3, VNFs cannot be instantiated from the GUI.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>ELCCR-847</remark>The Juniper vSRX VNF cannot be
       instantiated on the Xeon-D architectures due to missing CPU features in
       the VNF's domain XML. This impacts all example use cases where the
@@ -56,10 +89,53 @@
     </listitem>
 
     <listitem>
-      <para><remark>USERDOCAP-648</remark>The <literal>storage size</literal>
-      parameter on the VNF onboarding page is ignored. The default storage
-      size specified when creating the VM image is used when instantiating the
-      VM and when presenting VM information.</para>
+      <para><remark>ELCCR-912</remark>When the Enea Edge Management
+      application is installed on CentOS 7, prior to C7.1804 (kernel version
+      3.10.0-862), adding an upgrade image fails. As a workaround, please
+      update <literal>glib2</literal> to version 2.54.2 or later, using
+      <literal>#yum update glib2</literal>.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1468</remark>When using the Enea Edge Management
+      application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is
+      not possible. Either switch to HTTP mode (for more details see <olink
+      targetdoc="book_enea_edge_getting_started"
+      targetptr="device_up_process">The uCPE device Upgrade Process in the
+      <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
+      xmlns:xi="http://www.w3.org/2001/XInclude"
+      xpointer="element(book_enea_edge_getting_started/1)" /></olink> Manual)
+      or install it manually.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1497</remark>If the Enea Edge Management application
+      has an incorrect database configuration, when performing an
+      uninstallation, the Tomcat instance and Watchdog service will not be
+      stopped automatically. Instead, they must be killed explicitly.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1565</remark>Before starting an Enea Edge Management
+      upgrade, any owned Tomcat certificates should be manually copied into
+      the
+      <literal>/opt/ems/ucpemanager/application/config/certificates</literal>
+      folder.</para>
+    </listitem>
+
+    <listitem condition="hidden">
+      <para><remark>LXCR-3283</remark><emphasis role="bold">PDF
+      navigation</emphasis>: When using links to open other PDFs, or jump to
+      another place in the same PDF, jumping back sometimes fails. This has
+      been observed when opening a PDF in Adobe Reader, inside a browser with
+      PDF add-on, as well as when the browser is configured to open PDF files
+      in an external PDF reader. As a workaround, open the HTML version of the
+      document.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>LXCR-9799</remark>Proper boot order is not ensured if a
+      uCPE device has more than one HDD attached.</para>
     </listitem>
 
     <listitem>
@@ -67,11 +143,10 @@
       to be connected to a network with at least a router/gateway installed
       for next-hop communication.</para>
     </listitem>
-    
+
     <listitem>
-      <para><remark>ELCCR-1504</remark>To change the type of an interface 
-        from DPDK to SR-IOV, first delete the existing interface, then 
-        recreate it with the desired type.</para>
+      <para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
+      USB storage devices.</para>
     </listitem>
 
     <listitem>
@@ -85,29 +160,9 @@
     </listitem>
 
     <listitem>
-      <para><remark>STCR-6224</remark>The Enea Edge Automation and the Enea
-      Edge Automation Framework and Test Harness do not support multiple
-      custom scripts uploaded to a uCPE device at the same time.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>STCR-6292</remark>Management of WAN Interfaces is not
-      implemented in the Enea Edge Automation Framework and Test
-      Harness.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>USERDOCAP-628</remark>Enea Edge Automation Framework and
-      Test Harness does not have support for product features implemented in
-      Enea Edge 2.4.0 or newer.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>ELCCR-912</remark>When the Enea Edge Management
-      application is installed on CentOS 7, prior to C7.1804 (kernel version
-      3.10.0-862), adding an upgrade image fails. As a workaround, please
-      update <literal>glib2</literal> to version 2.54.2 or later, using
-      <literal>#yum update glib2</literal>.</para>
+      <para><remark>LXCR-10750</remark>In order to avoid an incorrect boot
+      order after a failed upgrade, the user should remove the upgrade image
+      before attempting again.</para>
     </listitem>
 
     <listitem>
@@ -117,58 +172,42 @@
     </listitem>
 
     <listitem>
+      <para><remark>USERDOCAP-648</remark>The <literal>storage size</literal>
+      parameter on the VNF onboarding page is ignored. The default storage
+      size specified when creating the VM image is used when instantiating the
+      VM and when presenting VM information.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>USERDOCAP-651</remark>Wireless AP configuration is
       optimized for wireless modules that use the <literal>ath10k</literal>
       driver. Using other wireless modules may result in undefined
       behavior.</para>
     </listitem>
+  </itemizedlist>
 
-    <listitem>
-      <para><remark>ELCCR-1518</remark>The Wireless AP's wpa2psk password
-      should not contain white space characters.</para>
-    </listitem>
+  <para><emphasis role="bold">The following limitations affect deprecated
+  components and their documentation:</emphasis></para>
 
+  <itemizedlist>
     <listitem>
-      <para><remark>ELCCR-1561</remark>Before starting an Enea Edge Management
-      upgrade, any owned Tomcat certificates should be manually copied into the 
-        <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates</literal>
-      folder.</para>
+      <para><remark>STCR-6224</remark>The Enea Edge Automation Framework and
+      Test Harness do not support multiple custom scripts uploaded to a uCPE
+      device at the same time. This limitation does not apply to Enea Edge
+      Automation.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-1378</remark>Modifying the type of the external
-      interfaces can lead to errors. Instead of modifying, it is recommended
-      to delete the old interfaces and recreate them with the desired
-      type.</para>
-    </listitem>
-    
-    <listitem>
-      <para><remark>ELCCR-1497</remark>If the Enea Edge Management application 
-        has an incorrect database configuration, when performing an uninstallation, 
-        the Tomcat instance and Watchdog service will not be stopped automatically. 
-        Instead, they must be killed explicitly.</para>
-    </listitem>
-    
-    <listitem>
-      <para><remark>ELCCR-1468</remark>When using the Enea Edge Management
-      application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is
-      not possible. Either switch to HTTP mode (for more details see <olink
-      targetdoc="book_enea_edge_getting_started"
-      targetptr="device_up_process">The uCPE device Upgrade Process in the
-      <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
-      xmlns:xi="http://www.w3.org/2001/XInclude"
-      xpointer="element(book_enea_edge_getting_started/1)" /></olink> Manual)
-      or install it manually.</para>
+      <para><remark>STCR-6292</remark>Management of WAN Interfaces is not
+      implemented in the Enea Edge Automation Framework and Test
+      Harness. This limitation does not apply to the Enea Edge Automation.</para>
     </listitem>
 
-    <listitem condition="hidden">
-      <para><remark>LXCR-3283</remark><emphasis role="bold">PDF
-      navigation</emphasis>: When using links to open other PDFs, or jump to
-      another place in the same PDF, jumping back sometimes fails. This has
-      been observed when opening a PDF in Adobe Reader, inside a browser with
-      PDF add-on, as well as when the browser is configured to open PDF files
-      in an external PDF reader. As a workaround, open the HTML version of the
-      document.</para>
+    <listitem>
+      <para><remark>USERDOCAP-628</remark>The Enea Edge Automation Framework
+      and Test Harness do not have support for product features implemented in
+      Enea Edge 2.4.0 or newer. Please use the new Enea Edge Automation 
+        component if you want support for newer features.</para>
     </listitem>
   </itemizedlist>
 
@@ -176,4 +215,4 @@
 
   <!-- <xi:include href="jiraissues_generated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
-</chapter>
+</chapter>
\ No newline at end of file