If you have not already, you would be wise to contact support, at
800-REDHAT1, or http://www.redhat.com/support, about this matter. You
will need your up-to-date entitlement information for this purpose.

sorry, this comment was intended to precede the above patch...
i had the same problem. apparently it has to do with the
'self.hardware' object not containing a field named 'class' for every
'hw' in the iteration (please excuse my lack of python-oriented
terminology -- i'd never seen python before this).
a *work-around* is as follows (see one-liner diff in attachment [well,
essentially one-liner, python doesn't diff well with all that
essential formatting...]), simply check to see whether the current
'hw' object in the loop iteration has a 'class' key.
this DOES NOT fix whatever is causing the self.hardware object to
contain entries without the 'class' field. for that, i unfortunately
have no suggestion or idea.

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note

You need to
log in
before you can comment on or make changes to this bug.