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

Default value for agent.setup.camSecure in agent.properties is incorrectly set to yes

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Deferred
  • Affects Version/s: 4.4.0.1, 4.5
  • Fix Version/s: None
  • Component/s: Agent / PDK
  • Environment:
    HQ-server 4.5.0-EE-112 running on CentOS 5.4
    HQ-agent 4.5.0-EE-112 running on RHEL 5.4
  • Case Links:
    none
  • Regression:
    No

Description

Default value for agent.setup.camSecure in agent.properties is incorrectly set to yes.

The commented value displayed for the agent.setup.camSecure setting is:
#agent.setup.camSecure=yes

When users uncomment this setting, the assumption is that the default value is yes. When running agent setup or on initial startup, the prompt indicates:
Should Agent communications to HQ always be secure [default=no]:

Since the true default value for agent.setup.camSecure is no, the corresponding line in the agent.properties should correctly state:
#agent.setup.camSecure=no

Correcting this default value will help to avoid confusion as to what is actually the correct default value and simply removing the comment marks should explicitly set the default values.

Expected Result:
All default values for configuration settings in the agent.properties file should be set correctly even when commented.

Actual Result:
The agent.setup.camSecure value in the agent.properties file is incorrectly set to yes.

Steps to Reproduce:
1. Install the agent on any platform.
2. Go to the <agent_install>/conf/ directory.
3. Edit the agent.properties file.
4. Note the agent.setup.camSecure value is set to yes by default

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:
    41 weeks, 2 days ago