Ticket #446 (closed defect: wontfix)

Opened 16 years ago

Last modified 11 years ago

RPMng doesn't announce its failures

Reported by: lueningh Owned by: desai
Priority: major Milestone: Bcfg2 0.9.4 Release
Component: bcfg2-client Version:
Keywords: Cc:


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/", line 5, in ?
    import Bcfg2.Client.Tools, rpmtools, os.path, rpm, ConfigParser
  File "/usr/lib64/python2.4/site-packages/Bcfg2/Client/Tools/", line 23, in ?
    import rpm, optparse, pwd, grp
ImportError: No module named rpm


Change History

comment:1 Changed 16 years ago by desai

  • Status changed from new to closed
  • Resolution set to wontfix
  • Milestone set to Bcfg2 0.9.4 Release

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...

comment:2 Changed 11 years ago by

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.