Bug 1333162 - Quota terminating scope descriptions aren't clear
Summary: Quota terminating scope descriptions aren't clear
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.2.0
Hardware: All
OS: Mac OS
medium
low
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-04 19:35 UTC by Shawn Purtell
Modified: 2017-07-24 14:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-12 19:05:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0884 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 22:50:07 UTC

Description Shawn Purtell 2016-05-04 19:35:19 UTC
Description of problem:
On Project Settings page, difference between Not Terminating and Terminating quotas are not clear

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

How reproducible:
Very

Steps to Reproduce:
1. Go to Settings Page
2. Look at first two quotas
3. wtf is that second section?

Actual results:


Expected results:


Additional info:

Comment 1 Jessica Forrester 2016-05-05 20:44:53 UTC
the description next to the terminating quota could add something useful that says "... like builds"

Comment 3 Troy Dawson 2017-01-20 23:20:20 UTC
This has been merged into ocp and is in OCP v3.5.0.7 or newer.

Comment 4 Yanping Zhang 2017-01-22 05:50:53 UTC
Checked on OCP v3.5.0.7.
Create "Terminating" quota,"NotTerminating" quota,"BestEffort" quota, "NotBestEffort" quota on project, the description of each quota has been updated as below:
 "Terminating": "Affects pods that have an active deadline. These pods usually include builds, deployers, and jobs.",
 "NotTerminating": "Affects pods that do not have an active deadline. These pods usually include your applications.",
 "BestEffort": "Affects pods that do not have resource limits set. These pods have a best effort quality of service.",
 "NotBestEffort": "Affects pods that have at least one resource limit set. These pods do not have a best effort quality of service."

The bug has been fixed, so move it to Verified.

Comment 6 errata-xmlrpc 2017-04-12 19:05:29 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, 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-2017:0884


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