Red Hat Bugzilla – Bug 967520
Alert condition of type Availability Change does not allow to set all possible values
Last modified: 2015-11-01 19:43:20 EST
Description of problem:
When I am creating new alert condition of "Availability Change" type, I am able to select only 3 options:
Goes down, Goes not up, Goes up
but, AlertConditionOperator defines more values.
AVAIL_GOES_DOWN(Type.STATELESS), // avail becomes DOWN from anything else
AVAIL_GOES_DISABLED(Type.STATELESS), // avail becomes DISABLED from anything else
AVAIL_GOES_UNKNOWN(Type.STATELESS), // avail becomes UNKNOWN from anything else
AVAIL_GOES_NOT_UP(Type.STATELESS), // convenience for avail becomes DOWN | DISABLED | UNKNOWN from UP
AVAIL_GOES_UP(Type.STATELESS), // avail becomes UP from anything else
UI should list all possible values, not just those 3. (It is possible to create alert condition with AVAIL_GOES_UNKNOWN using REST API, editing such condition in UI is a little ackward)
Version-Release number of selected component (if applicable):
The states AVAIL_GOES_UNKNOWN and AVAIL_GOES_DISABLED are not allowed for a resource of type platform. For other resource types it is possible to set these values. If REST API allows this type of alert condition, then it is probably a bug.
We should probably add the check to the SLSB, because if it is exposed via CLI it needs to be checked as well.