Bug 701436 - RHQ3 ---> RHQ4 errors in rhq-installer-dbupgrade.log
RHQ3 ---> RHQ4 errors in rhq-installer-dbupgrade.log
Product: RHQ Project
Classification: Other
Component: Database (Show other bugs)
All All
medium Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
Blocks: jon30-bugs
  Show dependency treegraph
Reported: 2011-05-02 16:34 EDT by Mike Foley
Modified: 2013-09-02 03:27 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-02 03:27:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
rhq-installer-dbupgrade.log (30.03 KB, application/octet-stream)
2011-05-02 16:34 EDT, Mike Foley
no flags Details
verification .... (51.64 KB, application/octet-stream)
2011-09-27 10:43 EDT, Mike Foley
no flags Details

  None (edit)
Description Mike Foley 2011-05-02 16:34:34 EDT
Created attachment 496364 [details]

Description of problem:
RHQ3  --->  RHQ4 errors in rhq-installer-dbupgrade.log

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

How reproducible:

Steps to Reproduce:
1. RHQ3.0 --> RHQ4.0 upgrade
Actual results:
errors in upgrade log file.  see attached.

Expected results:
no errors in upgrade log file.  

Additional info:
Comment 1 Charles Crouch 2011-08-11 17:23:37 EDT
Does this still occur when upgrading from RHQ3 to RHQ4.1beta. If so please 
increase severity
Comment 2 Charles Crouch 2011-09-26 17:55:37 EDT
Mike, I presumed you've already QE'd this scenario, upgrading from RHQ3 
(JON2.4) to a recent build of master?
Comment 3 Mike Foley 2011-09-27 10:42:42 EDT
attaching upgrade log to document this verification.  i upgraded from jopr 2.3.1 --->RHQ 3--->RHQ 4... no issues.
Comment 4 Mike Foley 2011-09-27 10:43:29 EDT
Created attachment 525148 [details]
verification ....
Comment 5 Heiko W. Rupp 2013-09-02 03:27:51 EDT
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.

Note You need to log in before you can comment on or make changes to this bug.