Moved straight to ON_QA for validation. The belief is the original bug only exists in 4.1
Running ./test-020-olm-upgrade.sh on my 4.2 cluster returns all success
(In reply to Eric Matysek from comment #2) > Running ./test-020-olm-upgrade.sh on my 4.2 cluster returns all success This test only verifies the operator was upgraded and not that elasticsearch is still using the same storage
Verified via verification for https://bugzilla.redhat.com/show_bug.cgi?id=1743194
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days