Back to bug 1016798
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2013-10-08 17:49:35 UTC | Target Release | --- | 4.0 |
| Eric Harney | 2013-10-08 17:50:34 UTC | Blocks | 1016806 | |
| Eric Harney | 2013-10-08 17:51:38 UTC | Assignee | rhos-maint | eharney |
| Dafna Ron | 2013-10-09 10:05:33 UTC | Keywords | TestBlocker | |
| Eric Harney | 2013-10-09 13:31:01 UTC | Status | NEW | ASSIGNED |
| Doc Text | Configure Gluster to allow the Cinder user to write to the share. # gluster volume set cinder-vol storage.owner-uid=165 # gluster volume set cinder-vol storage.owner-gid=165 | |||
| Doc Type | Bug Fix | Enhancement | ||
| Giulio Fidente | 2013-10-10 13:50:32 UTC | CC | gfidente | |
| Eric Harney | 2013-10-21 19:24:22 UTC | CC | dron | |
| Flags | needinfo?(dron) | |||
| Haim | 2013-10-22 08:10:58 UTC | Keywords | TestBlocker | |
| Flags | needinfo?(dron) | |||
| Dafna Ron | 2013-10-22 11:45:36 UTC | Flags | needinfo?(hateya) | |
| Stephen Gordon | 2013-11-18 20:39:23 UTC | CC | sgordon | |
| Target Milestone | --- | rc | ||
| Eric Harney | 2013-11-19 15:11:27 UTC | CC | yrabl | |
| Eric Harney | 2013-11-19 15:37:53 UTC | Link ID | OpenStack gerrit 56482 | |
| Eric Harney | 2013-11-20 14:53:14 UTC | Priority | unspecified | high |
| Status | ASSIGNED | ON_DEV | ||
| Eric Harney | 2013-11-20 16:53:51 UTC | Doc Text | Configure Gluster to allow the Cinder user to write to the share. # gluster volume set cinder-vol storage.owner-uid=165 # gluster volume set cinder-vol storage.owner-gid=165 | Workaround: Configure Gluster to allow the Cinder user to write to the share. # gluster volume set cinder-vol storage.owner-uid=165 # gluster volume set cinder-vol storage.owner-gid=165 or, after deployment, when Cinder has mounted the share: # chgrp cinder /var/lib/cinder/mnt/<uuid> # chmod g+w /var/lib/cinder/mnt/<uuid> |
| Doc Type | Enhancement | Known Issue | ||
| Haim | 2013-11-21 08:51:57 UTC | QA Contact | hateya | dron |
| Flags | needinfo?(hateya) | |||
| Eric Harney | 2013-11-26 22:07:05 UTC | Link ID | OpenStack gerrit 57542 | |
| Ayal Baron | 2013-12-01 10:10:19 UTC | CC | abaron | |
| Eric Harney | 2013-12-02 22:33:59 UTC | Blocks | 1033714 | |
| Eric Harney | 2013-12-03 22:31:42 UTC | Status | ON_DEV | POST |
| Eric Harney | 2013-12-03 22:56:08 UTC | Blocks | 1033652 | |
| Eric Harney | 2013-12-04 20:10:41 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-cinder-2013.2-5.el6ost | |||
| Link ID | OpenStack gerrit 56482 | |||
| Eric Harney | 2013-12-04 20:14:59 UTC | Doc Text | Workaround: Configure Gluster to allow the Cinder user to write to the share. # gluster volume set cinder-vol storage.owner-uid=165 # gluster volume set cinder-vol storage.owner-gid=165 or, after deployment, when Cinder has mounted the share: # chgrp cinder /var/lib/cinder/mnt/<uuid> # chmod g+w /var/lib/cinder/mnt/<uuid> | Cause: Cinder expected GlusterFS to be writable by the Cinder volume service. Consequence: GlusterFS snapshots were not created correctly. Fix: Cinder now forces the permissions to be what it expects on the GlusterFS share, or it will not attempt to create a snapshot. Result: GlusterFS snapshots work correctly if share permissions were not configured correctly beforehand. |
| Summary | cinder: can't create a snapshot when cinder is configured to work with gluster | GlusterFS: can't create a snapshot when cinder is configured to work with gluster (permissions) | ||
| Doc Type | Known Issue | Bug Fix | ||
| errata-xmlrpc | 2013-12-04 21:10:37 UTC | Status | MODIFIED | ON_QA |
| Dafna Ron | 2013-12-10 18:07:22 UTC | Status | ON_QA | VERIFIED |
| Don Domingo | 2013-12-10 23:46:01 UTC | CC | ddomingo | |
| Doc Text | Cause: Cinder expected GlusterFS to be writable by the Cinder volume service. Consequence: GlusterFS snapshots were not created correctly. Fix: Cinder now forces the permissions to be what it expects on the GlusterFS share, or it will not attempt to create a snapshot. Result: GlusterFS snapshots work correctly if share permissions were not configured correctly beforehand. | Previously, Cinder 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 Cinder 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. With this fix, Cinder 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 if Cinder does not have write permissions to the share. |
||
| Eric Harney | 2013-12-10 23:49:14 UTC | Doc Text | Previously, Cinder 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 Cinder 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. With this fix, Cinder 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 if Cinder does not have write permissions to the share. | Previously, Cinder 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 Cinder 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, Cinder 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 if Cinder does not have write permissions to the share before any data is modified. |
| Don Domingo | 2013-12-11 23:34:05 UTC | Doc Text | Previously, Cinder 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 Cinder 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, Cinder 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 if Cinder does not have write permissions to the share before any data is modified. | 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. |
| errata-xmlrpc | 2013-12-19 17:31:14 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2013-12-20 00:26:48 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-12-19 19:26:48 UTC | |||
| Perry Myers | 2016-04-26 20:25:38 UTC | CC | pmyers |
Back to bug 1016798