[Bug 731645] New: Reconfiguring Network Port on vmware ESXi Virtual Box does not work
https://bugzilla.novell.com/show_bug.cgi?id=731645 https://bugzilla.novell.com/show_bug.cgi?id=731645#c0 Summary: Reconfiguring Network Port on vmware ESXi Virtual Box does not work Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse@wizonet.ch QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6 ( .NET CLR 3.5.30729; .NET4.0E) New installed openSuSE 12.1 base system (server textbased / Runlevel 3) in ESXi 4.1 virtual box. After installation, the network port eth0 should be reconfigured from DHCP to statical ip address. This seems to work as espected, but after closing YaST, the network port is gone - only lo port available. rcnetwork restart or reboot does not help, only a manual "ifup eth0" brings up again the port. Possible solution/workaround: Do not reconfigure eth0 with edit. 1. Delete eth0 2. Close/Reopen YaST 3. Add eth0 with statical settings After these three steps, eth0 is still up an running. Reproducible: Always Steps to Reproduce: 1. Install openSuSE with "automated settings" -> eth0 will set up as DHCP port 2. Try to reconfigure eth0 with traditional method (ifup) and "edit" port 3. Close YaST 4. eth0 is gone Actual Results: Deleting eth0, close/open YaST and add eth0 can be used as workaround. Expected Results: editing a network port should not break its functionality Severity "Normal" because there is a workaround for me. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=731645 https://bugzilla.novell.com/show_bug.cgi?id=731645#c1 kk zhang <kkzhang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |kkzhang@novell.com Resolution| |NORESPONSE --- Comment #1 from kk zhang <kkzhang@novell.com> 2012-03-08 14:04:16 UTC --- Long time no response.So closed.Feel free to reopen it.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.
https://bugzilla.novell.com/show_bug.cgi?id=731645 https://bugzilla.novell.com/show_bug.cgi?id=731645#c2 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |suse-beta@cboltz.de Resolution|NORESPONSE | AssignedTo|bnc-team-screening@forge.pr |mvidner@suse.com |ovo.novell.com | --- Comment #2 from Christian Boltz <suse-beta@cboltz.de> 2012-03-14 00:32:18 CET --- Nobody reassigning the bug to the package maintainer is no reason to close a bug as "noresponse". Reopening (and assigning to the package maintainer). Martin, can you please attach the y2logs? -- 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.
participants (1)
-
bugzilla_noreply@novell.com