Bug 771507

Summary: repo in kickstart file fails initially, but works after edit->OK
Product: [Fedora] Fedora Reporter: Ray Mikkelson <ray.mikkelson>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-18.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 02:49:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ray Mikkelson 2012-01-03 22:35:13 UTC
Description of problem:

I have the following lines in my kickstart file, specifying my local Fedora repositories:

repo --name="myserver - releases"  --baseurl=nfs::myserver.com:/vol0/FedoraMirror/releases/16/Everything/x86_64/os --cost=1
repo --name="myserver - updates"  --baseurl=nfs::myserver.com:/vol0/FedoraMirror/updates/16/x86_64 --cost=1

The installer complains that it cannot access the repository data, initially, and prompts the user what s/he wants to do...  I then select the EDIT button, make absolutely no edits, then immediately (no rush, but doing nothing else) select the OK button, and the 2nd try works like a charm (is successful).  I have no idea why the first try fails, when the 2nd try works OK with no changes.

Version-Release number of selected component (if applicable):
Fedora 16 x86_64

How reproducible:
Specify the repo command in the kickstart file and access via NFS


Steps to Reproduce:
1. Download the Fedora 16 x86_64 complete DVD ISO image
2. Burn the DVD
3. Boot the installation DVD, specify the kernel argument ks=nfs:PathToMyServer dhcp
  
Actual results:

Described above


Expected results:

The initial attempt to use the local repository should succeed and no prompt given on how to proceed.


Additional info:

This problem may, in some way, be related to Bug 770990.

Comment 1 Chris Lumens 2012-08-03 19:35:38 UTC
I believe this should be fixed in F18 Alpha.  Please test and let us know.

Comment 2 Fedora End Of Life 2013-01-17 01:32:30 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-14 02:49:16 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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