Description of problem: On builds(/console/project/test/browse/builds/<bc>) and deployments(/console/project/test/browse/deployments/<dc>) page, clicking on Delete button didn't take effect.Although alert message displayed, buildconfigs and deploymentconfigs still shown on page Version-Release number of selected component (if applicable): devenv-rhel7_2838 oc v1.1-262-g429d52e kubernetes v1.1.0-origin-1107-g4c8e6f4 How reproducible: Always Steps to Reproduce: 1.Create image stream 2.Create application with ruby image and source code 3.Delete buildconfig and deploymentconfig Actual results: 3. buildconfig and deploymentconfig still shown on page, see attachments Expected results: 3.specific buildconfig and deploymentconfig should be deleted Additional info: imagestreams,services,pods could be deleted successfully
Created attachment 1100707 [details] BuildConfig-CannotDelete
Created attachment 1100708 [details] DeploymentConfig-CannotDelete
I think this is working as intended, although admittedly is a little confusing. We show the deleted build config (with a warning) so you can see old builds associated with it. The builds themselves aren't deleted, just the config. You should see the same behavior if you delete the build config (with --cascade=false) on the command line. Jessica, can you confirm? We have a trello card to support cascading deletes, which the CLI defaults to. Right now, that's not supported in the UI.
Yes this is working. The buildconfig object has been deleted, we still show you the build exists and the buildconfig that created it no longer exists so that you know to clean up the old builds. As sam says this is because we don't support cascading delete yet in web console.