Red Hat Bugzilla – Bug 800580
4.3 db upgrade failing if existing db does not have RHQ_DRIFT_TEMPLATE_MAP table
Last modified: 2013-09-01 06:02:28 EDT
Depending on the origin of the existing db it may or may not
include the RHQ_DRIFT_TEMPLATE_MAP table. The upgrade tries to
remove this obsolete table.
But it seems that the <schema-dropTable> command fails if the
table does not exist.
As a note, my failure case was an upgrade from 4.2 to 4.3.
In master I recommend we make the dropTable command more tolerant, or allow
an attribute to ignoreError.
Also, the unit tests need to be checked to figure out why this wasn't detected.
Relevant master commit: 7ade8f5748a0f973dd684be12aa7bdf1c75e1f57
- Add obsolete=true to RHQ_DRIFT_TEMPLATE_MAP. Instead of getting
deleted it's potentialy getting created.
Master commit: c5bd48824409d53a08536b9f4c93271e755d0619
The dropTable SST command did not honor ignoreError="true" and
would kill the upgrade step if the table did not exist. This
fixes that issue.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.