Merge the code from develop to master for 2.4.0Enea_NFV_Access_2.4.0hotfix_EDGESC-6feature_CPDX-3546EE240_HotFix1

Change-Id: Ibc844e001b7d75125d6006fa5333cc65bbf5afa4

1 files changed, 179 insertions, 0 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
new file mode 100644
index 0000000..81816a5
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
@@ -0,0 +1,179 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<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>
+
+  <itemizedlist>
+    <listitem>
+      <para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
+      USB storage devices.</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>
+      <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>
+    </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-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>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-474</remark>Deleting VNF instances with flows
+      configured on the OVS bridges can be done only after removing the
+      flows.</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-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
+      Juniper VNF is used.</para>
+    </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>LXCR-9853</remark>The WAN interface of a uCPE device needs
+      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>
+    </listitem>
+
+    <listitem>
+      <para><remark>LXCR-9992</remark>Depending on hardware capabilities,
+      there are certain limitations regarding the <literal>vfio-pci</literal>
+      and <literal>igb_uio</literal> drivers. While the Enea Edge Runtime uses
+      the <literal>vfio-pci</literal> driver by default, for certain hardware
+      configurations, <literal>igb_uio</literal> should be used instead, by
+      providing custom scripting. Please contact Enea for further
+      details.</para>
+    </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>
+    </listitem>
+
+    <listitem>
+      <para><remark>USERDOCAP-641</remark>Enea Edge does not have support for
+      IPv6 addresses on both uCPE devices and the Enea Edge Management
+      installation.</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>
+
+    <listitem>
+      <para><remark>ELCCR-1518</remark>The Wireless AP's wpa2psk password
+      should not contain white space characters.</para>
+    </listitem>
+
+    <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>
+    </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>
+    </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>
+  </itemizedlist>
+
+  <!-- The file with a section below is autocreated by make init  -->
+
+  <!-- <xi:include href="jiraissues_generated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+</chapter>