Bug 1894227
Summary: | Console shows wrong value for maxUnavailable and maxSurge when set to 0 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.7 | CC: | aos-bugs, asheth, jokerman, spadgett, yapei |
Target Milestone: | --- | ||
Target Release: | 4.6.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-30 16:45:31 UTC | Type: | --- |
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: | 1894110 | ||
Bug Blocks: | 1896990 |
Description
OpenShift BugZilla Robot
2020-11-03 18:47:06 UTC
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 |