Newly deployed subcloud firmware_sync_status stays out-of-sync (pick stx 5.0, 6.0)

Added Warning Note
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: I50410a8bcb2f641e0a00e0de7fd7e9c05d8a01fa

doc/source/dist_cloud/kubernetes/device-image-update-orchestration.rst

@@ -35,9 +35,9 @@ device image updates, including |FPGA| updates.
 
 -   Only one type of dcmanager strategy can exist at a time. Run
     :command:`dcmanager fw-update-strategy delete` to delete any existing
-    strategies before creating a new update \(patch\) strategy. Similarly, after
-    using an update \(patch\) strategy you will need to delete it before creating a
-    fw-update strategy.
+    strategies before creating a new update (patch) strategy. Similarly, after
+    using an update (patch) strategy you will need to delete it before
+    creating a fw-update strategy.
 
 -   Before applying a new functional device image for the same |PCI|
     vendor/device and label as a functional image that has already been applied,
@@ -52,7 +52,6 @@ device image updates, including |FPGA| updates.
 
 #.  Assign labels to |PCI| devices in each subcloud.
 
-
     #.  List known devices on a host.
 
         To list devices from a subcloud, run:
@@ -61,7 +60,7 @@ device image updates, including |FPGA| updates.
 
             ~(keystone_admin)]$ system host-device-list <hostname_or_id>
 
-        To list devices from the central cloud, run:
+        To list devices from the Central cloud, run:
 
         .. code-block:: none
 
@@ -84,9 +83,8 @@ device image updates, including |FPGA| updates.
             Either use single label for each hardware device, or use caution to
             avoid this scenario if using multiple device labels per device.
 
-
-#.  From the central cloud, upload one or more device images in the SystemController region.
-
+#.  From the Central cloud, upload one or more device images in the System
+    Controller region.
 
     -   To upload a root-key device image:
 
@@ -110,9 +108,9 @@ device image updates, including |FPGA| updates.
     For more information about uploading images, see |node-doc|:
     :ref:`Uploading a Device Image <uploading-a-device-image>`.
 
-#.  Apply one or more device images in the SystemController region.
+#.  Apply one or more device images in the System Controller region.
 
-    you can apply multiple device images in the SystemController region
+    You can apply multiple device images in the System Controller region
     provided they are for different devices or different labels.
 
     .. note::
@@ -128,9 +126,11 @@ device image updates, including |FPGA| updates.
     For more information about applying images, see |node-doc|: :ref:`Updating
     an Intel N3000 FPGA Image <updating-an-intel-n3000-fpga-image>`.
 
-#.  Create an update strategy using the :command:`fw-update-strategy create` command.
+#.  Create an update strategy using the :command:`fw-update-strategy create`
+    command.
 
-    The update strategy controls how |FPGA| updates are applied to hosts on subclouds.
+    The update strategy controls how |FPGA| updates are applied to hosts on
+    subclouds.
 
     .. code-block:: none
 
@@ -208,7 +208,8 @@ device image updates, including |FPGA| updates.
 #.  Monitor progress as the strategy is applied.
 
 
-    -   To monitor the step currently being performed on all subclouds, do the following:
+    -   To monitor the step currently being performed on all subclouds, do the
+        following:
 
         .. code-block:: none
 
@@ -224,7 +225,8 @@ device image updates, including |FPGA| updates.
             +-----------+-------+----------+------------------------------+----------------------------+----------------------------+
 
 
-    -   To monitor the step currently being performed on a specific subcloud, do the following:
+    -   To monitor the step currently being performed on a specific subcloud,
+        do the following:
 
         .. code-block:: none
 

doc/source/dist_cloud/kubernetes/reinstalling-a-subcloud-with-redfish-platform-management-service.rst

@@ -7,13 +7,18 @@ Reinstall a Subcloud with Redfish Platform Management Service
 =============================================================
 
 For subclouds with servers that support Redfish Virtual Media Service
-\(version 1.2 or higher\), you can use the Central Cloud's CLI to reinstall
-the ISO and bootstrap subclouds from the Central Cloud.
+\(version 1.2 or higher\), you can use the Central cloud's CLI to reinstall
+the ISO and bootstrap subclouds from the Central cloud.
 
 .. caution::
 
    All application and data on the subcloud will be lost after reinstallation.
 
+   Any records of |FPGA| device image updates on the subcloud will be lost.
+   You will need to reapply the |FPGA| device image update orchestration
+   procedure. For more information, see :ref:`Device Image Update Orchestration
+   <device-image-update-orchestration>`.
+
 .. rubric:: |context|
 
 The subcloud reinstallation has these phases:
@@ -36,7 +41,7 @@ Executing the dcmanager subcloud reinstall command in the Central Cloud:
 - The install values are required for subcloud reinstallation. By default,
   install values are stored in database after a subcloud installation or
   upgrade, and the reinstallation will re-use these values. You can use the
-  following CLI command in the Central Cloud to update them if necessary:
+  following CLI command in the Central cloud to update them if necessary:
 
   .. code-block:: none
 
@@ -46,13 +51,13 @@ Executing the dcmanager subcloud reinstall command in the Central Cloud:
   Subcloud Using Redfish Platform Management Service
   <installing-a-subcloud-using-redfish-platform-management-service>`.
 
-  You can only reinstall the same software version with the Central Cloud on
-  the subcloud.  If the software version of the subcloud is not same as the
-  system controller, the reinstall command will update the software version of
+  You can only reinstall the same software version with the Central cloud on
+  the subcloud. If the software version of the subcloud is not same as the
+  System Controller, the reinstall command will update the software version of
   the subcloud and install the correct version afterwards.
 
 
-- Check the subcloud's availability in the Central Cloud.
+- Check the subcloud's availability in the Central cloud.
 
   For example:
 
@@ -110,11 +115,16 @@ Executing the dcmanager subcloud reinstall command in the Central Cloud:
        This will reinstall the subcloud. All applications and data on the
        subcloud will be lost.
 
+       Any records of |FPGA| device image updates on the subcloud will be lost.
+       You will need to reapply the |FPGA| device image update orchestration
+       procedure. For more information, see :ref:`Device Image Update Orchestration
+       <device-image-update-orchestration>`.
+
     Please type ``reinstall`` to confirm: reinstall
 
     Any other input will abort the reinstallation.
 
-#.  In the Central Cloud, monitor the progress of the subcloud installation
+#.  In the Central cloud, monitor the progress of the subcloud installation
     and bootstrapping by viewing the deploy status field of the dcmanager
     subcloud list command.
 
@@ -135,7 +145,7 @@ Executing the dcmanager subcloud reinstall command in the Central Cloud:
 
     You can also monitor detailed logging of the subcloud installation and
     bootstrapping by monitoring the following log file on the active
-    controller in the Central Cloud:
+    controller in the Central cloud:
 
     -   /var/log/dcmanager/ansible/subcloud1_playbook_output.log