Bug 117387

Summary:	ccm upgrade does not maintain ordering of Java & SQL scripts
Product:	[Retired] Red Hat Web Application Framework	Reporter:	Daniel Berrangé <berrange>
Component:	installation	Assignee:	Justin Ross <jross>
Status:	CLOSED RAWHIDE	QA Contact:	Jon Orris <jorris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	nightly
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-04-06 14:43:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	113496

Description Daniel Berrangé 2004-03-03 15:25:48 UTC

Description of problem:
The Java portion of the upgrade process will typically require that
the SQL schema upgrade has already been done. There may, however, be
cases where there needs to be mulitple java/sql upgrade passes
interleaved. THe ccm upgrade command currently mindlessly runs

   1. All Java scripts
   2. All SQL scripts.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Write an upgrade containing multiple SQL & Java scripts

Actual results:
All Java scripts are run before all SQLK scripts

Expected results:
All scripts are run in the order defined in the .upgrade XML file.


Additional info:

Comment 1 Justin Ross 2004-03-03 18:37:29 UTC

Oh right, this is quite broken (it's the cause of the core and cms
6.0-6.1 upgrade problems).  Making this a blocker.

Comment 2 Justin Ross 2004-03-04 17:52:05 UTC

Fixed at perforce change 41041.