[Spacewalk-list] Unique constraint violation after upgrade

[Jan Pazdziora]

On Thu, Mar 08, 2012 at 03:33:46PM +0100, Pierre Casenove wrote:
> Hello,
> I just upgraded Spacewalk server to version 1.7, and synced the
> spacewalk client repo.
> here is the error message I get in file rhn_taskomatic_daemon.log:
> 
> INFO   | jvm 1    | 2012/03/08 14:21:00 | 2012-03-08 14:21:00,226
> [Thread-92] ERROR com.redhat.rhn.common.db.datasource.CachedStatement
> - Error while processing cached statement sql: insert into
> rhnPackageRepodata (package_id)
> INFO   | jvm 1    | 2012/03/08 14:21:00 |               (select
> cp.package_id as id from rhnChannelPackage cp left join
> rhnPackageRepoData rd on cp.package_id = rd.package_id
> INFO   | jvm 1    | 2012/03/08 14:21:00 |                       where
> cp.channel_id = ?
> INFO   | jvm 1    | 2012/03/08 14:21:00 |                         and
> rd.package_id is null)
> INFO   | jvm 1    | 2012/03/08 14:21:00 |
> com.redhat.rhn.common.db.WrappedSQLException: ERROR: duplicate key
> value violates unique constraint "rhnpackagerepodata_pk"

I cannot find a reason why taskomatic would run into this constraint
violation.

After you've synced the repo, did you by any chance manually trigger
the repodata regeneration? What is the repodata status of the channel
now -- did it finish alright eventually?

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat