Bug 1414862
| Summary: | getVgInfo not returning updated information on allocated extents on a PV | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Avihai <aefrat> | ||||
| Component: | Core | Assignee: | Allon Mureinik <amureini> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Avihai <aefrat> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | --- | CC: | amureini, bugs, laravot, tnisan | ||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||
| Target Release: | 4.20.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-20 11:40:03 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Avihai
2017-01-19 15:41:19 UTC
Bug was opened after a discussion with Liron R on bug 1410182 with his approval Created attachment 1242520 [details]
engine and vdsm logs
vdsClient is deprecated. Liron - please sync with Irit on the new client. Thanks Avihai/Yaniv, This bug is caused by internal logic in vdsm that avoids refresh of the vg data when the domain is active, regardless of the client used to execute it. Removing the vdsClient from the header. Postponing to 4.2, as this bug isn't affecting any flow that is using getVGInfo on 4.1. Verified . Engine: 4.2.0-0.0.master.20170707124946.gitf15a6d9.el7.centos VDSM: 4.20.1-158.gita94febd This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |