Reverts for DB update tasks need to be corrected
Bug #1624166 reported by
Michael Johnson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Fix Released
|
High
|
Michael Johnson |
Bug Description
There are a some database update tasks that have TODO tasks to update the revert method. Currently they are just disabling the object on failure.
UpdateHealthMonInDB
UpdateMemberInDB
UpdatePoolInDB
UpdateL7PolicyInDB
UpdateL7RuleInDB
These are problematic objects as they do not have a provisioning status associated with them. Either they need a provisioning status added or parent objects need to be updated with the ERROR state and users need to be able to delete from that level down if they are in ERROR.
I think we should add provisioning status to these objects as they can be deleted via the API individually to resolve the failure.
Changed in octavia: | |
status: | New → Triaged |
To post a comment you must log in.
These do have provisioning status now. The revert methods just need to be updated to reflect that change.