Bug 802918

Summary: [RFE] Add a note to the cumin-database install section that suggests running cumin-admin upgrade-schema for existing databases
Product: Red Hat Enterprise MRG Reporter: Trevor McKay <tmckay>
Component: Management_Console_Installation_GuideAssignee: Cheryn Tan <chetan>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: unspecified    
Version: DevelopmentCC: jskeoch, jwulf, matt, rlandman, sgraf
Target Milestone: 2.2Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-20 01:01:19 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: 794516    
Attachments:
Description Flags
Patch against Installation.xml to add instruction for cumin-admin upgrade-schema none

Description Trevor McKay 2012-03-13 18:41:36 UTC
Description of problem:

For users updating the cumin package on top of an existing install, the MCIG should suggest that they run "cumin-admin upgrade-schema" instead of "cumin-database install".  The latter will tell them that the database is already installed and will do nothing, the former *may* be required for cumin to run after the update.

There won't always be schema changes in a release, but if there are and the upgrade command is not run the service will fail on start up with messages in the log files noting that the upgrade should be run.  The command will return with "nothing to do" if there is indeed nothing to do.

Comment 2 Trevor McKay 2012-03-16 21:32:36 UTC
Created attachment 570709 [details]
Patch against Installation.xml to add instruction for cumin-admin upgrade-schema