Bug #37019 | Confusing message when no rule is actually scheduled | ||
---|---|---|---|
Submitted: | 27 May 2008 21:38 | Modified: | 28 May 2008 23:50 |
Reporter: | Diego Medina | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Enterprise Monitor: Web | Severity: | S3 (Non-critical) |
Version: | 2.0.0.6046 | OS: | Any |
Assigned to: | Joshua Ganderson | CPU Architecture: | Any |
[27 May 2008 21:38]
Diego Medina
[28 May 2008 23:50]
Joshua Ganderson
This is a tricky thing to communicate. The current message (after much discussion) is by design. What it's trying to communicate is that you attempted to apply X rules to Y servers and Z were successfully scheduled. While we could special case the 0 case for successful schedules created, I'm not sure that this is an added benefit - removing pertinent info about what we _tried_ to do.