1 files changed, 52 insertions, 173 deletions

diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index 961a281..ce9e9e0 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -4,100 +4,94 @@
 <chapter id="bugs-limitations">
   <title>Known Issues and Limitations in this Release</title>
 
-  <para>This chapter lists the known issues that affect the current
-  release.</para>
+  <para>This chapter lists the known general issues and limitations that
+  affect the current release.</para>
 
   <para><remark>The section further down is generated from JIRA with
   gen_known_issues.py, but that script is HARDCODED with affectedversion
   "EL7_3-virtualization" and needs to be adapted when a release info for
-  another ENFV Access version changes.</remark><emphasis
-  role="bold">Product-specific Issues and Limitations</emphasis></para>
+  another ENFV Access version changes.</remark></para>
 
   <itemizedlist>
-    <para><emphasis role="bold">Enea uCPE Manager</emphasis></para>
-
     <listitem>
-      <para><remark>ELCCR-99</remark>The uCPE Manager fails to onboard renamed
-      VNF bundles downloaded to the same repo.</para>
+      <para><remark>ELCCR-119</remark>Multiple uCPE devices behind a firewall
+      or a gateway connecting with Call-Home are not supported.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-119</remark>No support is provided for multiple uCPE
-      devices behind a firewall or gateway connecting Call Home to the uCPE
-      Manager (running outside the local network).</para>
+      <para><remark>ELCCR-319</remark>After a successful installation or
+      upgrade, it takes about 2 minutes until the device is accessible from
+      the uCPE Manager.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-319</remark>After a successful installation or
-      upgrade, it takes about 2 minutes until the device is accessible from
-      the browser.</para>
+      <para><remark>ELCCR-349</remark>If the uCPE Manager has not been
+      successfully installed originally or if the installed resources (files,
+      users, services, databases, environment variables, etc.) have been
+      manually changed/removed, the uninstallation may fail and some resources will
+      have to be removed manually.</para>
+    </listitem>
+    
+    <listitem>
+      <para><remark>ELCCR-349</remark>Recovery in case of a failed uCPE Manager
+      uninstallation is not implemented. In case of a failure the resources have to
+        be removed manually.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-349</remark>After uninstalling the uCPE manager
-      using the <filename>uninstall.sh</filename> script, the
-      <literal>ec_postgres</literal> service remains in an abnormal state. If
-      a product has not been successfully installed originally or if the
-      installed resources (files, users, services, databases, environment
-      variables, etc.) have been manually changed/removed, the uninstall may
-      fail and some resources will not be removed from the machine. Reverting
-      resources in the case of a failed uninstall is not implemented.</para>
+      <para><remark>ELCCR-454</remark>Only the default database is supported,
+      any requests for alternative databases are custom adaptations not tested
+      by Enea.</para>
     </listitem>
-        
-        <listitem><remark>ELCCR-454</remark>Only the default database is supported, any requests for alternative databases are custom adaptations.</listitem>
 
     <listitem>
-      <para><remark>ELCCR-371</remark>A software image for NFV Access runs
-      only upon the hardware platform it is built for. Currently, NFV Access
-      supports two separate platforms: Intel atom-c and Intel xeon-d. The user
-      uploading a software image to the uCPE Manager can specify which
-      platform the image belongs to. When upgrading devices that have older
-      versions of NFV Access (2.2.1 and earlier), the device does not provide
-      information about its platform. In such cases, it is not possible to
-      validate if it is acceptable to use a given software image for an
-      upgrade. In more recent versions of NFV Access (2.2.2 onwards), the
-      device supplies its platform and while upgrading a device, the system
-      will validate that the software image being upgraded to is of the same
-      platform type as the device.</para>
+      <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-474</remark>In case one VNF has configured flows in 
-        one of the OVS bridges it is connected to, the VNF instance cannot be 
-        deleted before removing the appropriate flows.</para>
+      <para><remark>ELCCR-527</remark>Cancelling a file upload in the uCPE
+      Manager will require the user to close and reopen the upload window for
+      the next upload to work.</para>
     </listitem>
-        
-        <listitem><remark>ELCCR-527</remark>When uploading a file, if the user cancels the upload, the upload window must be closed and reopened in order for the next upload to work.</listitem>
 
     <listitem>
-      <para><remark>LXCR-9088</remark>Automation Framework and Test Harness
-      tests require python version 2.7.X. Please make sure it is installed
-      before using the framework.</para>
+      <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>LXCR-????</remark>The Call Home functionality does not
       support having multiple interfaces/routes that go from the device to the
-      uCPE Manager. The IP/DNS address might need to be changed to the
-      established socket IP.</para>
+      uCPE Manager.</para>
     </listitem>
 
     <listitem>
-      <para><remark>LXCR-9799</remark>In case two HDDs installed with NFV
-      Access are attached to the same device, it is possible that NFV Access
-      will boot from the wrong partition. Please avoid having two NFV Access
-      images installed on two HDDs on the same device.</para>
+      <para><remark>LXCR-9799</remark>NFV Access can boot from the wrong
+      partition if two HDDs are attached to the same device, this must be
+      avoided.</para>
     </listitem>
