Bug 976034 - Boot option inst.repo=url is not used
Summary: Boot option inst.repo=url is not used
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-19 19:11 UTC by A.J. Werkman
Modified: 2015-02-17 15:38 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:38:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Anaconda.log (5.68 KB, text/plain)
2013-06-20 11:59 UTC, A.J. Werkman
no flags Details
Packaging.log (26.00 KB, text/plain)
2013-06-20 12:00 UTC, A.J. Werkman
no flags Details
ifcfg.log (567 bytes, text/plain)
2013-06-20 12:00 UTC, A.J. Werkman
no flags Details
Syslog (155.27 KB, text/plain)
2013-06-21 06:10 UTC, A.J. Werkman
no flags Details

Description A.J. Werkman 2013-06-19 19:11:53 UTC
Description of problem:
When booting with the inst.repo option pointing to an url, this url is not used to acces repo tree.

Version-Release number of selected component (if applicable):
19-TC5

How reproducible:
Most of the time. It looks like this is a timing problem

Steps to Reproduce:
1. Boot with inst.repo= url
2. Accept your faith
3. See that installtion source gives an error

Actual results:
URL is not used to install

Expected results:
URL should be used diectly to install from

Additional info:
When you wait a while before accepting your faith the url is used succesfully.
When an error occures, the packaging log show a curl error stating domain name not found. It looks like DNS is not yet functioning when curl tries the url. Retyping the same url in UI makes anaconda recognise the repo.

Comment 1 Samantha N. Bueno 2013-06-19 21:00:31 UTC
Please attach log files as individual text/plain attachments.

Comment 2 A.J. Werkman 2013-06-20 11:59:33 UTC
Created attachment 763446 [details]
Anaconda.log

Comment 3 A.J. Werkman 2013-06-20 12:00:10 UTC
Created attachment 763447 [details]
Packaging.log

Comment 4 A.J. Werkman 2013-06-20 12:00:50 UTC
Created attachment 763448 [details]
ifcfg.log

Comment 5 Brian Lane 2013-06-21 01:10:53 UTC
Please attach the other logs, especially syslog.

21:45:04,369 ERR anaconda: Geolocation refresh failed - no connectivity

Would seem to indicate that your network isn't up. If that's the case there really isn't much we can do.

Comment 6 A.J. Werkman 2013-06-21 06:10:08 UTC
Created attachment 763668 [details]
Syslog

Comment 7 A.J. Werkman 2013-06-21 06:12:58 UTC
(In reply to Brian C. Lane from comment #5)
> Please attach the other logs, especially syslog.
> 
> 21:45:04,369 ERR anaconda: Geolocation refresh failed - no connectivity
> 
> Would seem to indicate that your network isn't up. If that's the case there
> really isn't much we can do.

Well I think that my network isn't up _yet_. I assume because dhcp is still in the process of getting network information. Anaconda should not start network related tasks as long as dhcp isn't finished.

Comment 8 A.J. Werkman 2013-06-27 19:52:10 UTC
Looks like this error does not hit, when using an old/slow motherboard.
When using a new/fast motherboard, I see this error constantly

Comment 9 Fedora End Of Life 2015-01-09 18:28:58 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 10 Fedora End Of Life 2015-02-17 15:38:24 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


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