WMS 3427 OpenSearch Conversational Search, fix typos and more details. (oracle-livelabs#421)

* Opensearch Conversational Search Demo app stack lab

* more image alt text

* fix image

* more specific file names to avoid confusion

* typo

* WMS 3427 OpenSearch Conversational Search, fix typos and more details.

Author: streamnsight

oci-opensearch/conversational-with-rag/conversational-with-rag-demo-stack.md

@@ -11,7 +11,7 @@ Estimated Time: 15 minutes
 
 In this lab, you will:
 
-- Deploy the Conversational Search Demo application via the Ressource Manager. 
+- Deploy the Conversational Search Demo application via the Resource Manager. 
 
 The stack deploys a new VCN (if needed) a new cluster (if needed), the application (in a container inastance), and a load balancer.
 
@@ -31,7 +31,7 @@ You will also need a subscription to the Chicago or Frankfurt regions, which hos
 
 ## Step 2: Launch the Demo Stack
 
-The stack consists in a terraform script launched via Ressource Manager.
+The stack consists in a terraform script launched via Resource Manager.
 
 Click the following link to get started: 
 
@@ -84,8 +84,13 @@ You will be prompted to enter the OCID of the OpenSearch cluster.
 
 ![Paste OCID](../images/image-demo-opensearch-ocid2.png)
 
+## Step 7: Enter the Username and Password For the Cluster
 
-## Step 7: Configure Networking Information
+- **Enter** the **user** and **password** you specified at the time of cluster creation.
+
+![Enter User and Password](../images/image-demo-cluster-user-pass.png)
+
+## Step 8: Configure Networking Information
 
 The application needs to be deployed in the same VCN and subnet as the cluster, so you will be prompted to enter the VCN and subnet information.
 
@@ -102,7 +107,7 @@ If you followed the labs from the start, you should only have 1 VCN in the compa
 ![Select VCN, Private and Public Subnets](../images/image-demo-network.png)
 
 
-## Step 8: Deploy
+## Step 9: Deploy
 
 **Click** the **Next** button at the bottom of the page to start the deployment.
 
@@ -111,7 +116,7 @@ The Stack will deploy and show logs
 ![Deploy Stack - Accepted](../images/image-demo-rmj-accepted.png)
 
 
-## Step 9: Find the Application URL
+## Step 10: Find the Application URL
 
 - Once done, the stack switches to green.
 
@@ -125,7 +130,7 @@ The Stack will deploy and show logs
 
 - **Copy** the URL, and paste it in you browser
 
-## Step 10: Interact With the Application
+## Step 11: Interact With the Application
 
 You should see the application interface in your browser. If it doesn't show right away, wait a minute or two. The application loads and embeds data at start up, which can take a couple minutes.
 
@@ -146,6 +151,26 @@ You can ask questions like:
 
 To learn more about how this works, you can now proceed to the next lab, which guides you through the process the app uses step-by-step.
 
+## Step 12: Troubleshooting the Deployment
+
+- When accessing the URL, the page shows error 402 Bad Gateway:
+    - Give it a minute or two before reloading the page: when the app loads, it ingests the demo data which may take a couple minutes, before the app is effectively started.
+
+- After several minutes, the page still shows error 402 Bad Gateway:
+    - Check the application logs: 
+        - Search the menu for Container Instances
+        - Look up the Container instance created by the stack, named `opensearch-demo-YYYY`.
+        - Select the container `opensearch-demo-YYY` in the resources menu (bottom left)
+        - Open the logs, and look for latest error if any.
+
+        There may be auth error 401 trying to authenticate to the cluster: this indicates that wrong credentials were provided. You can open the stack and look at variables. There you can choose to Edit variables and update the credentials, then re-apply the stack.
+
+        There may be 409 errors with rate limit exceeded. This is normal as long as the 500 dem data records get ingested. However if the startup process never finished, and the last logs don't indicate the app was started, something went wrong during ingestion.
+
+        Timeout during ingestion may indicate the VCN configuration is wrong. If the VN was created with the wizard, it should have a public nad private subnets, with an Internet Gateway on the public subnet, and a Service Gateway and NAT gateway in the private subnet. You should also have created a security list to open port 9200 for OpenSearch API.
+
+If you can't figure what may be wrong, feel free to contact us with the contact button, and please provide the full app log in your email.
+
 
 ## Acknowledgements