|
Bugzilla – Full Text Bug Listing |
| Summary: | No network in state2 during update | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Andreas Jaeger <aj> |
| Component: | Update Problems | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | varkoly |
| Version: | Alpha 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
first screenshot to show problem
screenshot showing network setup YaST log files |
||
|
Description
Andreas Jaeger
2007-04-13 14:38:57 UTC
Created attachment 131037 [details]
first screenshot to show problem
Created attachment 131038 [details]
screenshot showing network setup
Created attachment 131039 [details]
YaST log files
After "rcnetwork start" I can continue the installation. Reproduced with same reason (also in vmware) But don't find anything wrong. dhcpcd is supposed to obtain and write correct resolv.conf Christian, do you have any idea where the problem could be? remove sysconfig maintainer from needinfo added dhcpcd maintainer Peter, could you check why dhcpcd doesn't write resolv.conf first time and second time do? Michal, sorry for the late reply. Please check how dhcpcd is called which options. Is there another dhcpcd running? Maybe dhcpcd is running as 'secondary' client. Normally you should see a message from modify_resolvconf in the system log. Does it only happen when updating? I don't know that from yast log - dhcpcd starts from initscript before YaST Andreas - could you attach /var/log/message from firstboot time? I only noticed it during update, all other installs worked fine. I don't have the file anymore. NOte: This error was easy to reproduce... Problem localized /network/src/installation/inst_netsetup.ycp on line 43: if (netconfig == "dhcp") netconfig = "static"; // FIXME So in this case system obtains ip/gw address without resolv.conf (and any others settings) Peter, is there any way to say dhcpcd force to use it's own cash instead new request? Only usable I see in documentation parameter -s for sending DHCP_INFORM message ... I have solution for this described here: http://lists.opensuse.org/opensuse-networking/2007-05/msg00001.html No, there is no way to force dhcpcd to use the cache. It wouldn't comply with the protocol anyway. Unless there is no network connection (no DHCP server cannot be contacted); then it would be allowed. Using configuration statically which was once obtained by DHCP is not good. It is a SuSE-ism, that some people around here think that it could make sense... It never makes sense for interface address, arguably it can be used to fixate NIS servers and such, which is the same for statically as well as for dynamically configured hosts. For second stage same network configuration will be used as in first stage (rcnetwork restart) The patch is created and tested - all kinds of network/non network types of installation. Now we test autoyast and then fix can be submitted Code is submitted in subversion: http://lists.opensuse.org/yast-devel/2007-05/msg00025.html but it needs to fix in dhcpcd: https://bugzilla.novell.com/show_bug.cgi?id=278551 fixed for beta5+ |