[7/8] git commit: Add troubleshooting section to vagrant.md

[ke...@apache.org]

Add troubleshooting section to vagrant.md

Add a troubleshooting section to the vagrant documentation.


Project: http://git-wip-us.apache.org/repos/asf/incubator-aurora/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-aurora/commit/130d4668
Tree: http://git-wip-us.apache.org/repos/asf/incubator-aurora/tree/130d4668
Diff: http://git-wip-us.apache.org/repos/asf/incubator-aurora/diff/130d4668

Branch: refs/heads/master
Commit: 130d466852800643410f1f55c8e3cf34fc4a36ab
Parents: 52b566c
Author: Zameer Manji <zm...@twitter.com>
Authored: Mon Dec 2 18:06:50 2013 -0800
Committer: Zameer Manji <zm...@twitter.com>
Committed: Mon Dec 2 18:06:50 2013 -0800

----------------------------------------------------------------------
 docs/vagrant.md | 7 +++++++
 1 file changed, 7 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-aurora/blob/130d4668/docs/vagrant.md
----------------------------------------------------------------------
diff --git a/docs/vagrant.md b/docs/vagrant.md
index 971a662..15d72bc 100644
--- a/docs/vagrant.md
+++ b/docs/vagrant.md
@@ -9,3 +9,10 @@ The observer is listening on http://192.168.33.4:1338/
 The master is listening on http://192.168.33.3:5050/
 
 Once everything is up, you can `vagrant ssh aurora-scheduler` and execute aurora client commands using the `aurora` client.
+
+Troubleshooting
+---------------
+Most of the vagrant related problems can be fixed by the following steps:
+* Destroying the vagrant environment with `vagrant destroy`
+* Cleaning the repository of build artifacts and other intermediate output with `git clean -fdx`
+* Bringing up the vagrant environment with `vagrant up`