Bug 1357475
| Summary: | Pod QoS Tier are different between OpenShift 3.2 and 3.3 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Weihua Meng <wmeng> |
| Component: | Node | Assignee: | Derek Carr <decarr> |
| Status: | CLOSED ERRATA | QA Contact: | Weihua Meng <wmeng> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.1 | CC: | agoldste, aos-bugs, jokerman, mmccomas, tdawson |
| Target Milestone: | --- | ||
| Target Release: | 3.2.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously pods that had a resource request of 0 and specified limits the pod was classified as BestEffort when it should have been Burstable for that resource. We have corrected this bug so that they're now correctly classified as Burstable.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-12 17:35:45 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: | |||
|
Description
Weihua Meng
2016-07-18 10:07:01 UTC
This looks like a bug in OpenShift 3.2, will investigate. Kubernetes 1.2 has a bug for how it evaluated QoS when a request=0 and a limit was specified. * In 1.2, a resource was best effort if its request is unspecified or 0. * The proper behavior is to say a resource is best effort if it has no limit specified, and its request is unspecified or 0. Fix for edge case in Origin PR: https://github.com/openshift/ose/pull/308 The behavior described in OpenShift 3.3.0.6 is correct moving forward. The pull request has not been merged. I'm marking this back to assigned. Please move it to Modified when the pull request has been merged. I'm also moving the target to 3.3.0, per the conversation in the pull request. This is a code fix for 3.2.x. Correcting version & target release. Merged into 3.2.x stream. not in latest 3.2 puddle. waiting for new puddle. Fixed.
openshift v3.2.1.15
kubernetes v1.2.0-36-g4a3f9c5
etcd 2.2.5
Now the Qos tier in OpenShift 3.2.1 is consistent with OpenShift 3.3.
for OpenShift 3.2.1.15
Scopes: BestEffort
* Matches all pods that have best effort quality of service.
Resource Used Hard
-------- ---- ----
pods 0 2
QoS Tier:
cpu: Burstable
memory: Burstable
Limits:
cpu: 1
memory: 1Gi
Requests:
memory: 0
cpu: 0
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/RHSA-2016:1853 |