ELCCR-1468 HA: Cannot upgrade NFV Access installationEnea_NFV_Access_2.4.0_RC3

Change-Id: I8a399d43dcfd6e5b845f90bf2e8e2e2c9bac6afc
Signed-off-by: Toma Bilius <toma.bilius@enea.com>

2 files changed, 128 insertions, 90 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml b/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
index 69e3b5d..9f9a50d 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
@@ -71,22 +71,24 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
         <para>Start the <literal>ucpemanager</literal> service.</para>
       </listitem>
     </itemizedlist>
-        
-        <para><olink
-    targetdoc="book_enea_nfv_access_getting_started"
-    targetptr="fresh_ucpemg_install">Fresh Installation of the Enea uCPE Manager in the
-    <ns:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
-    xpointer="element(book_enea_nfv_access_getting_started/1)"
-    xmlns:ns="http://www.w3.org/2001/XInclude" /></olink> Manual contains information 
-        about the input required to be entered during the execution of the upgrade script.</para>
 
-    <para>For an example on how to upgrade an Enea uCPE Manager installation in a
-    High Availability setup, consult <olink
+    <para><olink targetdoc="book_enea_nfv_access_getting_started"
+    targetptr="fresh_ucpemg_install">Fresh Installation of the Enea uCPE
+    Manager in the <ns:include
+    href="../../s_docbuild/olinkdb/pardoc-names.xml"
+    xmlns:ns="http://www.w3.org/2001/XInclude"
+    xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+    Manual contains information about the input required to be entered during
+    the execution of the upgrade script.</para>
+
+    <para>For an example on how to upgrade an Enea uCPE Manager installation
+    in a High Availability setup, consult <olink
     targetdoc="book_enea_nfv_access_getting_started"
     targetptr="ha_upgrade">Upgrading a High Availability Deployment in the
     <ns:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
-    xpointer="element(book_enea_nfv_access_getting_started/1)"
-    xmlns:ns="http://www.w3.org/2001/XInclude" /></olink> Manual.</para>
+    xmlns:ns="http://www.w3.org/2001/XInclude"
+    xpointer="element(book_enea_nfv_access_getting_started/1)" /></olink>
+    Manual.</para>
 
     <section id="restore_prev_ucpe_install">
       <title>Restoring a previous Enea uCPE Manager Installation</title>
@@ -235,6 +237,15 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
           upgrades the uCPE device to a newer version.</para>
         </listitem>
       </orderedlist>
+
+      <note>
+        <para>Upgrading from Enea NFV Access 2.3.0 is not possible when using
+        the Enea uCPE Manager in HTTPS mode. Either switch to HTTP by accessing
+        <emphasis role="bold">System</emphasis>, <emphasis
+        role="bold">Configuration</emphasis>, <emphasis role="bold">Web
+        Access</emphasis> and checking the <emphasis role="bold">Enable
+        HTTP</emphasis> box, or installing it manually.</para>
+      </note>
     </section>
 
     <section id="mg_upgrade">
@@ -390,10 +401,10 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
             can accept an image file is populated when the image file is
             chosen.</para>
 
-            <para>Mark the uCPE devices that you wish to upgrade and 
-                        press the <emphasis role="bold">&gt;</emphasis> button to
-            move the uCPE devices to the right side of the selector. Those
-            chosen form the list of uCPE devices that will be upgraded.</para>
+            <para>Mark the uCPE devices that you wish to upgrade and press the
+            <emphasis role="bold">&gt;</emphasis> button to move the uCPE
+            devices to the right side of the selector. Those chosen form the
+            list of uCPE devices that will be upgraded.</para>
           </listitem>
 
           <listitem>
@@ -420,9 +431,11 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
               </listitem>
             </itemizedlist>
           </listitem>
-                  
-                  <listitem><para>To start the upgrade, click 
-                  <emphasis role="bold">ok</emphasis>.</para></listitem>
+
+          <listitem>
+            <para>To start the upgrade, click <emphasis
+            role="bold">ok</emphasis>.</para>
+          </listitem>
         </itemizedlist>
 
         <note>
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 31d3a03..a1a5db3 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
@@ -84,80 +84,94 @@
     </listitem>
 
     <listitem>
