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

HQ Server upgrade does not maintain comments in hq-server.conf

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.5 Sprint 26, 4.5 M6, 4.5
  • Fix Version/s: None
  • Component/s: Installation / Upgrade
  • Environment:
    HQ-server 4.5.0-EE-82 running on RHEL 5.4
    HQ-agent 4.5.0-EE-82 running on RHEL 5.4
  • Case Links:
    none
  • Regression:
    Yes
  • Story Points:
    3
  • Tags:

Description

HQ Server upgrade does not maintain comments in hq-server.conf.

After upgrading the server, all the existing comments in the previous version of the hq-server.conf is missing in the upgraded hq-server.conf; only the actual server parameters are available.

Expected Result:
The hq-server.conf should display all comments post upgrade just as if installed new.

Actual Result:
All the comments in the upgraded hq-server.conf file is stripped.

Steps to Reproduce:
1. Upgrade the hq-server.
2. Examine the hq-server.conf file.
3. Note the comments are stripped.

Activity

Hide
Todd Rader added a comment -

The proposed mitigation fix is to simply copy the old file into a name with a suffix indicating it's a backup, so the comments are not lost. This looks straightforward, just insert a <copy> task before the upgrade-copy task in setup.xml:

<!-- Copy the existing config -->
<serverConfigUpgrade existing="${server.upgradedir}/conf/hq-server.conf"
new="${server.product.dir}/conf/hq-server.conf" upgradeDir="${server.upgradedir}"/>

Show
Todd Rader added a comment - The proposed mitigation fix is to simply copy the old file into a name with a suffix indicating it's a backup, so the comments are not lost. This looks straightforward, just insert a <copy> task before the upgrade-copy task in setup.xml: <!-- Copy the existing config --> <serverConfigUpgrade existing="${server.upgradedir}/conf/hq-server.conf" new="${server.product.dir}/conf/hq-server.conf" upgradeDir="${server.upgradedir}"/>
Hide
Jennifer Hickey added a comment -

Added backup of existing hq-server.conf to hq-server-yyyy-MM-dd.hhmm.conf during server upgrade

Show
Jennifer Hickey added a comment - Added backup of existing hq-server.conf to hq-server-yyyy-MM-dd.hhmm.conf during server upgrade
Hide
Frederic Calindas added a comment -

Tested with 4.5.0-EE-133 build.

After upgrading servers on Windows and Linux, the hq-server.conf file still did not maintain the previous comments.

A hq-server-YYYY-MM-DD.HHMM.conf file was generated in both Windows and Linux and all comments existed.

The hq-server.conf only contatined one comment with the date, for example:

  1. Wed Oct 13 20:27:58 EDT 2010
Show
Frederic Calindas added a comment - Tested with 4.5.0-EE-133 build. After upgrading servers on Windows and Linux, the hq-server.conf file still did not maintain the previous comments. A hq-server-YYYY-MM-DD.HHMM.conf file was generated in both Windows and Linux and all comments existed. The hq-server.conf only contatined one comment with the date, for example:
  1. Wed Oct 13 20:27:58 EDT 2010
Hide
Kashyap Parikh added a comment -

Moving out of 4.5 since we have added a workaround that preserves and copies original property file.

Show
Kashyap Parikh added a comment - Moving out of 4.5 since we have added a workaround that preserves and copies original property file.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
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 (1)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks ago