Bug 1026800
Summary: | installation repository availability not re-checked after networking changes | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Karel Volný <kvolny> |
Component: | anaconda | Assignee: | David Shea <dshea> |
Status: | CLOSED DUPLICATE | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-13 16:23:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Karel Volný
2013-11-05 13:15:01 UTC
I don't think that triggering a recheck on changes in the network is feasible, since there may be intermittent issues that we'd better to ignore, and there may be issues elsewhere in the network unrelated to the network configuration for which we'd also want to recheck. A better solution would be to recheck uninitialized repositories any time the source spoke is entered and the user hits "Done", regardless of whether the settings were changed. Such a change is handled in bug 1030997 *** This bug has been marked as a duplicate of bug 1030997 *** |