Bug 1329044

Description of problem:

When editing resource limits for a deployment, the messages and what is presented by the UI is confusing.

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

console.dev-preview-int.openshift.com

How reproducible:

Reproducible.

Steps to Reproduce:

Deploy an application which sets a resource memory limit below the threshold of 150Mi, such as 128Mi.

You will get an event error like:

Error creating: pods "wagtail-redis-1-" is forbidden: [Minimum memory usage per Pod is 150Mi, but request is 134217728., Minimum memory usage per Container is 150Mi, but request is 128Mi.]

Go to the deployment and select Actions->Set Resource Limits

The UI will show:

https://www.evernote.com/l/AHEI4IjX52BCObGWbbuiYNJWw4cP5KASKrI

"""
Request: 307 (but greyed out)
Limit: 128

Can't be less than 150 MiB.
Limit can't be less than request (307 MiB).
Memory limit total for all containers is less than pod minimum (150 MiB).
"""

So shows two messages, one say can't be less than 150MiB and the other that can't be less that 307MiB.

Change the Limit to 150 as know that is lower bound and messages change to:

https://www.evernote.com/l/AHFaKmyFdFVCar4ZVfu3_S2PNF3_Gfg8Zwo

"""
Request: 307 (but greyed out)
Limit: 150

Limit can't be less than request (307 MiB).
"""

This is confusing because I didn't set a memory Request value in the deployment configuration. When only having set Limit, that is all I sort of expect to need to update.

I would expect that if it knew Request wasn't set, that it would implicitly match the value of Limit if it was valid.

Instead I have to manually change Request to 150 as well to have it accept it.

Expected results:

Not be confusing. So is a usability issue.