|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast -> Network -> Network Device does Not restart network after hostname change | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | David Rankin <drankinatty> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | andrew, dmacvicar |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2logs that you requested
package for 11.0 package for 10.3 |
||
Please provide y2logs. Created attachment 246919 [details]
y2logs that you requested
Hopefully, this will be a fairly clean y2logs file. The install is less than a week old so you should get the entire history in this file. Let me know if you need any other files. Thanks.
Reassign to yast2-maintainers. This problem is fixed in openSUSE11.1 (from Beta3 above) What is the plan for a fix for 11.0? Would you test fixed package? If yes, for what architecture? Michal,
Sure, I'm more than happy to test it. I can test it with 11.0 x86_64 or i586. I have boxes with both architectures. Same goes for 10.3, I have both X86_64 and i586. Just send me a link to the patch and let me know what source package I need to install and patch.
Ok, I can provide fixed packages for 10.3-i386 and 11.0-i386 It's quite easy, but I have a lot of work with 11.1/sles11 these days So if I'll not do it in 2 weeks, please ping me here Thanks,
I know your swamped. Just let me know when you have a fix to test and I'll be happy to test. Also, I did additional testing and this problem not only occurs with hostname change, but also with IP address change or when changing from fixed IP to dhcp. Thanks for your help.
*** Bug 437151 has been marked as a duplicate of this bug. *** Created attachment 278008 [details]
package for 11.0
package for 11.0
Created attachment 278032 [details]
package for 10.3
package for 10.3
Use on your own risk, there packages are no supported (just build with backported fix) |
Devs, I ran into an annoying bug with Yast -> Network Device _not_ restarting eth0 after making hostname changes to a network card. This was incredibly frustrating to have to run back across town to the office after the ssh connection went dead. Yast correctly created /etc/sysconfig/ifcfg-eth0, but then for some reason just did not restart the device. I get to the office and loopback is the only device shown with ifconfig. A simple ifup eth0 started the card just fine. This is a brand new install of 11.0 on an MSI K9N2 SLI Platinum board, AMD Phenom 9850, 4G of RAM, with 2 Seagate 500G drives in RAID 1 using the dreaded BIOS RAID that, in reality, works just fine. The card is activated on boot using traditional ifup and the card comes up fine. The install DVD media was verified and no errors occurred during the install. I have 4 other 11.0 installs and this is the only time I have seen this behavior. However, this is the only x86_64 fixed IP install I have that is working with traditional ifup. I have my x86_64 laptop, but that is using network manager. In the past, changing the hostname in Yast via ssh has been no problem at all. That is what yast's scripts do. When you hit 'Finish' yast stops the network to adjust the settings and then restarts the network with the new settings. The ssh connection isn't even dropped. The problem with Yast now is when you hit "Finish", yast stops the network to adjust the settings, then FAILS to execute the code that is supposed to restart the network. I could understand the case where there are errors in the changes and the card "won't" come back up, but that isn't what we are talking about here. We are talking perfect configuration so that all that needs to be done is for yast to issue the 'ifup' call -- but it just doesn't. I've been remote managing and configuring machines for 8 years, 5 of those with SuSE and this is a new feature with yast software management in 11.0. This problem has been confirmed on the opensuse-user list under the thread: "Yast -> Network Device - Not Re-Starting eth0 after changes". As always, if you need additional information, just let me know. Thanks.