-      <para><remark>ELCCR-912</remark>When the Enea uCPE Manager 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>ELCCR-912</remark>When the Enea uCPE Manager 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-854</remark>Changing the management interface IP
+      address will result in a temporary loss of connection with the uCPE
+      device. If the device is behind a NAT, while using the Call Home
+      connection, reestablishing the connection automatically could take up to
+      20 minutes. Restarting the vCPE Overlay will immediately reestablish the
+      connection, but that implies the existence of an alternate way to
+      trigger the vCPE restart operation on the device.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>USERDOCAP-641</remark>Enea NFV Access does not have
+      support for IPv6 addresses on both uCPE devices and the Enea uCPE
+      Manager installation.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1428</remark>Wireless AP creation through the REST
+      API does not validate that the wireless interface and LAN bridge are
+      configured. Using these parameters may result in undefined
+      behavior.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1351</remark>The updated
+      <filename>.Keystore</filename> and <filename>server.xml</filename> files
+      from the
+      <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/</literal>
+      folder are overwritten during a product upgrade. As a workaround for
+      this issue, after an upgrade, copy the updated
+      <filename>.Keystore</filename> and <filename>server.xml</filename> files
+      into the
+      <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/</literal>
+      folder and restart the ucpemanager service.</para>
+    </listitem>
+
+    <listitem>
+      <para><remark>ELCCR-1371</remark>The current self-signed certificate for
+      the Enea uCPE Manager is generated at build time, with a hard-coded
+      common-name causing the uCPE device upgrade to fail in HTTPS mode. As a
+      workaround, another certificate (containing an IP based common-name)
+      must be generated.</para>
+
+      <para>Perform the following the steps to generate the
+      certificate:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Stop the uCPE Manager service.</para>
+        </listitem>
+
+        <listitem>
+          <para>Create the certificate using the
+          <filename>createCertificate.sh</filename> script from distribution
+          folder. This will create a new <filename>.Keystore</filename> file
+          and copy it into the
+          <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates</literal>
+          folder.</para>
+        </listitem>
+
+        <listitem>
+          <para>Start the Enea uCPE Manager, the new certificate should now
+          take effect.</para>
         </listitem>
+      </orderedlist>
+    </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-854</remark>Changing the management interface IP address 
-        will result in a temporary loss of connection with the uCPE device. If the 
-        device is behind a NAT, while using the Call Home connection, 
-        reestablishing the connection automatically could take up to 20 minutes. 
-        Restarting the vCPE Overlay will immediately reestablish the connection, 
-        but that implies the existence of an alternate way to trigger the vCPE 
-        restart operation on the device.</para>
-    </listitem>
-
-    <listitem>
-      <para><remark>USERDOCAP-641</remark>Enea NFV Access does not have support 
-        for IPv6 addresses on both uCPE devices and the Enea uCPE Manager 
-        installation.</para>
-    </listitem>
-    
-    <listitem>
-      <para><remark>ELCCR-1428</remark>Wireless AP creation through the REST 
-        API does not validate that the wireless interface and LAN bridge are 
-        configured. Using these parameters may result in undefined behavior.</para>
-    </listitem>
-        
-        <listitem>
-      <para><remark>ELCCR-1351</remark>The updated <filename>.Keystore</filename>
-          and <filename>server.xml</filename> files from the 
-          <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/</literal> 
-          folder are overwritten during a product upgrade. As a workaround for 
-        this issue, after an upgrade, copy the updated <filename>.Keystore</filename> 
-        and <filename>server.xml</filename> files into the 
-        <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/</literal> 
-        folder and restart the ucpemanager service.</para>
-        </listitem>
-
-    <listitem>
-      <para><remark>ELCCR-1371</remark>The current self-signed certificate for 
-          the Enea uCPE Manager is generated at build time, with a hard-coded common-name 
-          causing the uCPE device upgrade to fail in HTTPS mode. As a workaround, 
-          another certificate (containing an IP based common-name) must be generated.</para>
-          
-          <para>Perform the following the steps to generate the certificate:</para>
-          
-          <orderedlist>
-                <listitem><para>Stop the uCPE Manager service.</para></listitem>
-                
-                <listitem><para>Create the certificate using the 
-                  <filename>createCertificate.sh</filename> script from distribution 
-                  folder. This will create a new <filename>.Keystore</filename> file 
-                  and copy it into the 
-                <literal>/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates</literal> 
-                folder.</para></listitem>
-                
-                <listitem><para>Start the Enea uCPE Manager, the new certificate 
-                  should now take effect.</para></listitem>
-          </orderedlist>
-    </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-907</remark>At times the VIP address is not acquired 
-        by any of the backup nodes if a power failure happens on primary node 
-        in a High Availability setup. To recover, follow the official documentation 
-        available at <ulink
-  url="https://mariadb.com/kb/en/galera-cluster-recovery/">Galera Cluster Recovery</ulink>.</para>    
+      <para><remark>ELCCR-907</remark>At times the VIP address is not acquired
+      by any of the backup nodes if a power failure happens on primary node in
+      a High Availability setup. To recover, follow the official documentation
+      available at <ulink
+      url="https://mariadb.com/kb/en/galera-cluster-recovery/">Galera Cluster
+      Recovery</ulink>.</para>
     </listitem>
 
     <listitem condition="hidden">
@@ -168,6 +182,17 @@
       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>ELCCR-1468</remark>When using the Enea uCPE Manager 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_nfv_access_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_nfv_access_getting_started/1)" /></olink>
+Manual) or install it manually.</para>
+    </listitem>
   </itemizedlist>
 
   <!-- The file with a section below is autocreated by make init  -->