search

craigwatson / puppet-vmwaretools

Puppet module for non-OSP VMware Tools Installation
http://forge.puppetlabs.com/CraigWatson1987/vmwaretools
Apache License 2.0
27 stars 40 forks source link

Causes network interfaces to drop and not come back up in Ubuntu #6

Closed Aethylred closed 11 years ago

Aethylred commented 11 years ago

I'm using Ubuntu 12.04 serve x64 with the master branch of puppet-vmwaretools and trying to install VMware tools 9.0.0-782409 with vSphere 5.1. Puppet version is 2.7.18 and puppetmaster is running under passenger.

The module runs and removes the open vmware tools, and installs correctly, but disconnects the network interfaces and they will not restart until the virtual machine is rebooted.

craigwatson commented 11 years ago

Thanks for the report, can you confirm that the interfaces are actually being refreshed? The installation may take a while on Ubuntu as the drivers are compiled from source for the running kernel - your issue could be a long-running compilation - how many vCPUs and how much vRAM is allocated to the VM?

Are you running Puppet over SSH or the vSphere Client console?

Aethylred commented 11 years ago

Each VM has 2 vCPU and 2GB RAM. I've repeated this twice from cloned VMS with the OSS tools installed. They also have VMXNET3 interfaces.

I'm not sure if the interfaces have been refreshed, I'll have to check. When I do restart them they come up with green ticks for VMware Tools in vCenter.

Both times I initiated puppet agent --test via ssh.

craigwatson commented 11 years ago

Thanks - just to confirm, does your Puppet run via SSH complete successfully, or does it hang?

Could you test using the vSphere Client console?

Aethylred commented 11 years ago

SSH just hangs until your client times out the connection for the host not responding.

I've run it in the console now. It does not complete. After /Stage[main]/Vmwaretools::Install::Exec/Exec[remove_vmwaretools_working_dir] is triggered the network interface is down and the next thing that puppet tries to do that requires network connection fails with the error:

Network is unreachable - connect(2)

Also of interest is that running ifup eth0 responds with:

Cannot find device "eth0"
Failed to bring up eth0.

Everything comes right after a restart.

I've not repeated this on a VM that doesn't have the open vmware tools installed.

Aethylred commented 11 years ago

I've just verified that something silly might be required. like the MAC address changing, or that udev doesn't need to regenerate /etc/udev/rules.d/70-persistent-net.rules

craigwatson commented 11 years ago

Thanks!

Could you Ctrl+C the Puppet process immediately after the /Stage[main]/Vmwaretools::Install::Exec/Exec[remove_vmwaretools_working_dir] step and run /etc/init.d/networking restart and then check connectivity?

Could you also confirm what kernel version and type (i.e. server/desktop/virtual) you're using?

It's strange that I haven't seen this before, I'll run up a test VM in the next few days to try and debug this further.

Aethylred commented 11 years ago

I've certainly tried to restart the networking usually with service networking restart and restart networking (regular init.d incantation, and new upstart incantation) and I probably tried calling it directly as well, but it's unlikely I'll manage to abort the Puppet update before it crashes out due to a lack of network. It fails fast after that point.

All versions have been Ubuntu 12.10 Server x64 with uname -r giving:

3.5.0-26-generic
craigwatson commented 11 years ago

Hi, sorry for the delay. Can you please try installing the tools from archive manually (i.e. untarring the archive and running vmware-config-tools.pl -d) and post the output?

I'll have a test VM up shortly, but if you could try using your cloned VMs, it would be appreciated.

Aethylred commented 11 years ago

Hi Craig,

do you mean vmware-install.pl -d which is the install command?

The installer found the following conflicting packages installed on the system and will now remove them:

open-vm-dkms
open-vm-tools

(Reading database ... 64271 files and directories currently installed.)
Removing open-vm-dkms ...

-------- Uninstall Beginning --------
Module:  open-vm-tools
Version: 2012.05.21
Kernel:  3.5.0-17-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vmblock.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-17-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmci.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-17-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmhgfs.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-17-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmsync.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-17-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmxnet.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-17-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vsock.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-17-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod.....

DKMS: uninstall completed.

-------- Uninstall Beginning --------
Module:  open-vm-tools
Version: 2012.05.21
Kernel:  3.5.0-26-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vmblock.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-26-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmci.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-26-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmhgfs.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-26-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmsync.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-26-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vmxnet.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-26-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vsock.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.5.0-26-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod......

DKMS: uninstall completed.

------------------------------
Deleting module version: 2012.05.21
completely from the DKMS tree.
------------------------------
Done.
Removing open-vm-tools ...
 * Stopping open-vm guest daemon vmtoolsd
   ...done.
 * Removing open-vm-tools modules
FATAL: Module vmhgfs not found.
FATAL: Module vmsync not found.
FATAL: Module vmblock not found.
FATAL: Module vmxnet not found.
   ...done.
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Creating a new VMware Tools installer database using the tar4 format.

Installing VMware Tools.

The file /etc/vmware-tools/statechange.subr that this program was about to 
install already exists. Overwrite? [yes] 

The file /etc/vmware-tools/poweron-vm-default that this program was about to 
install already exists. Overwrite? [yes] 

