Paul Robert Marino wrote:
% for any one whos interested here is the workaround i found
% I had to do several alterations to the database
%
% "
% spaceschema=# select id,channel_arch_id from rhnChannel where label
% ='sci-linux-6_2';
% id | channel_arch_id
% -----+-----------------
% 109 | 513
% (1 row)
% spaceschema=# insert into rhnDistChannelMap
% (os,release,channel_arch_id,channel_id) VALUES
% ('sl-release','6.2','513','109');
% spaceschema=# alter table rhnserverhistory drop constraint
% "vn_rhnserverhistory_details";
% "
%
% oh by the way if any one is wondering the reason why im dropping the
% constraint is if you don't it just breaks again latter with this error
Well, I really wonder why you're dropping it. Do you know what's its
purpose? Are you sure about consequences of your change?
Be prepared to random unexpected errors in future. Moreover you
might not be able to upgrade schema in the future.
I strongly discourage anyone from doing such modifications.
% because of an on the bug the workaround brought to light.
%
% "
% ERROR: new row for relation "rhnserverhistory" violates check
% constraint "vn_rhnserverhistory_details"
% STATEMENT:
% insert into rhnServerHistory
% (id,
% server_id,
% summary,
% details)
% values
% (sequence_nextval('rhn_event_id_seq'),
% 1000010018,
% E'Updated system release from 6.2 to 6.2',
% E'')
% "
Regards,
--
Michael Mráka
Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
