Bug 791335
| Summary: | Initscripts sys-unconfig does not populate ifcfg-ethX files | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Scott Croft <secroft> |
| Component: | system-config-network | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.7 | CC: | lmiksik, psklenar, rvokal |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The text user interface version of the system-config-network service, system-config-network-tui, did not store the network configuration correctly after the system was cleaned with the sys-unconfig command. As a consequence, no network configuration was stored in the /etc/sysconfig/network-scripts/ directory. With this update, even if no previous configuration exists, system-config-network-tui stores the configuration in that directory as expected. As a result, a network configured with system-config-network-tui works after executing sys-unconfig.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-16 00:17:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1049888 | ||
|
Description
Scott Croft
2012-02-16 19:27:12 UTC
In RHEL 5, network configuration at this step is done by system-config-network-tui. Reassigning. I can verify, that system-config-network-tui after sys-unconfig fill network-scripts (and /etc/resolv.conf) right. (IP, netmask, gateway, dns,.) Testing with: system-config-network-1.3.99.23-1.el5 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1195.html |