forked from rook/rook
The isUpgrade flag was being set every time the operator was started. This caused the upgrade checks to be run every time the operator restarted. Thus, if any mons were down, you likely would get stuck on the upgrade checks since another mon could not be stopped. We need to rely on the upgrade being detected either by a different image name from the cluster CR update, or from different versions of the daemons running in case the operator was restarted in the middle of an upgrade. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>