Bug 2109854

Summary: Max unavailable and Max surge have inaccurate description
Product: OpenShift Container Platform Reporter: Pavel Kratochvil <pakratoc>
Component: Management ConsoleAssignee: Pavel Kratochvil <pakratoc>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.12CC: jhadvig, yapei
Target Milestone: ---   
Target Release: 4.12.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Wrong description for Max unavailability and Max surge fields Consequence: User can get confused since form fields have wrong descriptions Fix: Update the fields description Result: Proper description
 Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-17 19:53:12 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:
Attachments:
Description Flags
Edit update strategy window none

Description Pavel Kratochvil 2022-07-22 10:34:32 UTC 
Created attachment 1898686 [details]
Edit update strategy window

Description of problem:
Max unavailable and Max surge have inaccurate description in 'Edit update strategy' window. Both of the descriptions are the same and neither of them provide enough information to the user.

Version-Release number of selected component (if applicable):
4.12

How reproducible:
100%

Steps to Reproduce:
1. Select Workloads in menu
2. Select Deployments
3. Select any Deployment available
4. Pick 'Edit Update Strategy' from drop down menu

Actual results:
Shows 'Number or percentage of total pods at the start of the update (optional)' description for both(Max surge, Max unavailable).

Expected results:
Provide actual useful description which would inform the user about the fields.

Link to k8s docs:
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-unavailable
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-surge

Additional info:
Comment 2 Yadan Pei 2022-09-13 02:24:52 UTC 
Click on any Deployment -> Actions -> Edit update strategy, check the description Max unavailable and Max surge

Max unavailable: Percentage of total number of pods or the maximum number of pods that can be unavailable during the update(optional)


Max surge: Percentage of total number of pods or the maximum number of pods that can be scheduled above the original number of pods(optional)



the description is more readable and reasonable

verified on 4.12.0-0.nightly-2022-09-12-152748
Comment 5 errata-xmlrpc 2023-01-17 19:53:12 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.12.0 bug fix and 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-2022:7399