Bug 772661
Summary: | upgrade from JON 2.4.1 to 3.0.0 will fail if there is no role with id==2 | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Tom Fonteyne <tfonteyn> |
Component: | Core Server | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2 | CC: | hrupp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom Fonteyne
2012-01-09 14:56:00 UTC
workaround: recreate the role with: INSERT INTO rhq_role (id, "name", description, fsystem) VALUES (2, 'All Resources Role', 'Provides full access to all resources in inventory. Cannot modify users, roles or server settings.', false); -- Global: INVENTORY, BUNDLE INSERT INTO rhq_permission (role_id, operation) VALUES (2, 1); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 12); --- Resource: All except for MANAGE_EVENTS, added in 2.94 INSERT INTO rhq_permission (role_id, operation) VALUES (2, 3); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 4); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 5); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 6); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 7); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 8); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 9); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 10); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 11); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 13); INSERT INTO rhq_permission (role_id, operation) VALUES (2, 16); consider making role read-only |