Comment 4 for bug 1549857

Note the root cause was that this was a multinode install and the pull action was not being run prior to a redeploy. There are docs fixes in the queue to help people avoid this problem in the future.