Bug 618214
| Summary: | Upgrade JON2.3.1 to 2.4 lost 'SNMP Server Configuration Properties' data | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Rajan Timaniya <rtimaniy> | ||||||
| Component: | Database | Assignee: | Heiko W. Rupp <hrupp> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Rajan Timaniya <rtimaniy> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 3.0.0 | CC: | cwelton, hrupp, lkrejci, rtimaniy, skondkar | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 648780 (view as bug list) | Environment: | |||||||
| Last Closed: | 2013-09-02 07:17:47 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: | 625146 | ||||||||
| Attachments: |
|
||||||||
Manual upgrade steps for RHQ 3 are documented in https://bugzilla.redhat.com/show_bug.cgi?id=618214 We will re-visit this in master. *argh* Comment 1 has the wrong link. This one is the right one: https://bugzilla.redhat.com/show_bug.cgi?id=618265 Code added in master at version 5b29f99 As discuss with Heiko, the bug will be tested on JON 2.4.1 build, its known issue of JON 2.4 Needs to be tested as part of JON3 QA Failed. The configuration entries with the settings are persisted using the upgrade code but the rhq_plugin table is never updated with an entry for the snmp-alert plugin and thus the plugin is never associated with the configuration. Another problem that I can see here is that there are no entries for the server-side plugins in the rhq_plugin table before the RHQ 3 server is started for the first time so the upgrade code will have to insert a new entry in that table and somehow fake the plugins MD5 and binary contents... commit d19c483830aaed8ab154dcb494334ad1e5baab9e
Author: Lukas Krejci <lkrejci>
Date: Wed Dec 1 14:37:47 2010 +0100
BZ 618214 - Create a temporary entry in RHQ_PLUGIN table for the snmp-alert plugin in case we need to add something to its configuration during db-upgrade.
Once the server starts up, the temporary entry will get overwritten by the "real stuff".
Note that this needs to be tested on both postgres and oracle. Removing blocker against jon241 version of this bug Verified this by Upgrading JON2.3.1 to 2.4.1 build (version: 2.4.1.GA build number: 11123:4efbdc8279) Verified by upgrading on both postgres and oracle. The details of 'SNMP Server Configuration Properties' data is displayed in Administration->System Configuration->Settings->Configure Server Plugins->Alert Plugin->Alert:SNMP page. Please refer the attached screenshot. Marking as verified. Created attachment 506225 [details]
Screenshot
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago. |
Created attachment 434408 [details] server log Description of problem: Upgrade JON2.3.1 to 2.4 lost 'SNMP Server Configuration Properties' data ('SNMP protcol version' & 'Trap OID'). Version-Release number of selected component (if applicable): version: 2.4.0.GA_QA (build #78) build number: 10888:29722f6 How reproducible: Always Steps to Reproduce: 1) Install JON 2.3.1 and agent 2) Administration > System Configuration > Settings 3) Set 'SNMP Server Configuration Properties' SNMP Protocol Version: 2c Trap OID: 1.3.6.1.4.1.8072.4.0.1 Community: public 4) Down JON server 2.3.1 (Keep agent running) 5) Upgrade JON 2.3.1 to 2.4 (build #78) 6) Log-in to upgraded JON 2.4 (build #78) 7) Goto Server Settings > Installed Plugins >Server Plugins Configuration > Alert:SNMP 8) Refer Plugin configuration Actual results: Upgrade JON2.3.1 to 2.4 lost 'SNMP Server Configuration Properties' data ('SNMP protcol version' & 'Trap OID'). Expected results: Upgrade JON2.3.1 to 2.4 should not lost 'SNMP Server Configuration Properties' data. Additional info: Please refer attached server log.