#4089 [HHQ-3790] Upgrading hq-agent through UI does not maintain S

[Hyperic Team]

http://jira.hyperic.com/browse/HHQ-3790
Upgrading hq-agent through UI does not maintain Sybase functionality; all Sybase resources become unavailable

There are two main problems experienced from upgrading the hq-agent through the UI:


1. The jdbc driver for Sybase is no longer referenced - the existing copy (or softlink) from the earlier build is not copied during the upgrade so there is no longer a reference for the updated hq-agent.


2. Restarting the agent from the UI does not appear to perform a full restart; the added Sybase driver does not get picked up.

Expected Result:


All existing Sybase resources are maintained and functional as previously; no additional steps required.

Actual Result:


All existing Sybase resources become unavailable; extra steps are necessary for Sybase resources to be recognized.


The agent.log reports 'No suitable driver'

Steps to reproduce:


Within the UI, upgrade an older build of the hq-agent (i.e. 4.3.0-EE-1366) to a newer build (i.e. 4.3.0-EE-1368):


1. Log into HQ Server Dashboard


2. Select the Resource where the agent is installed on the Sybase server


3. Click the 'Views' tab


4. Click the 'Agent Commands' button


5. From the Execute Command dropdown list, select 'upgrade'


6. From the 'Select upgradeable agent bundle' dropdown list, select newer agent (i.e. agent-4.3.0-EE-1368.tgz)


7. The Result pane will display 'Successfully sent upgrade command to agent with id xxxxx.'


8. Upon upgrade completion, note all the Sybase resources are marked as unavailable


9. Connect to the Sybase server


10. Go to the hq-agent bundles directory (i.e. ./hq-agent-4.3-EE-1366/hyperic-hq-agent-4.3.0-EE/bundles)


11. Note the new agent build directory was successfully created by the upgrade


12. Change to the new agent directory and go to the /pdk/lib/jdbc directory


13. Note there is no supplied Sybase jdbc driver (jconn3.jar)


14. Copy the required jdbc driver to this location or create a softlink


15. Return to the HQ Server Dashboard


16. Select the Resource where the agent is installed on the Sybase server


17. Click the 'Views' tab


18. Click the 'Agent Commands' button


19. From the Execute Command dropdown list, select restart


20. Click the 'Execute' button


21. Upon restart, note the Sybase resources are still marked as unavailable

Work around:


Restart the hq-agent directly from the agent server (./hq-agent.sh restart)

Additional Notes:


This issue was reproduced from upgrading hq-agent-4.3.0-EE-1366 to hq-agent-4.3.0-EE-1368 on two different Sybase Servers:

See attached log files for additional details.