Bug 1015236 - Anaconda always request network dialog in cdrom custom install
Summary: Anaconda always request network dialog in cdrom custom install
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-03 17:29 UTC by Helio Chissini de Castro
Modified: 2015-02-17 17:29 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:29:44 UTC
Type: Bug


Attachments (Terms of Use)
Anaconda log (2.26 KB, text/x-log)
2013-10-03 17:29 UTC, Helio Chissini de Castro
no flags Details
Program log (21.13 KB, text/x-log)
2013-10-03 17:29 UTC, Helio Chissini de Castro
no flags Details
Kickstart file (5.46 KB, text/plain)
2013-10-03 17:32 UTC, Helio Chissini de Castro
no flags Details
Network dialog (187.30 KB, image/jpeg)
2013-10-03 17:33 UTC, Helio Chissini de Castro
no flags Details

Description Helio Chissini de Castro 2013-10-03 17:29:22 UTC
Created attachment 807192 [details]
Anaconda log

In a try to use an unattended install ( spin kickstart file ) in a machine with network and wifi cards, but not connected in any network produces anaconda dialog request to configure the network, even not been defined in the ks file.
Follows attached logs of anaconda until dialog appears, picture of dialog and teh used kickstart.

If bypass ( continue ) after the dalog, install occurs perfectly.

Thanks in advance

Comment 1 Helio Chissini de Castro 2013-10-03 17:29:55 UTC
Created attachment 807193 [details]
Program log

Comment 2 Helio Chissini de Castro 2013-10-03 17:32:11 UTC
Created attachment 807194 [details]
Kickstart file

Comment 3 Helio Chissini de Castro 2013-10-03 17:33:03 UTC
Created attachment 807195 [details]
Network dialog

Comment 4 Jerry Amundson 2014-06-03 14:30:07 UTC
Also see Bug 1061497

Comment 5 Fedora End Of Life 2015-01-09 20:06:23 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 6 Fedora End Of Life 2015-02-17 17:29:44 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.