Bug 1272124 - Change to network state should refresh software sources
Summary: Change to network state should refresh software sources
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 24
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-15 14:24 UTC by Pat Riehecky
Modified: 2017-03-06 19:30 UTC (History)
7 users (show)

Fixed In Version:
Clone Of: 1270354
Environment:
Last Closed: 2017-03-06 19:30:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pat Riehecky 2015-10-15 14:24:33 UTC
Whatever the RHEL7 resolution, Fedora also should feature this behavior.

+++ This bug was initially created as a clone of Bug #1270354 +++

Description of problem:
Currently it is possible to convince anaconda to attempt a network installation based on settings that are no longer in use.

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


How reproducible:100%


Steps to Reproduce:
1.boot off of netboot.iso
2.configure all settings for a valid connection to the RHEL yum repo
3.reconfigure the network to an address with no connectivity
4.Begin installation

Actual results:
Anaconda formats the drives and then, after a long wait, produces an error that the repo timed out

Expected results:
When the network settings are changed, access to the installation sources is validated to ensure it still works.

Additional info:

https://github.com/rhinstaller/anaconda/pull/411

Seems to resolve my use cases.

Comment 1 Jan Kurik 2016-02-24 13:50:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase


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