@weibin, Could you help verify this bug on 4.1 since I saw you verify this on 4.2. thanks
Tested and verified on 4.1.0-0.nightly-2019-08-28-043410
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/RHSA-2019:2594