-  </itemizedlist>
 
-  <para><remark>The section further down is generated from JIRA with
-  gen_known_issues.py, but that script is HARDCODED with affectedversion
-  "EL7_3-virtualization" and needs to be adapted when a release info for
-  another ENFV Access version changes.</remark></para>
+    <listitem>
+      <para><remark>LXCR-9853</remark>The WAN interface of 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>LXCR-9853</remark>When configuring a VNF with WAN and
+      Management access on different interfaces, the user has to ensure VNF's
+      virtual interfaces are configured so that proper routes are used for
+      traffic egress-ing the VNF.</para>
+    </listitem>
 
-  <para><emphasis role="bold">General Issues and Limitations</emphasis></para>
+    <listitem>
+      <para><remark>LXCR-9904</remark>NFV Access cannot be installed on USB
+      storage devices.</para>
+    </listitem>
 
-  <itemizedlist>
     <listitem condition="hidden">
       <para><emphasis role="bold">PDF navigation</emphasis>: When using links
       to open other PDFs, or jump to another place in the same PDF, jumping
@@ -106,121 +100,6 @@
       configured to open PDF files in an external PDF reader. As a workaround,
       open the HTML version of the document.<remark>LXCR-3283</remark></para>
     </listitem>
-
-    <listitem>
-      <para><remark>LXCR-9773</remark>REST API changes for specified modules
-      that might cause backward compatibility issues, are listed below:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>CustomScripts:</para>
-
-          <para>The <literal>uploadCustomScript()</literal> method takes in an
-          additional argument (device module name). This should not affect
-          current REST clients, since CustomScript functionality is available
-          only for NFV Access 2.2.2.</para>
-        </listitem>
-
-        <listitem>
-          <para>Device Upgrade:</para>
-
-          <para>A new method <literal>-- upload() --</literal> has been added
-          to allow uploads of NFV Access software images to the uCPE Manager.
-          This should not affect current REST clients, since it is a new
-          method.</para>
-        </listitem>
-
-        <listitem>
-          <para>VnfManager:</para>
-
-          <para>A new method <literal>-- upload() --</literal> has been added
-          to allow uploads of VNF images to the uCPE Manager as part of the
-          onboarding process. This should not affect current REST clients,
-          since it is a new method.</para>
-        </listitem>
-
-        <listitem>
-          <para>VcpeAgent (i.e. NFV Access device module):<itemizedlist>
-              <listitem>
-                <para>The system-attributes config table was split into
-                system-attributes-state (operational data) and
-                system-attributes (configuration data).<itemizedlist>
-                    <listitem>
-                      <para>The configuration data still contains the
-                      attributes: device-name, device-description and
-                      initial-configuration-complete.</para>
-                    </listitem>
-
-                    <listitem>
-                      <para>The fields device-type, device-version, device-id,
-                      device-latitude, and device-longitude are now
-                      operational data. device-ip-address has been added as
-                      oper data.</para>
-                    </listitem>
-
-                    <listitem>
-                      <para>customer-tag in release version 2.2.1 was a config
-                      leaf-list, it is now a leaf called device-customer-tags
-                      (comma-separated).</para>
-                    </listitem>
-
-                    <listitem>
-                      <para>mgmt-ip-address has been added as oper data. This
-                      attribute was configured within an ovs-bridge of type
-                      inband-mgmt.</para>
-                    </listitem>
-                  </itemizedlist></para>
-              </listitem>
-
-              <listitem>
-                <para>The external-interface-capabilities operational table
-                now has "wan" and "mgmt" Booleans.</para>
-              </listitem>
-
-              <listitem>
-                <para>The external-interface configuration table now has a
-                choice of "wan".</para>
-
-                <para>New fields for this type are mgmt-interface,
-                address-assignment , ip-address, gateway, netmask (only
-                considered if static).</para>
-              </listitem>
-
-              <listitem>
-                <para>In ovs-bridge, for the choice of inband-mgmt, the
-                mgmt-address and mgmt-port fields have been removed (there are
-                no fields left in this choice).</para>
-              </listitem>
-
-              <listitem>
-                <para>In the Host operational table, there are a couple of
-                changes:<itemizedlist>
-                    <listitem>
-                      <para>The "name" field has been removed, there is still
-                      a "host-name" field.</para>
-                    </listitem>
-
-                    <listitem>
-                      <para>A "machine-type" field has been added.</para>
-                    </listitem>
-                  </itemizedlist></para>
-              </listitem>
-            </itemizedlist></para>
-        </listitem>
-      </itemizedlist>
-    </listitem>
-
-    <listitem>
-      <para>REST clients should see some minor changes depending upon whether
-      they are dealing with version 2.2.1 or 2.2.2 of the device. Code that
-      deals with the system-attributes table, in-band management OVS bridges,
-      or the host operational data might need to be modified.</para>
-
-      <para>The new wan interface type only matters in that you need a
-      wan-mgmt interface configured to create the in-band mgmt. bridge. This
-      should typically happen automatically as part of initial install or
-      upgrade and should not affect the REST clients</para>
-    </listitem>
   </itemizedlist>
 
   <!-- The file with a section below is autocreated by make init  -->