Bug 1333122
| Summary: | quota events for compute resource failures are duplicated due to unstable map ordering | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jessica Forrester <jforrest> | ||||
| Component: | Node | Assignee: | Derek Carr <decarr> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Qingyu Wang <nobody+qwang> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.2.0 | CC: | adellape, aos-bugs, decarr, dma, eparis, jokerman, mmccomas, qixuan.wang | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.2.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Events related to quota failures for compute resources produced multiple identical events. This was due to errors describing why a request was rejected having a variable ordering of responses for the same root cause. This bug fix sorts resources in quota errors, and as a result duplicate events are avoided.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-06-27 15:06:30 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: |
|
||||||
Fixed upstream in https://github.com/kubernetes/kubernetes/pull/25161 Tested on Origin(openshift v1.3.0-alpha.1-140-g2b6d744, kubernetes v1.3.0-alpha.1-331-g0522e63, etcd 2.3.0) and OSE(OpenShift Master:v3.2.1.1-1-g33fa4ea,
Kubernetes Master:v1.2.0-36-g4a3f9c5 ), the bug has been fixed, thanks.
Following is the result:
# oc get event -n qwang1
FIRSTSEEN LASTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE
8m 8m 1 database-1-deploy Pod Normal Scheduled {default-scheduler } Successfully assigned database-1-deploy to openshift-146.lab.sjc.redhat.com
8m 8m 1 database-1-deploy Pod spec.containers{deployment} Normal Pulling {kubelet openshift-146.lab.sjc.redhat.com} pulling image "brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ose-deployer:v3.2.1.1"
8m 8m 1 database-1-deploy Pod spec.containers{deployment} Normal Pulled {kubelet openshift-146.lab.sjc.redhat.com} Successfully pulled image "brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ose-deployer:v3.2.1.1"
8m 8m 1 database-1-deploy Pod spec.containers{deployment} Normal Created {kubelet openshift-146.lab.sjc.redhat.com} Created container with docker id ea4aaf7dd17e
8m 8m 1 database-1-deploy Pod spec.containers{deployment} Normal Started {kubelet openshift-146.lab.sjc.redhat.com} Started container with docker id ea4aaf7dd17e
8m 6m 8 database-1 ReplicationController Warning FailedCreate {replication-controller } Error creating: pods "database-1-" is forbidden: Exceeded quota: myquota, requested: cpu=4,memory=4Gi, used: cpu=400m,memory=512Mi, limited: cpu=2,memory=1Gi
6m 4m 4 database-1 ReplicationController Warning FailedCreate {replication-controller } Error creating: pods "database-1-" is forbidden: Exceeded quota: myquota, requested: cpu=4,memory=4Gi, used: cpu=0,memory=0, limited: cpu=2,memory=1Gi
8m 8m 1 database DeploymentConfig Normal DeploymentCreated {deploymentconfig-controller } Created new deployment "database-1" for version 1
8m 8m 1 database DeploymentConfig Warning FailedUpdate {deployment-controller } Cannot update deployment qwang1/database-1 status to Pending: replicationcontrollers "database-1" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
4m 4m 1 database DeploymentConfig Normal DeploymentScaled {deploymentconfig-controller } Scaled deployment "database-1" from 1 to 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/RHBA-2016:1343 |
Created attachment 1153952 [details] duplicate events Events related to quota failures for compute resources end up with multiple identical events, the problem is the message is not stable because maps are not stable. see screenshot attached