[Bug 728473] New: installation of RC2 network failure under VirtualBox 4.1.6 on Windows7
https://bugzilla.novell.com/show_bug.cgi?id=728473 https://bugzilla.novell.com/show_bug.cgi?id=728473#c0 Summary: installation of RC2 network failure under VirtualBox 4.1.6 on Windows7 Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: howard.bryan.webb@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=460588) --> (http://bugzilla.novell.com/attachment.cgi?id=460588) yast2 files should show why network is unavailable User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 This is related to (but not same as) Bug#725912 -RC1 doesn't find eth0 on VirtBox N.B.Did not encounter Bug#726099 in either RC1 or RC2 -VirtBox kdeinit4 boot crash Installing opensuse 12.1 RC2 Hardware Alienware x86-64 VirtualBox 4.1.6 (latest version, bug fix rls only 1 week old) While in Stage 2 install... During Configuration->Network::Saving Network Configuration->Run SuSEconfig... Popup occurs: YaST2 No network running OK Click OK to acknowledge Next screen: Click Yes, test Internet connection Following screen: Test status: Downloading latest release notes At this point it hangs, it was necessary to click the Abort button. System completed installation. Later, when it came up, there was no network card (eth0), only loopback dev Using yast2->Network Devices->Network Settings, it claimed that Network Manager had been selected, and yast2 could not do anything until the older ifupdown was the option for managing the network devices. Made the change. Could bring the network up successfully afterward. Reproducible: Always Steps to Reproduce: 1. Install 12.1 RC2 on VirtualBox 4.1.6 hosted by Windows7 2. After working thru unexpected network errors during install, run ifconfig to see that eth0 is not present 3. Run yast2->Network Devices to see it complain that NetworkManager was chosen as mgmt api, not ifup/down Actual Results: Observe during Stage 2->Configuring Network Devices->Run SuSEconfig step that network error popup occurs Observe hang occurs 2 screens later while "Downloading latest release notes" Observe that yast2->Network Devices claims that NetworkManager was chosen Expected Results: 1) No network error popup 2) If such a popup should occur, following default steps will not later cause a hang 3) When the system comes up, the network should be available saved 100K using bzip2 instead of gzip -- 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=728473 https://bugzilla.novell.com/show_bug.cgi?id=728473#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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=728473 https://bugzilla.novell.com/show_bug.cgi?id=728473#c Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@suse.com AssignedTo|yast2-maintainers@suse.de |mvidner@suse.com -- 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