Erik, Yes, I double checked with latest OCP3.11, this problem have been fixed. Do you have plan to provide a fix in 3.10.z since this problem really exist in OCP3.10?
@Zhang no plans to backport to 3.10.z
Changing status to Verified base on comment 2 & comment 3
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-2018:2652