From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Description of problem: If clearpart is disabled in kickstart (which has to be done in two steps), and other options are then changed, the clearpart setting is restored and set to clear all partitions on all drives. This unexpected behaviour can have very bad consequences. To disable clearpart, I have to - Create kickstart - Set options, removing --all from clearpart line and update kickstart At this point, if I view the kickstart, I still see a clearpart line there, but with no options. I now edit advanced options to remove this by deselecting the checkbox next to clearpart and clicking the Update Kickstart button. Viewing the kickstart now shows no mention of clearpart. This is as expected and as required. However, if I now try to edit any of the options, I see that --all is back in the clearpart box. If I change any options on this page such as the root password or timezone, clearpart --all is back in the kickstart. To stop this, every time I make an edit to the options I have to remove --all from the clearpart box, then go into advanced options and deselect clearpart. Turning clearpart on with a default of --all seems to be the default behaviour every time I edit the options for a kickstart, regardless of whether or not it is being used in my kickstart. This is incredibly dangerous, as if this default is enabled. If instead of --all in the options box, we have a --drives xxx line, then our preference is not overwritten. However, due to bug 141644 we are not able to specify drives. Version-Release number of selected component (if applicable): 3.6.0 How reproducible: Always Steps to Reproduce: 1. Create kickstart in Satellite 2. Set options, removing --all from clearpart line and update kickstart 3. Edit advanced options, deselect clearpart and update kickstart At this point, the kickstart is as expected 4. Edit kickstart, select options 5. Change any option (not related to clearpart, e.g. root password) 6. Update kickstart Actual Results: The kickstart contains clearpart --all Expected Results: Kickstart should not contain any reference to clearpart Additional info: If you specify --drives xxx instead of --all as an argument, this is not overwritten. Only an absence of clearpart is overwritten. Because of bug 141644, I am unable to specify specific drives to the clearpart argument. It is reasonable to assume that data on some drives may need to be retained during a server reload, such as database partitions, home directories, etc. This unexpected behaviour can cause significate data loss.
fixed in rhn 370
This is working well now. Tested both cases on satellite, and the second case (since it's more interesting) on hosted.
mass move: PROD_READY --> CLOSED:CURRENTRELEASE