Why I cloned this bug 4.2? We still hit this issue when upgrade from 4.2 to 4.3.
The fix is in EO 4.3. But during upgrade, CLO was upgraded prior to EO, we still may hit this error (At that point EO is still 4.2, without the fix). I suggest backporting fix to EO 4.2
Verified in Elasticsearch Operator:4.3.1-202002032140
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.