The file /etc/vmware-tools/suspend-vm-default that this program was about to 
install already exists. Overwrite? [yes] 

The file /etc/vmware-tools/resume-vm-default that this program was about to 
install already exists. Overwrite? [yes] 

The file /etc/vmware-tools/poweroff-vm-default that this program was about to 
install already exists. Overwrite? [yes] 

The file /etc/vmware-tools/scripts/vmware/network that this program was about 
to install already exists. Overwrite? [yes] 

In which directory do you want to install the binary files? 
[/usr/bin] 

What is the directory that contains the init directories (rc0.d/ to rc6.d/)? 
[/etc] 

What is the directory that contains the init scripts? 
[/etc/init.d] 

In which directory do you want to install the daemon files? 
[/usr/sbin] 

In which directory do you want to install the library files? 
[/usr/lib/vmware-tools] 

The path "/usr/lib/vmware-tools" does not exist currently. This program is 
going to create it, including needed parent directories. Is this what you want?
[yes] 

In which directory do you want to install the documentation files? 
[/usr/share/doc/vmware-tools] 

The path "/usr/share/doc/vmware-tools" does not exist currently. This program 
is going to create it, including needed parent directories. Is this what you 
want? [yes] 

The installation of VMware Tools 9.0.0 build-782409 for Linux completed 
successfully. You can decide to remove this software from your system at any 
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

Before running VMware Tools for the first time, you need to configure it by 
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want 
this program to invoke the command for you now? [yes] 

The file /etc/pam.d/vmtoolsd that this program was about to install already 
exists.  Overwrite? [yes] 

Initializing...

Making sure services for VMware Tools are stopped.

The VMware FileSystem Sync Driver (vmsync) allows external third-party backup 
software that is integrated with vSphere to create backups of the virtual 
machine. Do you wish to enable this feature? [no] 

Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-RW0N8C/vmci-only'
/usr/bin/make -C /lib/modules/3.5.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.5.0-26-generic'
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-RW0N8C/vmci-only/driverLog.o
  LD [M]  /tmp/modconfig-RW0N8C/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-RW0N8C/vmci-only/vmci.mod.o
  LD [M]  /tmp/modconfig-RW0N8C/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.5.0-26-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-RW0N8C/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-RW0N8C/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-RW0N8C/vmci-only'

Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-77lVPG/vmci-only'
/usr/bin/make -C /lib/modules/3.5.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.5.0-26-generic'
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-77lVPG/vmci-only/driverLog.o
  LD [M]  /tmp/modconfig-77lVPG/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-77lVPG/vmci-only/vmci.mod.o
  LD [M]  /tmp/modconfig-77lVPG/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.5.0-26-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-77lVPG/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-77lVPG/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-77lVPG/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-77lVPG/vsock-only'
/usr/bin/make -C /lib/modules/3.5.0-26-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.5.0-26-generic'
  CC [M]  /tmp/modconfig-77lVPG/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/modconfig-77lVPG/vsock-only/linux/notify.o
  CC [M]  /tmp/modconfig-77lVPG/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/modconfig-77lVPG/vsock-only/linux/stats.o
  CC [M]  /tmp/modconfig-77lVPG/vsock-only/linux/util.o
  CC [M]  /tmp/modconfig-77lVPG/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/modconfig-77lVPG/vsock-only/driverLog.o
  LD [M]  /tmp/modconfig-77lVPG/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-77lVPG/vsock-only/vsock.mod.o
  LD [M]  /tmp/modconfig-77lVPG/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.5.0-26-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-77lVPG/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-77lVPG/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-77lVPG/vsock-only'

The module vmxnet3 has already been installed on this system by another 
installer or package and will not be modified by this installer.  Use the flag 
--clobber-kernel-modules=vmxnet3 to override.

The module pvscsi has already been installed on this system by another 
installer or package and will not be modified by this installer.  Use the flag 
--clobber-kernel-modules=pvscsi to override.

The module vmmemctl has already been installed on this system by another 
installer or package and will not be modified by this installer.  Use the flag 
--clobber-kernel-modules=vmmemctl to override.

The VMware Host-Guest Filesystem allows for shared folders between the host OS 
and the guest OS in a Fusion or Workstation virtual environment.  Do you wish 
to enable this feature? [no] 

The vmxnet driver is no longer supported on kernels 3.3 and greater. Please 
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)

The vmblock enables dragging or copying files between host and guest in a 
Fusion or Workstation virtual environment.  Do you wish to enable this feature?
[no] 

!!! [EXPERIMENTAL] !!!
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present.  By selecting yes,
you will be enabling this experimental feature.  You can always disable this
feature by re-running vmware-config-tools.pl.

Would you like to enable VMware automatic kernel modules?
[no] 

No X install found.

Creating a new initrd boot image for the kernel.
update-initramfs: Generating /boot/initrd.img-3.5.0-26-generic
initctl: Job failed to start
Unable to start services for VMware Tools

Execution aborted.

Updated with with console output.

craigwatson commented 11 years ago

Hi Aaron, I'm closing this issue for now due to inactivity, as I've made a lot of improvements and fixes to the module since you submitted the bug.

If you're still experiencing this bug, please feel free to comment, and can you also confirm if you're using the latest version of the module (currently 0.2.1).

Thanks, Craig