Back to bug 1369160
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jessica Forrester | 2016-08-22 14:40:40 UTC | Assignee | jforrest | spadgett |
| Jessica Forrester | 2016-08-22 23:03:32 UTC | Status | NEW | ASSIGNED |
| Jessica Forrester | 2016-08-23 12:57:56 UTC | Status | ASSIGNED | MODIFIED |
| errata-xmlrpc | 2016-08-24 19:31:30 UTC | Status | MODIFIED | ON_QA |
| Yanping Zhang | 2016-08-25 06:52:21 UTC | Status | ON_QA | VERIFIED |
| CC | yanpzhan | |||
| Samuel Padgett | 2016-09-14 12:39:55 UTC | Target Release | --- | 3.3.0 |
| Doc Text | Cause: On the pod metrics tab in the web console, we show the available CPU and memory for pods that have resource limits. Consequence: If a pod was using more CPU or memory than its limit, the available amount would show as a negative value. Fix: The web console was updated to show the amount over the limit in these cases. Result: Negative values no longer display for available pod CPU and memory . | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2016-09-27 00:34:03 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-09-27 09:45:31 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-09-27 05:45:31 UTC | |||
| Derek Carr | 2016-10-25 18:34:42 UTC | Depends On | 1336863 | |
| Dan McPherson | 2017-03-08 18:26:17 UTC | Target Release | 3.3.0 |
Back to bug 1369160