There has been fixes on this. QE can please confirm that this issue has been addressed.
No such issue for now.
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-0.nightly-2019-02-26-125216 True False 26h Cluster version is 4.0.0-0.nightly-2019-02-26-125216
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.