Comment 1 for bug 1419890

I will be checking this deeper now but I suspect this may not be a problem on production because of the way IS upgrade specs keeping the storage volume intact for Jenkins. On my tests I am simply destroying everything and restarting from scratch, while the storage is kept intact. IS won't probably (nor could) just destroy and start afresh like that.