RPMng doesn't announce its failures

[lueningh]

One of my machines wasn't playing nicely with RPMng: I would specify it as a driver, and Bcfg would silently drop it from its list. It turns out I didn't have rpm-python installed, as proved by the traceback below. We should check for this and announce the failure.

alcf-tb3:~ # bcfg2 -q -v -n -D Action,POSIX,Chkconfig,RPMng
Loaded tool drivers:
 Action     Chkconfig  POSIX

>>> import Bcfg2.Client.Tools.RPMng
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib64/python2.4/site-packages/Bcfg2/Client/Tools/RPMng.py", line 5, in ?
    import Bcfg2.Client.Tools, rpmtools, os.path, rpm, ConfigParser
  File "/usr/lib64/python2.4/site-packages/Bcfg2/Client/Tools/rpmtools.py", line 23, in ?
    import rpm, optparse, pwd, grp
ImportError: No module named rpm
>>> 

[desai]

Mike and I have determined that this is the right behavior; if we add an error message it will be printed out on all platforms without rpm...

[https://www.google.com/accounts/o8/id?id=AItOawnEusV609cT6ichWkkp_Whof8y86hcPhFk]

​what is malware