Bug 1769811
| Summary: | Document the new behavior for extending a volume group | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Anjana Suparna Sriram <asriram> |
| Component: | doc-Deploying_RHHI | Assignee: | storage-doc |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhhiv-1.6 | CC: | asriram, mkalinin, rhs-bugs, sasundar |
| Target Milestone: | --- | ||
| Target Release: | RHHI-V 1.7 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-23 19:24:19 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: | 1720261, 1728225 | ||
| Bug Blocks: | |||
|
Comment 1
SATHEESARAN
2019-11-11 10:15:25 UTC
(In reply to SATHEESARAN from comment #1) > This behaviour changes wrt ansible workflow in extending the logical volume > group. > There is nothing changed at LVM layer. Do we still need customers to be > aware of this change ? Hi Sas, moving this needinfo to Marina who raised this issue to provide more clarity. Regards, Anjana (In reply to Anjana Suparna Sriram from comment #2) > (In reply to SATHEESARAN from comment #1) > > This behaviour changes wrt ansible workflow in extending the logical volume > > group. > > There is nothing changed at LVM layer. Do we still need customers to be > > aware of this change ? > > Hi Sas, > > moving this needinfo to Marina who raised this issue to provide more clarity. > > Regards, > Anjana Sas, tbh, I do not remember how I got to that bug, since it does not have customer ticket attached. Probably it was referenced from another bug. Are you saying, that there is no change for the user in this configuration and all is done via the software, so documentation is not needed? I found the customer bug: bz#1728225. It is still open and it has KCS attached: https://access.redhat.com/solutions/4575941. Probably what I meant here is that this should be in the official documentation, rather then having the deployment fail and requiring opening a case because of that. Sas, please review the KCS and tell me why you think it should not be in teh official documentation? (In reply to Marina Kalinin from comment #3) > Sas, tbh, I do not remember how I got to that bug, since it does not have > customer ticket attached. Probably it was referenced from another bug. > > Are you saying, that there is no change for the user in this configuration > and all is done via the software, so documentation is not needed? > > I found the customer bug: bz#1728225. > It is still open and it has KCS attached: > https://access.redhat.com/solutions/4575941. > Probably what I meant here is that this should be in the official > documentation, rather then having the deployment fail and requiring opening > a case because of that. > Sas, please review the KCS and tell me why you think it should not be in the > official documentation? Marina, Yes, the changes as mentioned in the Knowledge Base Article is now solved. Cockpit handles it intelligently, when the user tries to create LVM cache, it includes the Original disk also. So the changes, no longer needs to be documented. The bug bz#1728225 was there to solve different purpose, where when the disk block size of 'Fast Disk' or 'SSD' doesn't match with the disk block size of 'Slow Disk' or HDD, it will throw error and for that the workaround is to deactivate and activate VG # vgchange -an gluster_vg_xxx # vgchange -ay gluster_vg_xxx |