Bug 1374250

Summary: Cannot input custom URL for network install
Product: [Fedora] Fedora Reporter: Seshadri <sesh19>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 26CC: anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:34:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
result of button click none

Description Seshadri 2016-09-08 10:34:10 UTC
Created attachment 1198987 [details]
result of button click

Description of problem:
Cannot enter custom URL for network install. Ideally "Installation Source" should be configurable even though automatic selection ("Closest mirror") works.

Version-Release number of selected component (if applicable):
Not sure of component version. Using Rawhide-20160828.n.0 netinst image.

How reproducible:
Every time

Steps to Reproduce:
1. Boot with netinst image mentioned above.
2. Proceed with install.
3. Click through till "INSTALLATION SUMMARY" screen.
4. Click "Installation Source", then "Closest mirror".

Actual results:
1. On clicking "Closest mirror", button gets activated but doesn't display a drop-down (which is what it seems to be). 
2. The text box next to it remains grayed out (cannot accept input). 
3. A very thin horizontal line shows up at the top left corner about 4 cm.

Expected results:
Drop down with more options? Or at least one to specify a custom URL for network install.

Additional info:
Closest mirror does work.

Comment 1 Seshadri 2016-09-08 14:00:43 UTC
VM running on VirtualBox Version 5.0.20 r106931.

Comment 2 Fedora End Of Life 2017-02-28 10:13:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 3 Fedora End Of Life 2018-05-03 09:06:28 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2018-05-29 11:34:40 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.