Bug 1433925
| Summary: | poolmetadatasize for the thinpool created on arbiter node should not be 16GB | ||
|---|---|---|---|
| Product: | [oVirt] cockpit-ovirt | Reporter: | RamaKasturi <knarra> |
| Component: | Gdeploy | Assignee: | Devyani Kota <dkota> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RamaKasturi <knarra> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 0.10.7-0.0.15 | CC: | bugs, dkota, knarra, rbarry, sabose |
| Target Milestone: | ovirt-4.1.5 | Flags: | sabose:
ovirt-4.1?
sabose: planning_ack? rule-engine: devel_ack+ knarra: testing_ack+ |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cockpit-ovirt-0.10.7-0.0.21 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-23 08:00:59 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: | 1411323, 1447919 | ||
|
Description
RamaKasturi
2017-03-20 11:52:28 UTC
Hi devyani, I am trying to verify this bug. I have installed latest ovirt-cockpit-dashboard and i have few queries on the same and could you please clarify the below ? 1) I see that thinpool size on arbiter node is 44GB? How did we arrive at this? 2) poolmetadatasize should be 0.5% of thinpool. 0.5% of 44 GB is 220MB. But in the gdeployconfig.conf file i see it as 1GB. Hi Kasturi, Not the best practice, but I think that the patches to both the following bugs: [1] [2] are related, considering the fact that changes are made to the same file. Thinpool size should be returning 16GB. Yes, poolmetadatasize should be 0.5% of thinpool. Testing after implementing both patches should help? Please let me know if it doesn't. Thanks. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1434735 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1433925 Hi devyani,
I see that poolmetadatasize for thinpool created on arbiter node is set as 1gb irrespective of the thinpoolsize. Is this the expected behaviour?, can you please confirm ?
When thinpool size was 44GB, poolmetadatasize was 1GB.
When thinpool size is 40GB, poolmetadatasize is set as 1GB.
Moving this back as i see that when allocating size for thinpool, poolmetadatasize is not taken into account. Here i see that thinpool size does not include poolmetadatasize. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. (In reply to RamaKasturi from comment #3) > Hi devyani, > > I see that poolmetadatasize for thinpool created on arbiter node is set > as 1gb irrespective of the thinpoolsize. Is this the expected behaviour?, > can you please confirm ? > > When thinpool size was 44GB, poolmetadatasize was 1GB. > > When thinpool size is 40GB, poolmetadatasize is set as 1GB. The poolmetadatasize is rounded up to nearest GB as per the code. So this is as expected. Kasturi, is the thinpoolsize then the only issue with this bug? If you say poolmetadatasize is rounded to nearest GB then only thinpoolsize is the issue with this bug. Verified and works fine with build cockpit-ovirt-dashboard-0.10.7-0.0.21.el7ev.noarch. Thinpoolsize on the arbiter node is rounded off to nearest GB which is 1GB. Since this bug is moved to on_qa will raise another bug to include poolmetadatasize with thinpoolsize. Logged another bug for the inclusion of poolmetadatasize with thinpool. https://bugzilla.redhat.com/show_bug.cgi?id=1474267 |