Bug 1566091
Summary: | Cinder backup uses os_brick to create a nfs share for backup and fails creating subdirectories | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Pranali Deore <pdeore> |
Component: | openstack-cinder | Assignee: | Pranali Deore <pdeore> |
Status: | CLOSED ERRATA | QA Contact: | Avi Avraham <aavraham> |
Severity: | medium | Docs Contact: | Kim Nylander <knylande> |
Priority: | high | ||
Version: | 12.0 (Pike) | CC: | aavraham, abishop, coldford, dmaley, dvd, eharney, geguileo, juwu, jzaher, mmethot, pdeore, pgrist, scohen, srevivo, tshefi |
Target Milestone: | z3 | Keywords: | Triaged, ZStream |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-cinder-11.1.0-10.el7ost | Doc Type: | Bug Fix |
Doc Text: |
The Cinder Backup service's NFS backend assumed that the NFS server has been configured to allow the Backup service to create files and directories on the server. The Backup service runs as a non-privileged 'cinder' user, and this requires file permissions and ownership on the server be set correctly. This caused backups to fail if the NFS server wasn't configured to allow the 'cinder' user to create files and directories. With this update, when initializing the NFS backend, the Backup service checks whether the server's permissions and directory ownership are correct. The permissions and directory ownership are updated automatically to ensure the Backup service works correctly.
|
Story Points: | --- |
Clone Of: | 1489127 | Environment: | |
Last Closed: | 2018-08-20 12:46:46 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: | |||
Bug Blocks: | 1489127, 1566071 |
Comment 5
Tzach Shefi
2018-07-02 11:50:32 UTC
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. https://access.redhat.com/errata/RHBA-2018:2516 |