diff --git a/charts/ibm-mqadvanced-server-dev/README.md b/charts/ibm-mqadvanced-server-dev/README.md
index 105c750..45f8640 100644
--- a/charts/ibm-mqadvanced-server-dev/README.md
+++ b/charts/ibm-mqadvanced-server-dev/README.md
@@ -75,6 +75,11 @@ Alternatively, a YAML file that specifies the values for the parameters can be p
 
 The chart mounts a [Persistent Volume](http://kubernetes.io/docs/user-guide/persistent-volumes/).
 
+# Troubleshooting
+
+## Cannot create a GlusterFS PersistentVolumeClaim
+The generated PVC name is too long.  See [here](https://www-03preprod.ibm.com/support/knowledgecenter/SSBS6K_2.1.0-beta/troubleshoot/cannot_create_pvc.html) for more information.  You can shorten the claim name using the `dataPVC.name` parameter.
+
 # Copyright
 
 © Copyright IBM Corporation 2017
diff --git a/charts/ibm-mqadvanced-server-prod/README.md b/charts/ibm-mqadvanced-server-prod/README.md
index 6dc330f..77be58f 100644
--- a/charts/ibm-mqadvanced-server-prod/README.md
+++ b/charts/ibm-mqadvanced-server-prod/README.md
@@ -182,6 +182,11 @@ Finally, build and push the image to your registry.
 
 You can then use the new image when you deploy MQ into your cluster. You will find that once you have run the image you will be able to see your new default objects and users.
 
+# Troubleshooting
+
+## Cannot create a GlusterFS PersistentVolumeClaim
+The generated PVC name is too long.  See [here](https://www-03preprod.ibm.com/support/knowledgecenter/SSBS6K_2.1.0-beta/troubleshoot/cannot_create_pvc.html) for more information.  You can shorten the claim name using the `dataPVC.name` parameter.
+
 # Copyright
 
 © Copyright IBM Corporation 2017