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

mv commands are causing a "rename" configuration event altough file name was not changed (the file changed location)

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.6.5
  • Fix Version/s: None
  • Component/s: Events
  • Environment:
    linux
  • Case Links:
    none
  • Regression:
    No

Description

a command like this:
"/server-4.6.5.RC2-EE/hq-engine/hq-server/conf/lib$ mv log4j ../"

is causing an event that is described in hyperic UI as reame file:

21-02-2012 18:30:08,420 IST INFO [ChangeEventProcessor] [ChangeEventProcessor@481] Event processed and fired: revId:980c88073
36e012df8e187faf26906b02c7fbff8 rename /home/hqadmin/server-4.6.5.RC2-EE/hq-engine/hq-server/conf/log4j.xml Old path: /home/h
qadmin/server-4.6.5.RC2-EE/hq-engine/hq-server/conf/lib/log4j.xml

Activity

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 (0)

Dates

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