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

Gemifre plugin - no indication to setup configuration properties

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.5
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.5.0-EE-M7 running on CentOS 5.4
    HQ-agent 4.5.0-EE-M7 running on RHEL 5.4
     - Gemfire 6.5 RC2 on hq-agent
  • Case Links:
    none
  • Regression:
    No

Description

Gemfire plugin - no indication to setup configuration properties.

After creating a Gemfire Distributed System platform, the message 'Platform test Gemfire has been created' is displayed; however, there is no indication that configuration properties must be set.

As with other plugins, there is typically an indication that 'This resource is turned off or has not been configured properly.'

For example, a server could show:
This resource is turned off or has not been configured properly.
The problem is: Invalid configuration: Error reported by Agent @ 10.150.29.94:2411: java.lang.SecurityException: Authentication failed! Username or password is null
Please turn on the server, or fix its Configuration Properties.

This type of message indicates to the user that the server is not fully configured and the configuration properties must be set to fully monitor the server.

In the case of GemFire Distributed System, the jmx.url, jms.username and jmx.password must be set.

Expected Result:
If configuration is necessary to monitor a server, there should be an indication that the resource is turned off or has not been configured properly.

Actual Result:
There is no indication that the resource is turned off or has not been configured properly.

Steps to Reproduce:
1. Log into Hyperic
2. Go to Browse - Resources
3. From the Tools Menu, select New Platform
4. Enter Proprties as necessary selecting Gemfire Distributed System for Platform Type
5. Click the OK button and Platform will be created
6. Click the Monitor tab
8. Click the Inventory tab
9. Note no indication that configuration properties are not set

Additional Information:
1. Examining the Configuration Properties, note the Shared parameters (jmx.url, jmx.username, jmx.password) are blank.
2. Clicking the Edit button populates the jmx.url.

Activity

Hide
German Laullon added a comment -

I think this is a server/ui "problem".

Show
German Laullon added a comment - I think this is a server/ui "problem".
Hide
Frederic Calindas added a comment -

There is no initial indication after creating the GemFire Distributed System platform; however, after exiting and going back intot he platform, there is indication:

This resource is turned off or has not been configured properly.
The problem is: Invalid configuration: Unable to connect to 10.16.16.125:2224: Read timed out
Please turn on the server, or fix its Configuration Properties.

Show
Frederic Calindas added a comment - There is no initial indication after creating the GemFire Distributed System platform; however, after exiting and going back intot he platform, there is indication: This resource is turned off or has not been configured properly. The problem is: Invalid configuration: Unable to connect to 10.16.16.125:2224: Read timed out Please turn on the server, or fix its Configuration Properties.
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:
    41 weeks, 2 days ago