Bug 117393

Summary: RickshawPublishAPIUpgrade doesn't run any content type initializers
Product: [Retired] Red Hat Enterprise CMS Reporter: Daniel BerrangĂ© <berrange>
Component: otherAssignee: 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:42:59 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:46:11 UTC 
Description of problem:
As a result of bug 117390, the RickshawPublishAPIUpgrade manually runs
the CMS initializer before doings its work. This, however, means that
none of the content item/asset initializers will have been run when
the republishing takes places. One consequence of this is that none of
the content ype speciifc search metadata XML generation rules will be
registered & thus the search indexes will be populated with garbage.
In other cases the publish may not even complete if the content item /
asset requires that a custom DomainObjectInstantiators be present -
for example the 'Address' content type requires a custom instantiator
for the ISOCode object.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Justin Ross 2004-03-03 18:53:52 UTC 
The RPAPIUpgrade#main method needs to run all the database-registered
initializers.  Adding to blocker list.
Comment 2 Justin Ross 2004-03-29 23:54:15 UTC 
Fixed a while ago now.