Red Hat Bugzilla – Bug 16307
Bug in installation scripts
Last modified: 2008-05-01 11:37:57 EDT
If you fill up the install dialog panels, and get to th epoint that you are
ready to install, and then decide to <BACK> thru some of the panels
maybe to check some settings, or reset a setting, and then <NEXT>
thru the panels, there are 2 issues:
1) certain panels clear the settings as you re-enter them ("next"ing into
This is inconvenient. It would be nice if they remembered the old
Specifically, the disk druid panel. if you set your mount points, and
back up to the fdisk, when you next into disk druid, you have to
the mount points.
2) certain panels appear to remember the settings, but in actual fact, the
settings are not passed onto the installation, and once you boot the
system, you find, way too late, that the settings are dropped.
network setting (ip settings)
to see what I am talking about, set these to non-default values, next
forward to the
"about to install page", then <PREV> back top the disk druid page, then
forward. You will see your timezone selected, and your IP info as you
then do the install. then boot up. wrong timezone (i think it is the
and some or all of your IP settings are not set.
I don't think it is so uncommon to BACK thru the install panel, for example
settings. it can also happen for legit reasons. for example, install tells
you that "/" is
to small, to you "BACK" to disk druid, reassign the "/" partition to a
larger one, or whatever,
and <NEXT> thru to the install. The install will have bad timezone, and teh
not be properly setup.
Please verify this Brent.
Addressing issue number one, the installer will remember your changes in certain
situations. For example, imagine that I enter the mount point screen, set my
mount points, and click "Next" to go to the next screen. Now, if I click "Back
two or three times and eventually click "Next" a number of times so that I
re-enter the mount point screen, my changes will be remembered. This is because
clicking "Next" at the mount point screen causes the changes to be remembered,
but if you click "Back" first, the changes will not be remembered.
This is not the behavior that the user expects. This bug will be added to our
list for the next release.
Issue number two is related but different. I will look at it soon.
I was not able to reproduce bug related to second issue. In fact, I tested this
and it seems to be working correctly. As for the first issue, the changes take
effect when 'Next' is pressed. The reason that the changes do not take effect
on clicking 'Back' is because 'Back' is meant to provide the user a way to back
out of the screen without any committing to any changes. I'm resolving as not a