The biggest item which has yet to be addressed is a mechanism for ensuring that certain threads in the ManagmentClient class are guaranteed both to terminate, and to terminate in a particular order. Currently, the ManagementClient either hangs, or exits prematurely, since only one or the other of these guarantees can be made in the present version of the code. This bug is not deemed insurmountable or likely to consume a great deal of time, and is documented in detail in the JavaDocs available on the Management reports page in the cs519g1 website on babbage.
There are some bugs in the C library, some due to buggy Sun implementations of the Invocation API. The bugs can probably be worked around with a minimum of hassle, and are documented in the C code available from the cs519g1 CVS tree.
It should be noted that all bugs mentioned here really are minor in nature, and generally tend only to cause the program to hang when it ought to exit (that is, no functionality is missing - the flow of control simply needs to be made more robust).