Red Hat Bugzilla – Bug 1308521
Purge taskomatic records during upgrade
Last modified: 2016-04-28 07:16:02 EDT
Description of problem:
In BZ#1305157 we've added additional functionality to Sat 5.6 added in BZ#1215671 to 5.7. However as these are added later in 5.7 lifecycle and not in plain 5.7 there are few problems during 5.6 -> 5.7 upgrade.
1. There are additional taskomatic related records in the DB but no Java classes -> taskomatic will be failing on plain 5.7 with ClassNotFound exceptions.
2. Applying erratum which fixed BZ#1215671 can cause troubles as there are no INSERT WHERE NOT EXISTS statements in https://github.com/spacewalkproject/spacewalk/blob/master/schema/spacewalk/upgrade/spacewalk-schema-2.3-to-spacewalk-schema-2.4/002-auto-errata-update-task.sql
Version-Release number of selected component (if applicable):
5.6 -> 5.7 upgrade
Steps to Reproduce:
1. Apply fix for BZ#1305157 on 5.6
2. Upgrade to 5.7
Upgraded DB from 5.6 to 5.7 contains taskomatic records related to (at plain 5.7) non-existing Java classes. During upgrade process either duplicate records are created or schema-upgrade process fails with unique constraint violation (haven't tested this one).
There should be no evidence of taskomatic classes added by BZ#1305157 on upgraded 5.7 instance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.