Description of problem: wmic module required for collection of running processes from Windows VMs is not available on the appliance. Version-Release number of selected component (if applicable): 5.3 How reproducible: Always Steps to Reproduce: 1. Try running wmic command from terminal on appliance. Additional info: The wmic command is utilized by lib/util/win32/miq-wmi-linux.rb to make wmi calls to Windows systems from linux.
GregM, What format is the wmic module packaged/delivered? Is it a ruby gem? Is this it: https://rubygems.org/gems/ruby-wmi Is this a regression or something new? Is it in the upstream? Thanks! JoeV
ruby-wmi only supports running on Windows. wmic was a binary that use to ship with the appliance that is required for collecting running processes from Windows machines. Hopefully these links are useful: http://pkgs.org/download/wmi http://rpmfind.net/linux/rpm2html/search.php?query=wmic http://www.iggyt.org/doku.php?id=wiki:infrastructure_tools:wmi:wmi-linux_client-wmic
John, We need to build it into an RPM You know how the source for the gem RPMs is the gem and the source for the CFME RPM is a tar file? Tell the source for wmic will likely be a tar file with all the bits in it, similar to the CFME souce tar file. Comment 3 describes how to install it on Linux I think what has to be done is to install wmic someplace and build it into a tar file. Then use that tar file to create an RPM. JoeV
Greg: I found that we have wmi-1.3.14-2.el6eso already in brew: https://brewweb.devel.redhat.com/packageinfo?packageID=34257 The site http://pkgs.org/download/wmi shows a version of wmi-1.3.14-3 So it appears we can use the one in brew,..do you agree? I'd just have to talkj with rel-eng about getting either the repo, or get the rpm cfme-5.4 tagged.
Yes, I agree the brew version is fine for our needs.
wmi-1.3.14 wmi-1.3.14-1.el6cf has been built into the cfme-5.4-rhel-6-candidate tag. The cfme.spec has been updated for the next cfme-5.4 build.
Verified that wmi-1.3.14-1.el6cf is now available on CFME appliances. Verified in 5.4.0.0.19.20150410165622_ad23806.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1100.html