Bug 1578115
| Summary: | Alerts do not trigger and do not send email notification | |||
|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Saif Ali <saali> | |
| Component: | UI - OPS | Assignee: | Harpreet Kataria <hkataria> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | juwatts | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 5.9.0 | CC: | cben, cpelland, dmisharo, gmccullo, hkataria, jocarter, lavenel, lufu, mkanoor, mpovolny, obarenbo, rmanes, saali, simaishi, smallamp, tfitzger | |
| Target Milestone: | GA | Keywords: | TestOnly, ZStream | |
| Target Release: | 5.10.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 5.10.0.6 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1607438 (view as bug list) | Environment: | ||
| Last Closed: | 2019-02-11 13:59:42 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | Container Management | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1595269, 1607438 | |||
Thanks, moving back to Lucy to evaluate root cause of Alerting issue. I suspect BZ description is "wrong": 1. Create new alert based on provider >> What to Evaluate >> nothing >> Driving Event >> Container operation: Pod container start >> Notification Frequency >> 1 minute Well "Based On: Provider" with a Pod event obviously can't work because that event never happens *on a Provider*, right? So that's just an instance of the wider UX problem (A) that we allow using irrelevant event types everywhere in Control (policies too)... Not sure if that's tracked anywhere. Now what I (and possibly others?) discussed here was problem (B), which could work except container entities don't currently support it: 1. Create new alert based on **Container Node** >> What to Evaluate >> nothing >> Driving Event >> **Container operation: Node restarted** >> Notification Frequency >> 1 minute where the decided solution is hide "Driving Event" dropdown when "Based On" is Container Node or Project. Sigh, confusion :-( OK BZ description can't really be "wrong", that may well be what customers tried. I tried to read case 1578115 now but gave up tracing the original issue... But that doesn't really matter, the case is long closed. So, should we keep this BZ for problem (B)? Open a new clean one? Open another one to track problem (A) too or does it exist already? New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/6b579309d524ba41daedb25028dd5e8816d1f69e commit 6b579309d524ba41daedb25028dd5e8816d1f69e Author: Harpreet Kataria <hkataria> AuthorDate: Thu Jul 19 13:27:19 2018 -0400 Commit: Harpreet Kataria <hkataria> CommitDate: Thu Jul 19 13:27:19 2018 -0400 Hide Driving Event field for Containers. As per https://bugzilla.redhat.com/show_bug.cgi?id=1578115#c26 in BZ removed an option to be able to set/display 'Driving Event' field when adding/editing an Alert that's based on 'Container Node' or 'Container Project' models. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1578115 app/controllers/miq_policy_controller/alerts.rb | 12 +- app/views/miq_policy/_alert_details.html.haml | 4 +- spec/controllers/miq_policy_controller/alerts_spec.rb | 42 + 3 files changed, 55 insertions(+), 3 deletions(-) Version: 5.10.0.22.20181030184024_26956a0 Verification Steps: 1) Navigate to Control -> Explorer -> Alerts 2) Select "Configuration", "Add a New Alert" 3) Select "Container Node" as the "Based On" value 4) Verified the "Driving Even"t drop down is no longer present The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |
Description of problem: Container operation alert do not send email notification whenever an event happening. Version-Release number of selected component (if applicable): 5.9.1.2 How reproducible: Steps to Reproduce: 1. Create new alert based on provider >> What to Evaluate >> nothing >> Driving Event >> Container operation: Pod container start >> Notification Frequency >> 1 minute 2. 3. On Openshift side create container pod Actual results: We seen an event in the log but no email send out Expected results: email send out when ever the condition met. Additional info: