Bug 590718
Summary: | Fail upgrade JON 2.3.1 to JON 2.4 with Roles & Users | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Rajan Timaniya <rtimaniy> | ||||||||
Component: | Core Server | Assignee: | Simeon Pinder <spinder> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | high | ||||||||||
Version: | 3.0.0 | ||||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | 2.4 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2010-08-12 16:48:52 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: | 565628, 577267 | ||||||||||
Attachments: |
|
Description
Rajan Timaniya
2010-05-10 14:37:51 UTC
Created attachment 412861 [details]
UI Error
Created attachment 412862 [details]
UI error stack trace
I've reproduced this. It can also be reproduced without creating any roles on a fresh upgrade by attempting to browse an available role. The dbupgrade sql was not complete and did not include some of the necessary tables used by ldap mappings. Not sure how we missed this up to now or in our last dbupgrade discussion about this. Checked in missing upgrade logic. Passes testing on my local postgres instance, but still needs oracle and further testing. Fixed in successful build of master >= 303 with: commit abc4d3ebd679a9d8e17e1759caa8f5991c314b7a Verified on JON build #147 http://hudson-qe.rhq.rdu.redhat.com:8080/job/jon/147/ Steps: 1) Install JON 2.3.1 on Oracle 10g / Postgres (8.4.2) 2) Create role - 'Test_Role' 3) Create user - 'rajan' and assign 'Test_Role' to the user 4) Upgrade JON 2.3.2 to JON build #147 5) Log-in to JON build #147 and click on role 'test-role' JON is working fine with role and users after upgrade JON 2.3.1 to JON 2.4 (JON build #147). Mass-closure of verified bugs against JON. |