Bug #1065

vmware snipped fails and causes unattended script to quit unexpectedly

Added by Corey Osman almost 2 years ago. Updated 6 months ago.

Status:Feedback Start:07/24/2011
Priority:Normal Due date:
Assigned to:- % Done:

0%
Category:-
Target version:-
Backlog:No Difficulity:
Votes: 0

Description

The vmware snippet does not run correctly and crashes the post install script.

#this never gets run as a result
/usr/bin/wget -q -O /dev/null --no-check-certificate http://192.168.1.1:3000/unattended/built

  1. Snippet file
    app/views/unattended/snippets/_vmware.erb
  1. This assumes that an rpm exists on some repo that would need to exist in the first place
    yum -t -y -e 0 install VMwareTools
  1. vmware usually provides a tar.gz file for the tools installer.
  1. Shouldn't we specify the full path to dmidecode?
    if dmidecode | grep -qi VMware

I think getting this info out of /proc might be easier or using facter to determine if the vm is virtual and what kind of vm it is.

History

Updated by Ohad Levy almost 2 years ago

  • Status changed from New to Feedback

I think we can probably remove vmware as a default snippet, and let everyone adjust for their needs?

this snippets were written almost two years ago, so a review is more then welcomed! :)

Updated by Benjamin Papillon 6 months ago

I'm also in favor of removing this snippet. There are others snippets for the admin to understand how snippets work.
The good way to install VMWare tools nowadays on a recent rhel platform is to use their rpm on their repositories.

Also available in: Atom PDF