Bugzilla – Bug 171488
DNS/DHCP/Hostname configuration in Yast hangs
Last modified: 2007-10-03 19:22:44 UTC
Hi, I reviewed the bug list finding two related bugs: 137762, 120332. As suggested in 137762 I added the ### BEGIN INFO # # Modified_by: NetworkManager # Process: /usr/bin/NetworkManager # Process_id: 26213 # ### END INFO header hoping for a change... What happens: if I go into Yast -> Network Card -> Hostname and DNS there is always a "0.100" entered in the second nameserver domain. If I remove it (otherwise yast complains) and save it and press next for yast to accept the settings for the network card, some scripts run until "Write hostname and DNS configuration". There it hangs. I also had the case, where the complete network card settings were suddenly destroyed and the network was down (which is why I hesitate to play more around). After that I configured the network by hand. This is on a 64 bit x86. SuSE is 10.0 but I applied the most recdent upgrades except liby2util 2.12.9-0.4, which I reversed, because the problem seems to have appeared after this upgrade. Adding the header to /etc/resolv.conf or not (as reported in bug 137762) does not change the situation. /etc/resolv.conf is neither read nor written. if I make changes within yast's "Hostname and DNS configuration". My liby2util version is 2.12.8-2. Here follows my support.txt info. REMARK: I attached the support.txt to the end but then got the message that the report was longer than 65xxx char. So I just left the hardware stuff of it. If you need the full support.txt, please let me know how to submit it. Thanks in advance. Markus Buttons: --net ##Y2support-/tmp/siga/siga.txt: <pre> 1. Hardware ------------------------------------------------------------------------------- 1.1 procinfo - /usr/bin/procinfo Linux 2.6.13-15.8-smp (geeko@buildhost) (gcc 4.0.2 20050901) #1 4CPU [ehv-server-2] Memory: Total Used Free Shared Buffers Mem: 6137588 2666956 3470632 0 466544 Swap: 6345632 0 6345632 Bootup: Tue Apr 25 20:05:07 2006 Load average: 1.24 1.20 1.19 2/213 14424 user : 4d 8:20:17.89 16.5% page in : 1419959 disk 1: 96201r 1147113w nice : 0:01:38.55 0.0% page out: 9372244 disk 2: 1795r 0w system: 0:36:41.97 0.1% page act: 619804 IOwait: 0:58:36.84 0.1% page dea: 0 hw irq: 0:00:04.82 0.0% page flt: 89742626 sw irq: 0:01:06.24 0.0% swap in : 0 idle : 21d 20:43:36.81 83.2% swap out: 0 uptime: 6d 13:41:25.18 context : 237296806 irq 0: 141920036 timer irq169: 0 uhci_hcd:usb1 irq 1: 8101 i8042 irq177: 1243318 ioc0 irq 4: 6 irq185: 30 ioc1 irq 5: 2 irq193: 0 uhci_hcd:usb2 irq 6: 3 irq201: 0 uhci_hcd:usb3 irq 8: 1893 rtc irq209: 19 ehci_hcd:usb4 irq 9: 0 acpi irq217: 239076 eth0 irq 12: 882 i8042 irq225: 4799166 eth1 irq 14: 2183 ide0 ------------------------------------------------------------------------------- 1.2 cmdline - /proc/cmdline root=/dev/sda6 vga=0x317 selinux=0 resume=/dev/sda11 splash=silent -------------------------------------------------------------------------------
The bugs you are referring to are for 10.1, you stated 10.0 as product. For which version are you reporting this? NetworkManager is generally not supported in 10.0 as it got introduced with 10.1. If you are reporting this for 10.1, correct the Product field and attach /var/log/YaST2 as tarball.
Well, I downloaded the iso images for SuSE 10.0 and did all upgrades till recently about 30.04. From the upgrades I reverted the Yast ones and the OpenOffice ones, which cause trouble. So I believe that I am on 10.0, but after all upgrades, how far am I from 10.1? The NetworkManager does not exist on my system, however, if I include the comment in the /etc/resolve.conf, then Yast reacts in that way, that a popup window appears telling that a temporary resolve.conf exists or so. Does that help? Regards Markus Remark: After clicking on links in this original message (New) getting back etc (I honestly dont remember) I suddenly had this additional Comments field and the Related People Group Security Assignee: E-mail List <bnc-team-screening@forge.provo.novell.com> Reporter: Markus Kohler <markus.kohler@verum.com> QA Contact: Klaus Kaempf <kkaempf@novell.com> Info Provider: Markus Kohler <markus.kohler@verum.com> Section that was missing when I viewed the bug after logging in.
I suppuse this is an update problem with NetworkManager - reassigning to the Gnome team.
Raising to major because it seems to break config and be a regression. Robert, I'm no longer seeing that resolv.conf header being written out for one thing.
Martin: I stopped writing out the header for another reason -- which, unfortunately, I cannot recall. I'll add it back.
Although, rereading the initial poster, I don't see why the NM changes is the issue. The poster is saying YaST is _hanging_!
Created attachment 81832 [details] resolv.conf as written out by newly-submitted NM
I submitted an NM package to autobuild that writes out resolv.conf as above, with the modify_resolvconf-style header. I believe this is a sufficient fix from the NM side. I am skeptical about the rest of the problem, though, since the poster seems to be describing several YaST issues. Reassigning to Martin for verification (feel free to close, dude).
Markus, kernel 2.6.13 and liby2util 2.12.x mean that you are still using 10.0. Note that applying online updates just fixes critical bugs in the product, it does not add new features as a complete system upgrade does. However, as you are using NM, I believe you have a strange mixture of packages from two product releases. Can you attach the output of "rpm -qa --last"? Also attach the yast logs: http://en.opensuse.org/Bug_Reporting_FAQ#YaST Note that attaching a file is done using a link near the bottom of the page. The error in comment 0 seems to have been caused by just pasting the text to the comment box.
*** Bug 137762 has been marked as a duplicate of this bug. ***
Hi Martin, Summary: - I installed NOTHING else than SuSE 10.0 free evaluation version (that incl. acroread etc.) - I did all upgrades until the most recent ones - I reverted the upgrades of the OpenOffice and liby2util because yast and Openoffice caused me headaches after the most recent upgrade. - in the case of OpenOffice it helped to step back, with Yast it did NOT - I have no strange mixture: I checked and I DO NOT HAVE NetworkManager (used locate which is updated daily) - I only saw comments/other bugs reported in news groups which is why I tried to include this header in /etc/resolv.conf. - Whatever I do: put the header in resolv.conf, have old or new liby2util installed: Yast hangs definitely when I use Yast to configure Network Services -> DNS and Hostname - also whatever I do: in the second domain search field appears always 0.100 which seams to be the remains of 192.168.0.100 (the DNS host). MEANING: I am regularly legally and honestly on 10.0 with latest upgrades. I don't request new features but report a bug. I attach the requeste files in a later step (after commit) Regards, Markus
Created attachment 82190 [details] Yast logs
Created attachment 82191 [details] rpm -qa -last output
Created attachment 82193 [details] locate NetworkManager call output -> no NetworkManager installed
Reassigning to the new co-maintainer of yast2-network.
second service...
As this is no longer reproducible and 10.0 support will end soon, definitely not something for online update