Updated the Known Issues Chapter, reordering issues

per component etc.

Change-Id: Idd94904936583cbdffa2ae6491a881453a77e7e1
Signed-off-by: mrpa <miruna.paun@enea.com>

1 files changed, 51 insertions, 56 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 ef184d8..a46289e 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
@@ -7,20 +7,10 @@
   <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></para>
-
   <itemizedlist>
     <listitem>
-      <para><remark>CPDX-3292</remark>The Factory Reset button in the uCPE
-      Manager is experimental as of the 2.2.2 release.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>ELCCR-119</remark>Multiple uCPE devices behind a firewall
-      or a gateway connecting with Call-Home are not supported.</para>
+      <para><remark>LXCR-9904</remark>NFV Access cannot be installed on USB
+      storage devices.</para>
     </listitem>
 
     <listitem>
@@ -30,29 +20,29 @@
     </listitem>
 
     <listitem>
+      <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>
+
+    <listitem>
       <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>
+      manually changed/removed, the uninstallation may fail and some resources
+      will have to be removed manually.</para>
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-454</remark>Only the default database is supported,
-      any requests for alternative databases are custom adaptations not tested
-      by Enea.</para>
+      <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-474</remark>Deleting VNF instances with flows
-      configured on the OVS bridges can be done only after removing the
-      flows.</para>
+      <para><remark>ELCCR-454</remark> For the uCPE Manager, only the default
+      database is supported, any requests for alternative databases are custom
+      adaptations not tested by Enea.</para>
     </listitem>
 
     <listitem>
@@ -62,6 +52,28 @@
     </listitem>
 
     <listitem>
+      <para><remark>ELCCR-577</remark>If a uCPEM is restored from a backup
+      made on an older release version than 2.2.3, VNFs cannot be instantiated
+      from the GUI.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>CPDX-3292</remark>The Factory Reset button in the uCPE
+      Manager is experimental as of the 2.2.2 release.</para>
+    </listitem>
+
+    <listitem>
+      <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-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>
@@ -74,17 +86,11 @@
     </listitem>
 
     <listitem>
-      <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>
-
-    <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
@@ -93,31 +99,20 @@
     </listitem>
 
     <listitem>
-      <para><remark>LXCR-9904</remark>NFV Access cannot be installed on USB
-      storage devices.</para>
-    </listitem>
-
-    <listitem>
-    <para><remark>ELCCR-577</remark>If a uCPEM is restored from a backup made 
-      on an older release version than 2.2.3, VNFs cannot be instantiated from the GUI.
-    </para>
-        </listitem>
-
-    <listitem>
       <para><remark>LXCR-9992</remark>Due to the way VFIO works, there are
-      certain limitations regarding which devices can be used with VFIO. Mainly, it
-      comes down to how IOMMU groups work. Any Virtual Function device can
-      be used with VFIO on its own, however, physical devices will require either
-      all ports to be bound to VFIO, or only some of them bound while others not
-      bound to anything at all.</para>
+      certain limitations regarding which devices can be used with VFIO.
+      Mainly, it comes down to how IOMMU groups work. Any Virtual Function
+      device can be used with VFIO on its own, however, physical devices will
+      require either all ports to be bound to VFIO, or only some of them bound
+      while others not bound to anything at all.</para>
 
       <para>If UEFI secure boot is enabled, the Linux kernel may disallow the
-      use of UIO on the system. Therefore, devices intended for use by the DPDK should be
-        bound to the <literal>vfio-pci</literal> kernel module rather than the 
-        <literal>igb_uio</literal>.</para>
-        </listitem>
-    
-        <listitem>
+      use of UIO on the system. Therefore, devices intended for use by the
+      DPDK should be bound to the <literal>vfio-pci</literal> kernel module
+      rather than the <literal>igb_uio</literal>.</para>
+    </listitem>
+
+    <listitem>
       <para><remark>STCR-6224</remark>The Automation Framework and Test
       Harness do not support multiple custom scripts uploaded to the device at
       the same time.</para>
@@ -137,4 +132,4 @@
 
   <!-- <xi:include href="jiraissues_generated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
-</chapter>
+</chapter>
\ No newline at end of file