Bug 1321604
| Summary: | Hardware.Volumes data not available for VMware VMs | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
| Component: | Reporting | Assignee: | Yuri Rudman <yrudman> |
| Status: | CLOSED ERRATA | QA Contact: | Satyajit Bulage <sbulage> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.5.0 | CC: | cpelland, dajohnso, gtanzill, jhardy, jistefan, mfeifer, obarenbo, pmukhedk, yrudman |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.5.5 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 5.5.5.2 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, running SmartState Analysis on VMware virtual machine volumes produced an empty report. This was caused by the Hardware.Volumes attribute (such as free space, free space %, used space) data not populating, because the 'checkall' expression was used to create the report instead of 'checkany'. With this update, the yaml code has been changed to use 'checkany' in the FIND expression, and volume information is reported correctly.
|
Story Points: | --- |
| Clone Of: | 1319764 | Environment: | |
| Last Closed: | 2016-07-26 15:31:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1319764 | ||
| Bug Blocks: | |||
|
Comment 1
Yuri Rudman
2016-06-13 13:45:46 UTC
Able to generate Reports for "VMs with Volume Free Space <= 20%" with all the data populated properly. Verified version :-5.5.5.4.20160722162813_629f93b 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://rhn.redhat.com/errata/RHBA-2016-1488.html |