Bug 1108910
Summary: | gear deletion should delete quota entries | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
Component: | Containers | Assignee: | Brenton Leanhardt <bleanhar> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 2.1.0 | CC: | adellape, agrimm, anli, bmeng, jialiu, jokerman, libra-onpremise-devel, mmccomas |
Target Milestone: | --- | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-openshift-origin-node-1.23.9.15-1.el6op, rubygem-openshift-origin-container-selinux-0.8.1.3-1.el6op | Doc Type: | Bug Fix |
Doc Text: |
Due to a bug in the OpenShift Enterprise runtime, quota settings were not removed when gears were deleted. This bug fix updates the gear deletion logic to include quota configuration removal, and quota settings are now correctly removed when gears are deleted.
|
Story Points: | --- |
Clone Of: | 1103849 | Environment: | |
Last Closed: | 2014-08-26 13:52:27 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: | |||
Bug Depends On: | 1103849 | ||
Bug Blocks: |
Description
Brenton Leanhardt
2014-06-12 20:01:38 UTC
Upstream commit: commit b7a83174d85d2534b8c4223d04b1b198469e5b6e Author: Andy Grimm <agrimm> Date: Tue Jun 3 11:12:40 2014 -0400 Bug 1103849 - Remove quota for deleted gear by uid Verified and pass on puddle-2-1-2014-08-01 Before app delete: [root@node1 ~]# repquota -v / |grep 53df1b1416ae31a6e4000009 53df1b1416ae31a6e4000009 -- 1580 0 2048576 388 0 80000 After app delete: NO quota info are left. [root@node1 ~]# repquota -v / |grep 53df1b1416ae31a6e4000009 [root@node1 ~]# repquota -v / |grep 3263 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. http://rhn.redhat.com/errata/RHBA-2014-1095.html |