Bug 597205
| Summary: | OPTIONS ifcfg parameter is corrupted after mn-c-e run in stage 2. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Radek Vykydal <rvykydal> | ||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 6.0 | CC: | borgan, jstodola, maier | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | anaconda-13.21.51-1 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-11-10 19:46:15 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: | 597206 | ||||||||
| Attachments: |
|
||||||||
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. (In reply to comment #0) > Created an attachment (id=417576) [details] > Patch with fix. OK, thanks Radek. So this would fix again the same regression that was already fixed with 8549a36d4b22171992951a272b82f0aa14234dc4 on 2009-10-05. > Steps to Reproduce: > 1. Run install with OPTIONS= ifcfg file parameter containing '=' in value > (at the moment, it is in any device activated in stage 1, but this behavior is > not correct and may change) Right, that's a bug in loader/net.c:writeEnabledNetInfo as mentioned here https://www.redhat.com/archives/anaconda-devel-list/2010-May/msg00713.html. osa_layer2 is initialized with 1 and never reset to zero, so it always writes out 'OPTIONS="layer2=1"' on all platforms. This has to change definitely. (In reply to comment #2) > osa_layer2 is initialized with 1 and never reset to zero, so it always writes > out 'OPTIONS="layer2=1"' on all platforms. This has to change definitely. BTW, that's been "fixed" upstream in commit ef100b6baa5324fb5f5060b21f804bddc16ebead and this anaconda-14.3-1, see bug 577005. Updates image with patch: http://rvykydal.fedorapeople.org/updates.597205.img Created attachment 418205 [details] ifcfg.log I tried anaconda-13.21.48-1.el6 and the updates image from comment 4, but after clicking on "Configure Network" button, eth0 lost its IPv4 address: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 4096 qdisc pfifo_fast state UNKNO WN qlen 1000 link/ether 02:00:00:00:00:07 brd ff:ff:ff:ff:ff:ff inet 10.16.105.196/21 brd 10.16.111.255 scope global eth0 inet6 fe80::ff:fe00:7/64 scope link valid_lft forever preferred_lft forever Ýanaconda root@rtt5 /¨# nm-dispatcher.action: nm_dispatcher_action: Invalid conn ection: '(null)' / 'connection setting not found' invalid: 1 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 4096 qdisc pfifo_fast state UNKNO WN qlen 1000 link/ether 02:00:00:00:00:07 brd ff:ff:ff:ff:ff:ff inet6 fe80::ff:fe00:7/64 scope link valid_lft forever preferred_lft forever All ifcfg files including the original one written by writeEnabledNetInfo of loader are missing SUBCHANNELS and NETTYPE among other (s390 specific) things. This explains why the network does not come up on boot in bug 597206. Jan, is BOOTPROTO=dhcp intentional? Does the installation work, if you don't run nm-c-e? I think it won't work either, since this most probably depends on fixes for bug 595388 and bug 595382 which are closely related and concern loader's readNetInfo and writeEnabledNetInfo and therefore the initial ifcfg file anaconda starts with. BOOTPROTO=dhcp is not intentional. With updates img from comment 4 and not running nm-c-e, ifcfg-eth0 contains: DEVICE=eth0 HWADDR=00:11:25:BE:2C:57 ONBOOT=yes BOOTPROTO=dhcp OPTIONS="layer2=1" TYPE=Ethernet DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 (and eth0 doesn't bring up during boot) This should be fixed in anaconda-13.21.51-1. After running nm-c-e in stage 2 and finishing the installation, OPTIONS parameter contains: OPTIONS="layer2=1 portno=0" Tested on build RHEL6.0-20100707.4 with anaconda-13.21.56-1.el6, system booted with eth0 up. Moving to VERIFIED. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |
Created attachment 417576 [details] Patch with fix. Description of problem: If networkmanager-configuration-editor is run in stage 2, value ifcfg parameter OPTIONS is corrupted - everything after first '=' character is lost, for example OPTIONS="layer2=1" becomes OPTIONS="layer2" Version-Release number of selected component (if applicable): anaconda-13.21.45-1 (snapshot 5) How reproducible: Always Steps to Reproduce: 1. Run install with OPTIONS= ifcfg file parameter containing '=' in value (at the moment, it is in any device activated in stage 1, but this behavior is not correct and may change) 2. In stage 2, run nm-c-e with [Configure Network] on hostname screen, then leave it with [Cancel] 3. See /etc/sysconfig/network-scripts/ifcfg-ethX or /tmp/ifcfg.log Actual results: OPTIONS parameter is corrupted Expected results: OPTIONS parameter is intact by running nm-c-e Additional info: The bug concerns all values containing '=' character. Patch attached.