+++ This bug was initially created as a clone of Bug #1894227 +++ +++ This bug was initially created as a clone of Bug #1894110 +++ On the Deployment page, the console will show the value 1 if either maxUnavailable or maxSurge is set to 0. These fields are allowed to be set to 0 (as long as they're not both 0). We should only show the default value as 1 if the fields are missing from the resource YAML. --- Additional comment from spadgett on 2020-11-03 18:04:11 UTC --- *** Bug 1891820 has been marked as a duplicate of this bug. *** --- Additional comment from spadgett on 2020-11-03 18:07:08 UTC --- *** Bug 1891820 has been marked as a duplicate of this bug. ***
Checked on ocp 4.5 cluster with payload 4.5.0-0.nightly-2020-11-15-110315. Create deployment, and edit to set maxUnavailable or maxSurge to 0, after save, the related item shows 0 on the detail page. The bug is fixed.
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.5.20 bug fix and golang security 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:5118