Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Custom changes made to wrapper.conf are not persisted when agent upgraded

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.1.0, 4.2.0, 4.3, 4.4
  • Fix Version/s: None
  • Component/s: Agent / PDK
  • Environment:
    HQ-server 4.4.0-EE-1462 running on RHEL 5
    HQ-agent 4.4.0-EE-1462 running on Windows 2008
     - VMware vCenter Server 4.0 running with HQ-agent
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

Custom changes made to wrapper.conf are not persisted when agent upgraded.

When updates to additional java parameters, logging properties or windows properties are made within the wrapper.conf within an agent bundle (i.e. C:\hq\hyperic-hq-agent-4.4.0-EE\bundles\agent-4.4.0-EE-1462\conf), the changes are not persisted and maintained when an agent is upgraded via the HQ UI.

Since the wrapper.conf is located in the bundle, the updated bundle is deployed with it's own wrapper.conf.

After the bundled is copied, the upgrade process restarts the agent.

If a change was made to the Name of the service for the Wrapper Windows NT/2000/XP Service Properties, the result will show the service is not installed.

This may also cause two agents getting registered on the same port to one HQ server.

Expected Result:
The agent upgrade should complete successfully and maintain changes made to the previous bundle.

Actual Result:
Changes made to the wrapper.conf are not maintained when the agent is upgraded.

Steps to reproduce:
1. Install and configure an agent to a HQ server
2. Log into HQ Server and Browse Resource
3. Select the platform of the server with an agent installed
4. Select the hq-agent link from within the Deployed Servers Health
5. Go to the Views tab
6. Click the Agent Commands button
7. Select upgrade from the drop-down list of Execute Command
8. Select the agent bundle version to upgrade (if more than two)
9. Click the Execute button
10. Examine the agent.log on the agent machine
11. Note the custom changes made to the wrapper.conf are not persisted

Work around:
1. Manually copy the wrapper.conf from the previous bundle into the new bundle
2. Restart the agent

Additional Notes:
If changes made to the Name of the service for the Wrapper Windows NT/2000/XP Service Properties, may need to uninstall service and reinstall

Activity

Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    40 weeks, 6 days ago