Thanks for reporting this bug.
Was during an upgrade from lucid to precise?
Indeed a prerm existed for dhcp3-server in lucid, and not in precise. The prerm is likely failing because dhcp3-server is not running.
Can you check whether it is running (sudo service dhcp3-server status) and, if not, try to start it (sudo service dhcp3-server start)?
Thanks for reporting this bug.
Was during an upgrade from lucid to precise?
Indeed a prerm existed for dhcp3-server in lucid, and not in precise. The prerm is likely failing because dhcp3-server is not running.
Can you check whether it is running (sudo service dhcp3-server status) and, if not, try to start it (sudo service dhcp3-server start)?