(DOCSP-13670) Production Notes Troubleshooting, correct version of MDB when running OM in local mode (#551)

* (DOCSP-13670) Production Notes Troubleshooting, correct version of MDB when running OM in local mode

* Address tech review

Author: JuliaMongo

source/includes/steps-deploy-k8s-opsmgr-local-mode.yaml

@@ -274,20 +274,24 @@ content: |
 
 ---
 
-title: "Copy the MongoDB installation archive to the |onprem| Persistent Volume for each |onprem| :opsmgrkube:`replica <spec.replicas>` you deployed."
+title: "Copy the MongoDB archive to the |onprem| Persistent Volume."
 level: 4
 ref: copy-mdb-archive
 stepnum: 10
 content: |
-
+  
+  Copy the MongoDB archive for each MongoDB version you intend to deploy
+  to the |onprem| Persistent Volume.
+  
   The commands that you use depend on the environment to which you
-  deployed the operator:
+  deployed the |k8s-op-short|:
 
   .. note::
 
-     Only copy the MongoDB installation tarballs to ``Replica 1`` and
-     beyond  if you deployed more than one |onprem| :opsmgrkube:`replica 
-     <spec.replicas>`. 
+     If you deployed more than one |onprem|
+     :opsmgrkube:`replica <spec.replicas>`, copy only the MongoDB
+     installation ``tarball`` packages to ``Replica 1`` and
+     beyond.
 
   .. tabs::
 
@@ -317,7 +321,7 @@ content: |
 
         #. If you deployed a version of |onprem| from 4.4.0 up to and
            including 4.4.3, copy the MongoDB   
-           Database Tools installation tarball to the |onprem|
+           Database Tools installation ``tarball`` to the |onprem|
            PersistentVolume. For example, to copy the
            ``{+mdbtools-version+}`` release:
 
@@ -341,7 +345,7 @@ content: |
         To copy the MongoDB installation archive to the 
         |onprem| PersistentVolume:
 
-        a. Copy the MongoDB Server installation tarball to the 
+        a. Copy the MongoDB Server installation ``tarball`` to the 
            |onprem| PersistentVolume. For example, to copy the ``4.4.0``
            release:
 
@@ -361,7 +365,7 @@ content: |
 
         #. If you deployed a version of |onprem| from 4.4.0 up to and
            including 4.4.3, copy the MongoDB 
-           Database Tools installation tarball to the |onprem|
+           Database Tools installation ``tarball`` to the |onprem|
            PersistentVolume. For example, to copy the
            ``{+mdbtools-version+}`` release:
 
@@ -393,7 +397,7 @@ content: |
      - :doc:`/tutorial/create-project-using-configmap`
 
   #. Deploy a :ref:`MongoDB database resource <k8s-deploy-mdb-resources>` 
-     in the same namespace to which you deployed |onprem|. 
+     in the same namespace to which you deployed |onprem|.
      Ensure that you:
 
      i. Match the ``spec.opsManager.configMapRef.name`` of the resource 
@@ -402,8 +406,8 @@ content: |
         the secret you created that contains an |onprem| programmatic 
         API key pair.
 
-  {+mdbagent+}\s running in MongoDB database resource containers that
-  you create with the |k8s-op-short| download the installation archives
-  from |onprem| instead of from the Internet. 
+  {+mdbagent+}\s run in MongoDB database resource containers that
+  you create with the |k8s-op-short|. Download the installation archives
+  from |onprem| instead of downloading them from the Internet.
 
 ...

source/reference/troubleshooting.txt

@@ -633,9 +633,9 @@ When you :ref:`configure TLS
 that you specify a valid certificate.
 
 If you don't specify the correct Domain Name for each |tls| certificate,
-the |k8s-op-short| logs may contain an error message similar to the
-following, where ``foo.svc.local`` is the incorrectly-specified Domain
-Name for the cluster member's Pod:
+the |k8s-op-short| :ref:`logs <review-k8s-op-logs>` may contain an error
+message similar to the following, where ``foo.svc.local`` is the
+incorrectly-specified Domain Name for the cluster member's Pod:
 
 .. code-block:: sh
    :copyable: false
@@ -658,3 +658,46 @@ To check whether you have correctly configured |tls| certificates:
 To learn more about |tls| certificate requirements, see
 :ref:`TLS prerequisites <secure-tls-prerequisites>`.
 
+Verify the MongoDB Version when Running in Local Mode
+-----------------------------------------------------
+
+MongoDB ``CustomResource`` may fail to reach a ``Running`` state
+if |onprem| is running in :ref:`Local Mode
+<deploy-om-container-local-mode>` and you specify either a version of MongoDB
+that doesn't exist, or a valid version of MongoDB for which
+|onprem| deployed in local mode did not download a corresponding MongoDB archive.
+
+If you specify a MongoDB version that doesn't exist, or a valid MongoDB
+version for which |onprem| coud not download a MongoDB archive, then
+even though the Pods can reach the ``READY`` state,
+the |k8s-op-short| :ref:`logs <review-k8s-op-logs>` contain an
+error message similar to the following:
+
+.. code-block:: sh
+   :copyable: false
+
+   Failed to create/update (Ops Manager reconciliation phase):
+   Status: 400 (Bad Request), Detail:
+   Invalid config: MongoDB version 4.10.1 is not available.
+
+This may mean that the {+mdbagent+} could not successfully download a
+corresponding MongoDB binary to the :file:`/var/lib/mongodb-mms-automation`
+directory. In cases when the {+mdbagent+} can download the MongoDB
+binary for the specified MongoDB version successfully, this directory
+contains a MongoDB binary folder, such as :file:`mongodb-linux-x86_64-4.4.0`.
+
+To check whether a MongoDB binary folder is present:
+
+1. Specify the Pod's name to this command:
+
+   .. code-block:: sh
+
+      kubectl exec --stdin --tty $<pod_name> /bin/sh
+
+2. Check whether a MongoDB binary folder is present in the
+   :file:`/var/lib/mongodb-mms-automation` directory.
+
+3. If you cannot locate a MongoDB binary folder,
+   `copy the MongoDB archive 
+   <../tutorial/deploy-om-container-local-mode.html#copy-the-mongodb-archive-to-the-onprem-persistent-volume>`__
+   into the |onprem| Persistent Volume for each deployed |onprem| replica set.