Basically, if monitoring is not enabled during the installation of a satellite, enabling monitoring will result in an environment not suitable for monitoring (known problems: some needed and assumed data (like the default 'Panic Destination' contact method) is missing from the database). An example traceback caused by attempting to create a general, check nothing probe attached. To replicate: Enable monitoring with a satellite not installed with monitoring. Create a system probe, which will generate 500.
Created attachment 117352 [details] Create Probe Traceback
moving to the right tracking bug.
mass assign QA contact for rhn410 bugs
The real solution to this bug is to properly warn the user when they enable monitoring that they need to run the enable-monitoring.pl script.
I tested this under new satellite 510 and this scenario work there.
Closing as WONTFIX. If anyone wants this bug to be reopened feel free to do so!