Bug 1894110 - Console shows wrong value for maxUnavailable and maxSurge when set to 0
Summary: Console shows wrong value for maxUnavailable and maxSurge when set to 0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.7.0
Assignee: Jakub Hadvig
QA Contact: Yanping Zhang
URL:
Whiteboard:
: 1891820 (view as bug list)
Depends On:
Blocks: 1894227
TreeView+ depends on / blocked
 
Reported: 2020-11-03 15:03 UTC by Samuel Padgett
Modified: 2023-12-15 20:00 UTC (History)
4 users (show)

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
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
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7083 0 None closed Bug 1894110: Handle values of 0 for maxUnavailable and maxSurge 2021-01-15 13:08:53 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:31:05 UTC

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


Note You need to log in before you can comment on or make changes to this bug.