Comment 5 for bug 1454781

Actual issue was about wasting disk space by IBP target images from removed environment.

Average target images disk space consumption is expected to be slightly less than 1G per environment.

non removed yaml file is just a couple of Kbytes.

I could partially agree that it was not fixed properly, however i don't think that it's still high. The root cause is that nailgun doesn't use this yaml file as a source of all information about the images, it uses image data from release section of fixtures. But fuel-agent during the image build couldn't update fixtures with metadata about the images at nailgun side and in addition fuel-agent requires input data about the images to be built. So, what we get here is definitely the chicken and the egg problem.

Leaving this yaml file as is is completely safe as fuel-agent will recreate yaml file only during image building stage. Even if you drop nailgun db and start to deploy environments and under certain circumstances your env ID will interfere with the one which's already existing in yaml files, fuel-agent will silently rewrite it.

I'll file a separate bug about yaml removal targeted to 8.0 with meduim or even low priority.

This bug should be closed as it actually fixes the problem.