New subject: [Bug 437182] Yast -> Network -> Network Device does Not restart network after hostname change

21 Oct 2008


      https://bugzilla.novell.com/show_bug.cgi?id=437182


           Summary: Yast -> Network -> Network Device does Not restart
                    network after hostname change
           Product: openSUSE 11.0
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: YaST2
        AssignedTo: bnc-team-screening@forge.provo.novell.com
        ReportedBy: drankinatty@suddenlinkmail.com
         QAContact: jsrain@novell.com
          Found By: ---


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.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug 437182] New: Yast -> Network -> Network Device does Not restart network after hostname change

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

tags

participants (1)