Kicking this back over to DF. 
One note, we still don't have the rhn_sat_cluster_recid_seq created to
replace the use of server_id as the recid in the rhn_sat_cluster
table. I chatted w/ pjones about what needs to be done to add it, and
this is what he said:

<nhansen> hey, so is creating a sequence for an id as easy as: create
sequence rhn_sat_cluster_recid_seq; ?
<nhansen> as in, is that all I have to add to the
tables/rhn_sat_cluster.sql file to create a new one?
<pjones> also need 2 more change files: one as rhn for "grant select
on rhn_sat_cluster_recid_seq to rhn_dml_r;", one as rhnuser for
"create or replace synonym rhn_sat_cluster_recid_seq for
rhn.rhn_sat_cluster_recid_seq;"
<nhansen> ok, so if I want to create rhn_sat_cluster_recid_seq, then I
need to add it in those 3 places?
<pjones> yes, those three places.

Creation logic is in place.

To QA:  Create a scout via the UI.  If you can create probes for the
scout you created, the creation logic worked.

By virtue of the fact that rhn_sat_cluster records are able to be
created via the web installer, this bug passes qa.