I have tested this on below version: openshift v3.9.0-0.22.0 kubernetes v1.9.1+a0ce1bc657 Pod can be running with a valid disk after a bad disk request. Thanks
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:0489