Description of problem: There are various issues with allocatePartitions extended partition handling. 1) It will remove pre-existing non empty ext. partitions without scheduling a destroy action 2) Imagine the following: 1. empty disk, custom part. 2. users adds 4 partitons 3. user changes his mind goes back to 3 partitions Now we will have a create action for an extended partition from storage/partitioning.py:599, but no matching destroy action from when the user changed his mind -> boom
(In reply to comment #0) > Description of problem: > There are various issues with allocatePartitions extended partition handling. > > 1) It will remove pre-existing non empty ext. partitions without scheduling > a destroy action > I think we are removing pre-existing ext. partitions only explicitly with delete, being pre-existing, they are not handled implicitly in allocatePartitions. > 2) Imagine the following: > > 1. empty disk, custom part. > 2. users adds 4 partitons > 3. user changes his mind goes back to 3 partitions > > Now we will have a create action for an extended partition from > storage/partitioning.py:599, but no matching destroy action from when the user > changed his mind -> boom Yep, this is a catch.
(In reply to comment #1) > (In reply to comment #0) > > Description of problem: > > There are various issues with allocatePartitions extended partition handling. > > > > 1) It will remove pre-existing non empty ext. partitions without scheduling > > a destroy action > > > > I think we are removing pre-existing ext. partitions only explicitly with > delete, > being pre-existing, they are not handled implicitly in allocatePartitions. > My bad, that should have read: 1) It will remove a pre-existing empty ext. partitions without scheduling a destroy action Notice the change from "non empty" -> "empty"
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fixed in anaconda-12.16-1.