https://bugzilla.novell.com/show_bug.cgi?id=223408
Summary: Problem changing NIC during installation Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: holgi@novell.com QAContact: jsrain@novell.com
Two network cards (NIC) environment: If you do configure the 'wrong' NIC during installation and do recognize that when YaST tries to (unseccessfull) enable a connection to the internet - returning to the NIC configuration (with back buttons) deleting the config of the 'wrong' NIC and configuring the 'right' NIC causes a problem: it is not possible to connect to the internet afterwards. I thing YaST do not delete the config or the 'wrong' NIC and still tries to use just that NIC to enable the connection.
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #1 from holgi@novell.com 2006-11-23 01:22 MST ------- Created an attachment (id=106663) --> (https://bugzilla.novell.com/attachment.cgi?id=106663&action=view) YaST2.tgz
https://bugzilla.novell.com/show_bug.cgi?id=223408
kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
https://bugzilla.novell.com/show_bug.cgi?id=223408
kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |kmachalkova@novell.com
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #2 from kmachalkova@novell.com 2006-11-23 01:44 MST ------- Holgi, I really miss file named 'y2log' ;-) It's not included in attached tarball. It's better to use save_y2logs command to save all the logs, since it's difficult to tell in advance which part of it will be relevant.
Also, I don't fully understand what does term 'wrong' stand for. It has no cable connected ? It is not configured ? Moreover, there's always this 'Change Device' button in the internet test, where you can choose the right device if you think the wrong one is pre-selected. Doesn't that work for you ?
https://bugzilla.novell.com/show_bug.cgi?id=223408
holgi@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #106663|0 |1 is obsolete| |
------- Comment #3 from holgi@novell.com 2006-11-23 01:57 MST ------- Created an attachment (id=106668) --> (https://bugzilla.novell.com/attachment.cgi?id=106668&action=view) YaST2.tgz
I have no idea what went wrong when packing the logs. ;-)
'wrong' NIC means a not cable connected NIC which was automatically selected by YaST2 to be configured.
'right' NIC means the cable connected NIC but not selected and configured by YaST during installation. That's the reason why there was no selection of NIC available when entering the internet test.
After changing the config there was also no selection of NIC available when entering the internet test. YaST just displayed the 'right' NIC afterwards (but did not use?).
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #4 from kmachalkova@novell.com 2006-11-24 01:57 MST ------- Hmm, I see two NICs there: Intel (00:11:11:42:ef:b1) and Delta (00:00:1c:b5:9e:6b). The first one is pre-selected by YaST, yet it is not up and has no cable plugged in. The reason for that is that the Delta card is detected, but probably not proposed to be configured, or gets somehow lost for (so far) unknown reason. So the Intel NIC is used as a fallback. Does YaST see both cards (even in the installed system) ?
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #5 from holgi@novell.com 2006-11-24 02:21 MST ------- The problem is not the preselection but the user error configuring the wrong NIC (which was preselected - but that is not the problem) and that it does not work if user went back and changed the configuration
YaST do detect both cards - if you select the 2nd (by hand) and configure it (before you go further to the internet test) it works fine.
The problem is if you - do configure the wrong one (see above) - go to the internet test - return with the back buttons - delete the config of the wrong one - configure the right one - go again to the internet test
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #6 from kmachalkova@novell.com 2006-11-24 02:21 MST ------- OK, OK, I will read the whole log next time :-) YaST does see both cards. For the first time, it uses Intel card for connecting, but:
2006-11-23 08:31:18 <1> fornax(4476) [YCP] NetworkDevices.ycp:1249 eth-id-00:11:11:42:ef:b1 is down or disconnected
For the second attempt, Delta card is selected, but again:
2006-11-23 08:32:03 <1> fornax(4476) [YCP] NetworkDevices.ycp:1249 eth-id-00:00:1c:b5:9e:6b is down or disconnected
I wonder why ...
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #7 from kmachalkova@novell.com 2006-11-24 03:19 MST ------- Anyway:
kmachalkova@felix:~/YaST2/223408/internet-test> cat curl_1.log * getaddrinfo(3) failed for www.suse.com:80 * Couldn't resolve host 'www.suse.com' * Closing connection #0 curl: (6) Couldn't resolve host 'www.suse.com'
kmachalkova@felix:~/YaST2/223408/internet-test> cat resolv.conf domain suse.de
-> no nameserver entry in /etc/resolv.conf. Provided that the card was about to be configured via DHCP, it seems that dhclient did not modify /etc/resolv.conf properly
https://bugzilla.novell.com/show_bug.cgi?id=223408
kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |olh@novell.com
------- Comment #8 from kmachalkova@novell.com 2007-01-19 04:54 MST ------- *** Bug 236666 has been marked as a duplicate of this bug. ***
https://bugzilla.novell.com/show_bug.cgi?id=223408
kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kmachalkova@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |holgi@novell.com
------- Comment #9 from kmachalkova@novell.com 2007-02-13 03:04 MST ------- When YaST stores network configuration, it does 'rcnetwork reload' in case the network is already running (i.e. 'rcnetwork status' returns 0), and 'rcnetwork restart' otherwise. So in case DHCLIENT_MODIFY_RESOLV_CONF is set to yes, dhclient should modify resolv.conf on network reload, shouldn't it ?
Also, when I delete content of my resolv.conf manually, and call 'rcnetwork reload', it doesn't get restored back by dhclient. As Olaf mentioned in bug #236666, /etc/yp.conf is affected by this as well, it doesn't get created after network reload. Is this correct behaviour?
Christian, can you please comment ?
https://bugzilla.novell.com/show_bug.cgi?id=223408
kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Info Provider|holgi@novell.com |zoz@novell.com
------- Comment #10 from kmachalkova@novell.com 2007-02-13 03:07 MST ------- Wrong info provider ...
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #11 from kmachalkova@novell.com 2007-02-22 03:11 MST ------- Ping :-) (please see comment #9)
https://bugzilla.novell.com/show_bug.cgi?id=223408
zoz@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|zoz@novell.com |
------- Comment #12 from zoz@novell.com 2007-02-22 04:20 MST -------
So in case DHCLIENT_MODIFY_RESOLV_CONF is set to yes, dhclient should modify resolv.conf on network reload, shouldn't it ?
Yes, if: - /etc/sysconfig/network/config:MODIFY_RESOLV_CONF_DYNAMICALLY="yes" - something in the configuration for this interface has changed. 'network reload' does only take down/up interface for which has something canged in configuration (if '/sbin/ifprobe <iface>' returns != 0).
Also, when I delete content of my resolv.conf manually, and call 'rcnetwork reload', it doesn't get restored back by dhclient.
'network reload' tells you which interfaces it takes down and up. resolv.conf is not an configuration file for the interface, but is changed (sometimes) when the interface goes down/up. Therefore 'network reload' will not necessarily change resolv.conf. If you for example 'touch ifcfg-<the right one>' then it does.
Please ask again, if something is still unclear.
https://bugzilla.novell.com/show_bug.cgi?id=223408
kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |zoz@novell.com
------- Comment #13 from kmachalkova@novell.com 2007-02-26 08:51 MST -------
Yes, if:
- /etc/sysconfig/network/config:MODIFY_RESOLV_CONF_DYNAMICALLY="yes"
- something in the configuration for this interface has changed.
Therefore 'network reload' will not necessarily change resolv.conf. If you for example 'touch ifcfg-<the right one>' then it does.
Does 'something in the configuration has changed' cover also the cases when some ifcfg-* file has been deleted and/or new one has been created?
Because I guess what happened here was that: * user configured the device A (yast created ifcfg-A file) and tried internet test unsuccesfully * then he went back and deleted configuration of device A (yast deleted ifcfg-A) * finally he picked up and configured device B (yast created ifcfg-B)
and then 'rcnetwork reload' did not modify resolv.conf, even though both DHCLIENT_MODIFY_RESOLV_CONF and MODIFY_RESOLV_CONF_DYNAMICALLY have been set
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #14 from kmachalkova@novell.com 2007-02-26 09:50 MST ------- And actually, it did restart, not reload. Now I see it in the logs:
2006-11-23 08:31:28 <1> fornax(4476) [YCP] NetworkDevices.ycp:1030 Deleting file: eth-id-00:11:11:42:ef:b1 .. 2006-11-23 08:31:39 <1> fornax(4476) [YCP] NetworkDevices.ycp:609 Devs=$["eth":$["id-00:00:1c:b5:9e:6b": ... 2006-11-23 08:31:39 <1> fornax(4476) [YCP] NetworkDevices.ycp:618 Deleted=["eth-id-00:11:11:42:ef:b1"] 2006-11-23 08:31:39 <1> fornax(4476) [YCP] NetworkConfig.ycp:160 Writing configuration .. 2006-11-23 08:31:40 <1> fornax(4476) [YCP] NetworkService.ycp:73 rcnetwork restart
So forget comment #9 and #13, the problem is not within the 'rcnetwork reload', but 'rcnetwork restart'.
Later on (after checking status with ethtool): 2006-11-23 08:32:03 <1> fornax(4476) [YCP] NetworkDevices.ycp:1249 eth-id-00:00:1c:b5:9e:6b is down or disconnected
So the network restart 1)did not bring newly configured iface up 2)did not modify resolv.conf
Any clue, why might that be?
https://bugzilla.novell.com/show_bug.cgi?id=223408
holgi@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|zoz@novell.com |
------- Comment #15 from holgi@novell.com 2007-03-01 08:40 MST ------- With openSUSE Build 0052 is looks like the 'old' network config of a 'deleted' NIC will not be removed -> so there are two dhcp-clients running.
-> second NIC does not set DNS, Default Route ... -> still getting error message
https://bugzilla.novell.com/show_bug.cgi?id=223408
------- Comment #16 from holgi@novell.com 2007-03-01 08:42 MST ------- Created an attachment (id=121822) --> (https://bugzilla.novell.com/attachment.cgi?id=121822&action=view) y2logs.tgz
https://bugzilla.novell.com/show_bug.cgi?id=223408
User cthiel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=223408#c17
Christoph Thiel cthiel@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cthiel@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |holgi@novell.com
--- Comment #17 from Christoph Thiel cthiel@novell.com 2008-04-25 07:46:44 MST --- Holgi, please retest with openSUSE 11.0 and check if the problem still persists.
https://bugzilla.novell.com/show_bug.cgi?id=223408
User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=223408#c18
Andreas Jaeger aj@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|holgi@novell.com | Resolution| |NORESPONSE
--- Comment #18 from Andreas Jaeger aj@novell.com 2008-10-23 13:35:40 MDT --- The requested information has not been provided for over 4 weeks. The bug gets therefore closed as NORESPONSE.
Please reopen the bug if you can supply the requested information. I would appreciate if you could test openSUSE 11.1 Beta3 first and report whether the bug exists there as well.
-
bugzilla_noreply＠novell.com