From 50ec23f8b7c30ce72f90e65ee7af11162517f78a Mon Sep 17 00:00:00 2001
From: Scott Koranda <skoranda@gmail.com>
Date: Mon, 22 Mar 2021 08:58:23 -0500
Subject: [PATCH] Add documentation on how to fix bad bootstrap.

Add documentation on how to fix bad bootstrap.
---
 README.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/README.md b/README.md
index 6650bee..c7e9ec0 100644
--- a/README.md
+++ b/README.md
@@ -283,6 +283,22 @@ https://registry2.comanage.incommon.training
 
 for node 2, and so on.
 
+## Fixing a bad bootstrap
+
+Trainees that do not follow the instructions closely may bootstrap
+COmanage Registry with a configuration that does not allow them
+to authenticate as the platform administrator. When that happens
+follow these steps on the training node as the root user:
+
+1. `docker stack rm comanage`
+1. `cd /srv/docker/var/lib/mysql`
+1. `rm -rf ./`
+1. `cd /srv/docker/srv/comanage-registry/local/Config`
+1. `rm -rf ./`
+
+Then tell the user to correct the error in the stack file
+and try again.
+
 ## Interference from existing SSH agent
 
 If you find that your existing SSH agent is interfering with the SSH connections