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:
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