Activity log for bug #1153055

Date Who What changed Old value New value Message
2013-03-09 21:10:25 Henry Nash bug added bug
2013-03-09 21:11:03 Henry Nash description When we delete a domain, we don't either check if there are resources that are linked to it. Depending on the database this will either leave the DB in a somewhat inconsistent state...or fail with an integrity check error. As a wider questions is what SHOULD happen if someone tries to delete a domain? Logically, we should delete all projects, users and groups that are owned by it - although it would be unfortunate if someone did it in error! I suggest we should ONLY allow a domain to be deleted if it is first disabled, as way of preventing inadvertent deletion - and then we should really delete all the entities owned by that domain. When we delete a domain, we don't check if there are resources that are owned by it. Depending on the database this will either leave the DB in a somewhat inconsistent state...or fail with an integrity check error. As a wider questions is what SHOULD happen if someone tries to delete a domain? Logically, we should delete all projects, users and groups that are owned by it - although it would be unfortunate if someone did it in error! I suggest we should ONLY allow a domain to be deleted if it is first disabled, as way of preventing inadvertent deletion - and then we should really delete all the entities owned by that domain.
2013-03-09 21:11:39 Henry Nash description When we delete a domain, we don't check if there are resources that are owned by it. Depending on the database this will either leave the DB in a somewhat inconsistent state...or fail with an integrity check error. As a wider questions is what SHOULD happen if someone tries to delete a domain? Logically, we should delete all projects, users and groups that are owned by it - although it would be unfortunate if someone did it in error! I suggest we should ONLY allow a domain to be deleted if it is first disabled, as way of preventing inadvertent deletion - and then we should really delete all the entities owned by that domain. When we delete a domain, we don't check if there are resources that are owned by it. Depending on the database this will either leave the DB in a somewhat inconsistent state...or fail with an integrity check error. A wider question is what SHOULD happen if someone tries to delete a domain? Logically, we should delete all projects, users and groups that are owned by it - although it would be unfortunate if someone did that in error! I suggest we should ONLY allow a domain to be deleted if it is first disabled, as way of preventing inadvertent deletion - and then we should really delete all the entities owned by that domain.
2013-03-14 16:57:40 Dolph Mathews marked as duplicate 1097995