update with troubleshooting info

README.md

@@ -66,3 +66,36 @@ switch to version directory of choice and run these commands
 oc apply -f pipeline.yaml
 oc create -f pipeline-run.yaml
 ```
+
+# Known Issues
+
+## Time to install
+
+In testing we have seen the pipeline take from 2-6 hours to progress from installation of operators to active instances of the software.  please be patient.
+
+The pipeline is fully idempotent and can be restarted as needed.
+
+## DB2 crash loop
+
+known issues around db2 not coming up may cause problems with maximo manage installation:
+* https://github.com/ibm-mas/ansible-devops/issues/1039
+* https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=issues-watson-query#known-issues-dv__install-upgrade__title__1
+
+if the maximo manage activation is not progressing.  check to see if a pod that starts with something like inst1-masdev-manage-maxinst-* exists and view its logs.  If you see messages like "invalid tablespaces", check to see if db2 is healthy.  if db2u etcd pod is unhealthy or crashing, you can delete the pod to restart it.  
+
+at this point you will have to reset the db2 database with this workaround:
+
+Go to terminal c-db2w-shared-db2u-0 in db2u namespace
+
+```
+su -lc '/tmp/setupdb.sh | tee /tmp/setupdb.log' db2inst1
+```
+
+Go to project mas-inst1-manage
+Delete the pod inst1-masdev-manage-maxinst-*
+
+
+
+## TLS certs
+
+the pipeline looks for a lets-encrypt cert previously generated by upstream automation and if found uses this cert for maximo public routes.  This cert may not have all maximo paths enabled by default.  If you encounter a non-trusted certificate you may have to open the path in a separate browser window and accept the cert.