Comment 3 for bug 1419890

I'll set this for future pending some triaging. We decided it's not critical if the deployment is upgraded rather than blasted and redone (but keeping the jenkins volume). If we redeploy, we can also recreate the jenkins volume to get a clean slate which should help with this problem.