Bug 1767791
| Summary: | Chargeback reports not working | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
| Component: | Reporting | Assignee: | Libor Pichler <lpichler> |
| Status: | CLOSED ERRATA | QA Contact: | Tasos Papaioannou <tpapaioa> |
| Severity: | urgent | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Priority: | urgent | ||
| Version: | 5.10.9 | CC: | dmetzger, gekis, gtanzill, jprause, obarenbo, tpapaioa |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.11.1 | Flags: | simaishi:
cfme-5.11.z+
simaishi: mirror+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.11.1.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1750800 | Environment: | |
| Last Closed: | 2019-12-13 00:35:40 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: | 1750800 | ||
| Bug Blocks: | |||
|
Comment 2
CFME Bot
2019-11-01 19:28:46 UTC
New commit detected on ManageIQ/manageiq/ivanchuk: https://github.com/ManageIQ/manageiq/commit/24b389a21290e640d732650b4bead69573cb922c commit 24b389a21290e640d732650b4bead69573cb922c Author: Gregg Tanzillo <gtanzill> AuthorDate: Wed Sep 11 06:21:02 2019 -0400 Commit: Gregg Tanzillo <gtanzill> CommitDate: Wed Sep 11 06:21:02 2019 -0400 Merge pull request #19280 from lpichler/dont_raise_error_when_tenant_is_not_find_in_chargebackVM Don't raise error when tenant is not find in chargeback VM (cherry picked from commit aa30a4e3ea46b0cab4d1ec07141416cb9c68e89a) https://bugzilla.redhat.com/show_bug.cgi?id=1767791 app/models/chargeback_vm.rb | 8 +- spec/models/chargeback_vm_spec.rb | 27 +- 2 files changed, 25 insertions(+), 10 deletions(-) Verified on 5.11.1.0. 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-2019:4201 |