Description of problem: This is a placeholder to ensure that we find a solution (not necessarily through code change) for installation's "Upgrade" mode. Currently the mode is poorly documented and potentially misleading, as despite the implication of the name, it does not guarantee any preservation of customer customizations. Options include changing the name, improving documentation, making the feature less prominent, etc. Investigation is underway. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This will be included in version 11.1.2.114 of anaconda relative commit: e561fbbccb0c8a9a480506071145ba5a4c7a14c6
The idea here is to prevent upgrades between major versions (3->4 or 4->5). the only upgrades that will be minor version (5.1 -> 5.2, 5.2 -> 5.3....) The test should be strait forward.
The message that will appear in the log if the user makes a invalid kickstart upgrade will be : "A kickstart upgrade was attempted on a system with no valid upgrade candidates."
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0164.html