Bug 1203912
Summary: | network settings lost during install centos 6.6 | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | jw | ||||||||||||||||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||
Version: | 6.6 | CC: | jw, rvykydal | ||||||||||||||||||||||
Target Milestone: | rc | ||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||
Hardware: | Unspecified | ||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||
Last Closed: | 2017-12-06 11:48:02 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: | |||||||||||||||||||||||||
Attachments: |
|
Description
jw
2015-03-19 23:48:14 UTC
Please attach /tmp/*log (including /tmp/syslog) anaconda logs and the kickstart file. You can use scp or copy to local storage in shell in tty2 (Ctlr-Alt-F2) during installation. You can also find the log files on installed system: /var/log/anaconda.log /var/log/anaconda.syslog /var/log/anaconda.ifcfg.log I'm just putting together the log files but the one thing I found was if I opted for DHCP all worked well but if I opted to enter static IP configuration during install it failed. After a few tests I found that the config for eth0 always had DHCP set for BOOTPROTO. It looks like this is not set correctly if you use the asknetwork option appended to your isolinux.cfg boot command. I'm getting round this by running a post install script to change the BOOTPROTO to static but it means I can't opt for DHCP if I wanted to. Is the issue related to this bug report? https://bugzilla.redhat.com/show_bug.cgi?id=1187089 1187089 Created attachment 1005095 [details]
anaconda.ifcfg.log
Created attachment 1005096 [details]
anaconda.log
Created attachment 1005097 [details]
anaconda.syslog
Created attachment 1005098 [details]
anaconda-ks.cfg
Created attachment 1005099 [details]
kick start file
Created attachment 1005100 [details]
install.log
Created attachment 1005101 [details]
install.log.syslog
Created attachment 1005102 [details]
isolinux.cfg
Created attachment 1005103 [details]
ks.post.log
Created attachment 1005104 [details]
ks.post
If I set a second interface eth1 for example, The settings from the dialog box during install comes through as eth0 and the two sets of interface configurations are mixed. Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |