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

Issue with "boolean" config option type in resource plugins

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.5, 4.5.1.2
  • Fix Version/s: None
  • Component/s: UI / UX
  • Case Links:
    none
  • Regression:
    No

Description

If you have the default to true for a config option of type boolean that it will not allow the value to ever be false. Here's a very basic xml plugin that demonstrates this:

Sample plugin for testing issue.

<plugin>
  <service name="Test Service">

    <config>
      <option name="script"
              description="Collector script"
              default="/tmp/myscript.sh" />

      <option name="doSomething"
              description="Should I do something?"
	      type="boolean"
              default="true" />
    </config>

    <filter name="template"
            value="exec:file=%script%,args=%device%"/>

    <metric name="Availability"
            template="${template}:Availability"
            indicator="false"/>
  </service>
</plugin>

Changing the default to false causes it work as expected.

Steps I took to reproduce:

1.) Deploy example plugin
2.) Add a dummy service type
3.) Go to configuration properties and uncheck the checkbox.
4.) Click Ok
5.) The rendered page will still show doSomething as true
6.) Repeat steps 3 - 5 = same results
7.) Replace default value to false in plugin and redoploy
8.) Repeat stesp 3 - 5 = doSomething will show as false

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