deployment-delete doesn't delete the corresponding config
Bug #1504384 reported by
Yingzhe Zeng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-heatclient |
Fix Committed
|
Medium
|
Yingzhe Zeng |
Bug Description
When use deployment-create command to create a software deployment,
heatclient will create a corresponding software config at first,
then create the deployment with the previously created config ID.
So there'll be a config and a deployment created in DB at once by deployment-create command.
But deployment-delete command only deletes the deployment, leave the config in DB.
This makes the software_config table in DB more and more bigger, unless use config-delete command manually.
Changed in python-heatclient: | |
assignee: | nobody → Yingzhe Zeng (zengyingzhe) |
Changed in python-heatclient: | |
milestone: | none → 1.3.0 |
To post a comment you must log in.
I think this is expected behaviour and not a bug . We create an empty config, if a config id is not provided when creating a deployment. This is only for usecases where user wants to pass input_values to config baked into images. Most of the cases user would specify a config already created.