| Summary: | GlusterFS: can't create a snapshot when cinder is configured to work with gluster (permissions) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Dafna Ron <dron> | ||||
| Component: | openstack-cinder | Assignee: | Eric Harney <eharney> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Dafna Ron <dron> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.0 | CC: | abaron, ddomingo, dron, eharney, gfidente, hateya, sgordon, yeylon, yrabl | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 4.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | openstack-cinder-2013.2-5.el6ost | Doc Type: | Bug Fix | ||||
| Doc Text: |
Previously, the Block Storage service did not check first if it had the required permissions to write to a GlusterFS share before creating a snapshot. As a result, if the Block Storage service did not have write permissions to a GlusterFS share, any attempts to create a snapshot on the share would fail. No indication would be given to the user of why the attempt failed, and the volume/snapshot data could be left in an inconsistent state.
With this fix, the Block Storage service now checks if it has write permissions to a GlusterFS share before creating a snapshot. Any attempt to create a snapshot would fail with the correct notification (before any data is modified) if the Block Storage service does not have write permissions to the share.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-12-20 00:26:48 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: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1016806, 1033652, 1033714 | ||||||
| Attachments: |
|
||||||
|
Description
Dafna Ron
2013-10-08 17:21:43 UTC
This is probably related to the permissions of the /var/lib/cinder/mnt/4a31... directory. I suspect we should be ensuring that the volume permissions are configured with something like this, which should ensure the cinder user can write in the directory. # gluster volume set cinder-vol storage.owner-uid=165 # gluster volume set cinder-vol storage.owner-gid=165 I've confirmed that the above instructions made this work for me. (Though had to remove the "=" in the command.) "chown -R cinder: /var/lib/cinder/mnt/" also worked for me, this is something we should automate in packstack maybe? removing testBlocker since we have a workaround. I'm planning to add code to Cinder to detect when the share is not writable, so that snapshot operations will fail earlier, rather than putting the qcow2 files/metadata tracking into an inconsistent state. *** Bug 1031939 has been marked as a duplicate of this bug. *** *** Bug 1029947 has been marked as a duplicate of this bug. *** verified on [root@cougar06 ~(keystone_admin)]# rpm -qa |grep cinder python-cinderclient-1.0.7-1.el6ost.noarch openstack-cinder-2013.2-8.el6ost.noarch python-cinder-2013.2-8.el6ost.noarch 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. http://rhn.redhat.com/errata/RHEA-2013-1859.html |