Bug 1337696
| Summary: | Remove PVC from webui doesn't remove it from DC | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OKD | Reporter: | Grant Shipley <gshipley> | ||||||||||||
| Component: | Deployments | Assignee: | Michail Kargakis <mkargaki> | ||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | zhou ying <yinzhou> | ||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 3.x | CC: | aos-bugs, dmace, mkargaki | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2016-05-27 14:10:15 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: |
|
||||||||||||||
Created attachment 1159674 [details]
image2
Created attachment 1159675 [details]
image3
Created attachment 1159676 [details]
image4
Created attachment 1159677 [details]
image5
This isn't a bug in Online. Origin doesn't re-write deploymentConfigs in this manner in response to a PVC delete operation. I'm not even sure that it should. This is probably better discussed in an RFE or GitHub issue for Origin. Reassigning to origin/deployments for now and cc'ing Michalis. I don't know that there's any precedent for any sort of API-level protection against deleting resources another resource "depends" on. The use case extends to other things, like secrets or image stream tags referenced by a trigger. I am not sure what to do with this. We cannot just rewrite a template because an object it depends on does not exist. As Dan said, this use extends on a bunch of other things. The correct thing to do at the moment is to edit your deployment config and remove the obsolete reference. I am going to close this bug and open a RFE on Github so it can get more eyes. Github issue: https://github.com/openshift/origin/issues/9059 |
Created attachment 1159673 [details] image Description of problem: After adding a volume and making a claim and then removing the claim from the webui the claim is not actually remove from the Deployment config. See attachments showing no claims but a mount point still. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Add volume 2. Get a claim 3. Remove storage from webui 4. See that it was removed (oc get pvc) 5. See that it wasn't removed from DeploymentConfig Actual results: Expected results: Additional info: