helm-service-cleanup
When a service example cinder gets deployed with helm charts and then removed, it leaves some leftovers like cinder database, some service/user records in keystone. All these leftovers prevents successful subsequent deployment of cinder. The root cause of this is the way how openstack components react on already existing objects. Instead of exiting without action of detection of this objects, they fail.
The same issue will be applied to all openstack processes which creating databases and running manage db process.
Blueprint information
- Status:
- Started
- Approver:
- Steven Dake
- Priority:
- Medium
- Drafter:
- Serguei Bezverkhi
- Direction:
- Approved
- Assignee:
- Serguei Bezverkhi
- Definition:
- Approved
- Series goal:
- Accepted for master
- Implementation:
-
Good progress
- Milestone target:
-
0.7.0
- Started by
- Serguei Bezverkhi
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
adding cleanup service for cinder
Gerrit topic: https:/
Addressed by: https:/
PS Adds keystone cleanup service
Addressed by: https:/
PS adds glance cleanuip service
Addressed by: https:/
PS adds neutron cleanup service
Addressed by: https:/
PS adds nova cleanup service
Work Items
Work items:
(unassigned): TODO
(unassigned)
(unassigned)
(sbezverk)keystone: DONE
(sbezverk)glance: DONE
(sbezverk)neutron: DONE
(sbezverk)nova: DONE
(sbezverk)cinder: DONE
(unassigned)
(unassigned)
(unassigned)heat: TODO
