Bug 1586032
| Summary: | [RHHI] Guarenteed space differing under storage domains in the RHV-M | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | bipin <bshetty> |
| Component: | Frontend.WebAdmin | Assignee: | Denis Chaplygin <dchaplyg> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | bipin <bshetty> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | future | CC: | amarchuk, bshetty, bugs, dchaplyg, rhs-bugs, sabose, sankarshan, sasundar, tnisan |
| Target Milestone: | ovirt-4.2.4 | Flags: | rule-engine:
ovirt-4.2?
rule-engine: blocker+ bshetty: planning_ack? rule-engine: devel_ack+ bshetty: testing_ack+ |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: SD sharing same thin devices reported free size of that device, ignoring SD size limitation.
Fix: In case of a bigger underlying device, report size is limited to the SD size.
Result: Guaranteed space is not bigger, then SD free space
|
Story Points: | --- |
| Clone Of: | 1586023 | Environment: | |
| Last Closed: | 2018-06-26 08:39:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1586023 | ||
|
Description
bipin
2018-06-05 10:59:17 UTC
Please provide lsblk output from all 3 nodes, the vdsm logs with the logicalvolume monitoring and the engine.log object has no attribute 'glusterLogicalVolumeList' - I see this error, can you check the version of vdsm running on the host? The vdsm version used is vdsm-4.20.29 Verified the bug in component version vdsm-4.20.31-1.el7ev.x86_64. Result: Now the Storage Domain using same thin devices have same guaranteed free space. Attaching the screenshot from RHV-M This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |