+++ 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. ***
Create a deployment, check values on Deployment details page: when maxUnavailable is set to 0, Max Unavailable shows '0 of 2 pods' When maxSurge is set to 0, Max Surge shows '0 greater than 2 pods' For Deployment Config, fix for this bug should be good but we can't check the display due to bug https://bugzilla.redhat.com/show_bug.cgi?id=1897423 Moving this to VERIFIED since the original issue reported has been resolved Verified on 4.6.0-0.nightly-2020-11-12-142005
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 (OpenShift Container Platform 4.6.6 bug fix 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/RHBA-2020:5115