Bug 1023725 - on any install image, when entering "Installation Source" spoke, selection is always the default, even if previously changed
on any install image, when entering "Installation Source" spoke, selection is...
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
20
All Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-27 08:02 EDT by Andre Robatino
Modified: 2014-01-16 15:30 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-16 15:30:08 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andre Robatino 2013-10-27 08:02:55 EDT
Description of problem:
On the install DVD, every time the "Installation Source" spoke is entered, the selected choice is "Auto-detected installation media" (the default), even if it was changed to either "ISO file" or "On the network" on a previous visit to the spoke. On the netinst, every time the "Installation Source" spoke is entered, the selected choice is "On the network" (the default), even if it was changed to "ISO file" on a previous visit to the spoke.

Version-Release number of selected component (if applicable):
anaconda-20.25.4-1 (20 Beta TC6)

How reproducible:
always

Steps to Reproduce:
1. Enter "Installation Source" spoke for the first time. At this point, the selected default choice is correct, for either the DVD or netinst.
2. Change the selected choice to one of the non-default values.
3. Exit and reenter the spoke.

Actual results:
The selected choice is changed back to the default.

Expected results:
Choice should be the same as when the spoke was last exited.

Additional info:
This is an old bug - the behavior was the same at least as far back as 19 Final.

Note You need to log in before you can comment on or make changes to this bug.