COSNOSCR-576 final corrections made to the install. guide and rel info. ver update.

1 files changed, 48 insertions, 30 deletions

diff --git a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
index c24d2a9..55e9be7 100644
--- a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
+++ b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
@@ -276,9 +276,32 @@
             <para>Workaround:</para>
 
             <para>Starting the <literal>systemd</literal> service manually
-            makes it run successfully. Enea NFV Core 1.0.1 will be shipped
-            without Openstack Resource Agents, therefore this issue should not
-            affect the user.</para>
+            makes it run successfully. Enea NFV Core 1.0.1 is shipped without
+            Openstack Resource Agents, therefore this issue should not affect
+            the user.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Issue #2 with Openstack Resource Agents and Compute Fencing
+        functionality</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>In an OPNFV deployment that uses Openstack Resource Agents,
+            when we configure the <literal>fence_compute</literal> as a
+            Pacemaker resource, the Controller nodes start to reboot each
+            other endlessly.</para>
+          </listitem>
+
+          <listitem>
+            <para>Workaround:</para>
+
+            <para>Enea NFV Core 1.0.1 is shipped without Openstack Resource
+            Agents, therefore this issue should not affect the user.</para>
           </listitem>
         </itemizedlist>
       </listitem>
@@ -319,30 +342,6 @@
       </listitem>
 
       <listitem>
-        <para>Issue #2 with Openstack Resource Agents and Compute Fencing
-        functionality</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>Description and Impact:</para>
-
-            <para>In an OPNFV deployment that uses Openstack Resource Agents,
-            when we configure the <literal>fence_compute</literal> as a
-            Pacemaker resource, the Controller nodes start to reboot each
-            other endlessly.</para>
-          </listitem>
-
-          <listitem>
-            <para>Workaround:</para>
-
-            <para>Enea NFV Core 1.0.1 will be shipped without Openstack
-            Resource Agents, therefore this issue should not affect the
-            user.</para>
-          </listitem>
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
         <para>Offline Deploy with Fuel fails at times</para>
 
         <itemizedlist>
@@ -373,7 +372,7 @@
 
         <itemizedlist>
           <listitem>
-            <para>Description and Impact</para>
+            <para>Description and Impact:</para>
 
             <para>There is a short period of a few seconds after a VM stated
             the boot procedure when attaching an external volume will result
@@ -381,11 +380,11 @@
             kernel.</para>
 
             <para>Disks attached in the first few seconds of the booting
-            procedure of a VM, will fail to register in the guest VM..</para>
+            procedure of a VM, will fail to register in the guest VM.</para>
           </listitem>
 
           <listitem>
-            <para>Workaround</para>
+            <para>Workaround:</para>
 
             <para>Attach volumes to a VM only before the VM is booting or
             after the period of a few seconds has passed since the booting
@@ -393,6 +392,25 @@
           </listitem>
         </itemizedlist>
       </listitem>
+
+      <listitem>
+        <para>Fuel Healthcheck Stack creation with wait condition test,
+        fails</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>The platform test case (create stack with wait condition)
+            from the Fuel Healthcheck, fails. This has no impact on overall
+            cluster functionality.</para>
+          </listitem>
+
+          <listitem>
+            <para>Workaround: N/A.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
     </orderedlist>
   </section>