[Bug 845886] New: vmware appliance: zypper dup from 12.3 disables the virtual ethernet port
https://bugzilla.novell.com/show_bug.cgi?id=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c0 Summary: vmware appliance: zypper dup from 12.3 disables the virtual ethernet port Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: VMWare OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Greg.Freemyer@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.69 Safari/537.36 I have vmware appliance I use for testing. With 12.3 I had the virtual ethernet port configured such that ifconfig showed it. I then run "ifconfig eth0 up; dhclient eth0" and it is on the lan. When I ran zypper dup it complained that a couple "VMware Client-side Extensions" was in conflict, so I told zypper dup to uninstall them. After zypper dup was complete, I rebooted and attempted get on the lan, but ifconfig did not show a network adapter. I had to go into yast and configure it. Then it showed up in ifconfig, even though it had a new name. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c1 lynn wilson <lynn@steve-ss.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lynn@steve-ss.com --- Comment #1 from lynn wilson <lynn@steve-ss.com> 2013-10-16 22:02:18 UTC --- Same here, but on a vBox 12.3 to 13.1 guest upgrade using the NET iso: http://lists.opensuse.org/opensuse-factory/2013-10/msg00382.html Maybe just with virtual interfaces? 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=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c2 Andrey Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #2 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-10-17 02:50:47 UTC --- (In reply to comment #0)
When I ran zypper dup it complained that a couple "VMware Client-side Extensions" was in conflict, so I told zypper dup to uninstall them.
If you had extensions installed, your ethernet most likely was provided by vmnet driver. After you removed extensions, this driver disappeared. Did you reboot after removing extensions? Did you still have ethernet interface at this point? -- 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=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c3 --- Comment #3 from Greg Freemyer <Greg.Freemyer@gmail.com> 2013-10-16 23:37:58 EDT --- You may be right about the cause. I did not reboot after removing the extensions but before running zypper dup. In fact I removed the extensions as part of running zypper dup. I don't have a 3rd VM handy to do another test upgrade with. If you think it worth while I could take the time to setup another 12.3 VM and test your theory. What I did do several hours ago was repeat the process and document exactly what I did the second time: - Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup - choose uninstall vmware client packages (2 different interactions with zypper) - let it run to completion - reboot - login as root - ifconfig The only interface displayed is lo (loopback). I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. -- 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=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c4 John Beranek <john@redux.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |john@redux.org.uk --- Comment #4 from John Beranek <john@redux.org.uk> 2013-10-17 22:38:56 UTC --- I find this bug report odd, as the kernel includes VMware's vmxnet3 driver, and has done for quite some time: /lib/modules/3.11.2-1.g420e19b-desktop/kernel/drivers/net/vmxnet3/vmxnet3.ko -- 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=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c5 --- Comment #5 from Greg Freemyer <Greg.Freemyer@gmail.com> 2013-10-18 16:41:28 EDT --- Still no joy. === I created a brand new openSUSE 12.3 instance from an appliance I built on susestudio months ago. It was built as a VMware appliance. It did not have the 3rd party VMware client packages installed. I confirmed ifconfig showed 2 interfaces (lo and eth0). "ifconfig eth0 up" brought the virtual NIC up and "dhclient eth0" got it an IP and I could communicate with the world. I adjusted the repos to be 13.1 repos (OSS and updates) and did a "zypper dup". No packages had to be uninstalled because no 3rd party packages were present. At the conclusion I rebooted to vmware. After reboot ifconfig only show lo (loopback). === Obviously the workaround of launching yast and configuring the virtual NIC is straight forward, but it is not something our users should have to do. -- 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=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c6 --- Comment #6 from John Beranek <john@redux.org.uk> 2013-10-18 20:47:26 UTC --- Can you determine which NIC driver is being used on the 12.3 VM before you do the upgrade? -- 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=845886 https://bugzilla.novell.com/show_bug.cgi?id=845886#c7 Greg Freemyer <Greg.Freemyer@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |INVALID --- Comment #7 from Greg Freemyer <Greg.Freemyer@gmail.com> 2013-10-18 17:25:00 EDT --- Hold the horses, problem resolved! === your question prompted me to take a better look. I recreated a virgin 12.3 VMware machine. I have the VM in my appliance configured to start with the network down. That's why I automatically run "ifconfig eth0 up; dhclient eth0" This time immediately after first boot / login, I ran "ifconfig" and it only shows "lo". Because I know the interface is named eth0 in 12.3 I can run "ifconfig eth0 up; dhclient eth0" and it works. I now realize I need to run "ifconfig -a" as my first command to get the name of the down interfaces. In 13.1 my interface is named enp0s17. And I can run "ifconfig enp0s17 up; dhclient enp017" and all is well. So the "bug" is that I assumed "ifconfig" would show me all interfaces, even ones that were down. Instead I needed to be running "ifconfig -a". === Thanks for asking enough questions that I figured it out. -- 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