Description of problem: Max unavailable and Max surge value are not shown on Deployment Config Details page Version-Release number of selected component (if applicable): 4.7.0-0.nightly-2020-11-12-063401 How reproducible: Always Steps to Reproduce: 1. create a deploymentconfig and check its details # oc get dc example -n yapei47 -o json | jq '.spec.strategy.type' "Rolling" # oc get dc example -n yapei47 -o json | jq '.spec.strategy.rollingParams.maxUnavailable' "25%" # oc get dc example -n yapei47 -o json | jq '.spec.strategy.rollingParams.maxSurge' 0 Actual results: 1. Max unavailable and Max surge value is not shown on details page Expected results: 1. Max unavailable and Max surge value should be shown on details page Additional info:
Max surge and max unavailable are now displayed on the deployment config page Version: 4.7.0-0.nightly-2020-11-17-005408 the fields in question are now visible on the deployment config page. see the screen shot attached.
Created attachment 1730474 [details] Screen shot showing the fields
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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-2020:5633