Bug 1554533
Summary: | Schedule report fails to send mail when report is not empty | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Reporting | Assignee: | Yuri Rudman <yrudman> |
Status: | CLOSED ERRATA | QA Contact: | Niyaz Akhtar Ansari <nansari> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.8.0 | CC: | cpelland, ikaur, nansari, obarenbo, yrudman |
Target Milestone: | GA | Keywords: | Regression, ZStream |
Target Release: | 5.8.4 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.8.4.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1547846 | Environment: | |
Last Closed: | 2018-06-25 14:18:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1547846 | ||
Bug Blocks: |
Comment 3
CFME Bot
2018-04-09 18:36:32 UTC
I am unable to select custom report In Filter drop downs while creating schedule. I have logged the issue in 5.9 which has been fixed in 5.9 but the issue is reproducible in 5.8.4.1 as well. 5.9 BZ : https://bugzilla.redhat.com/show_bug.cgi?id=1559323 Niyaz, could you test this BZ using standard reports, which should be available for selection ? Yuri, I have tested with standard reports and its works fine. I moved to assign as per step 2 of steps to reproduce because i can't select the custom report. It works fine with standard reports. OK, thank you Niyaz. I can confirm that for the purpose of testing this specific bug step 2 could be replaced by "select any report". There is no differentiations between standard and custom reports when sending e-mail notification. Moving this BZ to Verified state Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1972 |