Bug 1328713 - In text mode,unable to continue the installation ,as long as you change the Installation source once
Summary: In text mode,unable to continue the installation ,as long as you change the I...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 06:55 UTC by lnie
Modified: 2017-08-08 14:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 14:16:39 UTC
Type: Bug


Attachments (Terms of Use)
screenshot (36.22 KB, image/png)
2016-04-20 06:55 UTC, lnie
no flags Details
screenshot2 (35.46 KB, image/png)
2016-04-20 06:56 UTC, lnie
no flags Details
anaconda.log (79.10 KB, text/plain)
2016-04-20 09:22 UTC, lnie
no flags Details
syslog (61.94 KB, text/plain)
2016-04-20 09:22 UTC, lnie
no flags Details
packaging.log (970 bytes, text/plain)
2016-04-20 09:23 UTC, lnie
no flags Details
storage.log (26.93 KB, text/plain)
2016-04-20 09:24 UTC, lnie
no flags Details
hawkey.log (1.62 KB, text/plain)
2016-04-20 09:25 UTC, lnie
no flags Details

Description lnie 2016-04-20 06:55:38 UTC
Created attachment 1148871 [details]
screenshot

Description of problem:
When I was doing an installation with f24-server-dvd.iso in text mode,I tried to change the installation to a nfs repo,but anaconda still said "source changed,please verify",two hours after I confirmed the Software selection.

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

f24-20160419-server-dvd-x86_64
How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2016-04-20 06:56:22 UTC
Created attachment 1148872 [details]
screenshot2

Comment 2 lnie 2016-04-20 09:22:25 UTC
Created attachment 1148944 [details]
anaconda.log

Comment 3 lnie 2016-04-20 09:22:55 UTC
Created attachment 1148945 [details]
syslog

Comment 4 lnie 2016-04-20 09:23:45 UTC
Created attachment 1148946 [details]
packaging.log

Comment 5 lnie 2016-04-20 09:24:10 UTC
Created attachment 1148947 [details]
storage.log

Comment 6 lnie 2016-04-20 09:25:00 UTC
Created attachment 1148948 [details]
hawkey.log

Comment 7 Fedora End Of Life 2017-07-25 20:34:44 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 8 Fedora End Of Life 2017-08-08 14:16:39 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.