Bug 326
Summary: | Missing file halts network startup procedure | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | verm |
Component: | linuxconf | Assignee: | David Lawrence <dkl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1998-12-09 19:44:39 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: |
Description
verm
1998-12-07 12:17:22 UTC
Yes, if the redhat-release file is missing, then the startup of linuxconf will indeed fail. Unable to replicate this file not getting created however. Need more information about the circumstances surrounding this error, i.e. which type of install are you doing, where in the install is the problem occurring? Linuxconf does indeed fail if the redhat-release file is missing, and this is as a result of the dependance of Linuxconf on the file. This is by design. Let us know if there are situations where the redhat-release file is not getting created. Commits pushed to master at https://github.com/openshift/openshift-sdn https://github.com/openshift/openshift-sdn/commit/445ac8cbfda7bc617869f0aa558dfd6e594945ca Fix debug.sh error when it is executed on containerized cluster (issue #326) https://github.com/openshift/openshift-sdn/commit/612ba30ace0fff169f1f12b8befb1458e8e5db2d Merge pull request #327 from harobed/issue326 Fix debug.sh error when it is executed on containerized cluster |