Bug 1894110

Summary:	Console shows wrong value for maxUnavailable and maxSurge when set to 0
Product:	OpenShift Container Platform	Reporter:	Samuel Padgett <spadgett>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED ERRATA	QA Contact:	Yanping Zhang <yanpzhan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.7	CC:	aos-bugs, asheth, jokerman, yapei
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Console allows for maxUnavailable or maxSurge fields to be set to 0. Consequence: Console shows wrong value for maxUnavailable and maxSurge when set to 0 Fix: Default maxUnavailable or maxSurge value to 1 Result: Console shows right value for maxUnavailable and maxSurge when set to 0	Story Points:	---
Clone Of:		Environment:	Version: 4.7.0-0.nightly-2020-10-27-051128 Cluster ID: 760f002b-ec12-4c94-a1a1-a305493025c6 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:81.0) Gecko/20100101 Firefox/81.0
Last Closed:	2021-02-24 15:31:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1894227

Description Samuel Padgett 2020-11-03 15:03:15 UTC

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.

Comment 1 Samuel Padgett 2020-11-03 18:04:11 UTC

*** Bug 1891820 has been marked as a duplicate of this bug. ***

Comment 2 Samuel Padgett 2020-11-03 18:07:08 UTC

*** Bug 1891820 has been marked as a duplicate of this bug. ***

Comment 4 Yanping Zhang 2020-11-09 07:39:09 UTC

Tested against pr7083, create deployment in project, when set either maxUnavailable or maxSurge to 0, it will show 0 now.
The bug is fixed.

Comment 7 errata-xmlrpc 2021-02-24 15:31:01 UTC

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