Description of problem: The alert conditions for platform resource displays the availability dropdown values 'Goes Disabled' and 'Goes Unknown' ( For condition type: Availability Change) Please refer the attached screenshot. As we cannot disable a platform resource, ( Ref. Bug : https://bugzilla.redhat.com/show_bug.cgi?id=807629) the availability alert values 'Goes Disabled' and 'Goes Unknown' are not required. Version-Release number of selected component (if applicable): Build#1386 (Version: 4.4.0-SNAPSHOT Build Number: 28e565c) How reproducible: Always Steps to Reproduce: 1. Navigate to Alerts->Definitions tab of a platform resource. 2. Click on 'New' button. 3. Enter alert name and click on 'Conditions' tab. 4. Click on 'Add' button. 5. Select condition type: Availability Change and click on 'Availability' dropdown. 6. It displays values 'Goes Disabled' and 'Goes Unknown'. Actual results: The alert conditions for platform resource displays the availability dropdown values 'Goes Disabled' and 'Goes Unknown'. Expected results: Platform Alert conditions for availability (Goes Disabled and Goes Unknown ) should be removed. Additional info:
Created attachment 579497 [details] Screenshot
setting priority to medium per BZ triage 4/23 (crouch, santos, oleary, foley)
http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=b352ab2 git log master time: Mon Jun 25 15:16:12 2012 +0200 commit: b352ab20a4e0deb0d9eccf1d492de2917d2098c2 author: Jirka Kremser - jkremser message: [BZ 815321 - Platform alert conditions for availability (Goes Disabled and Goes Unknown ) should be removed] Options have been reomved when adding alert condition for resource of type platform
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.