cinder backup fails with nfs volume + nfs backup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Undecided
|
Vladislav Belogrudov |
Bug Description
When using nfs backends for volumes and backups cinder fails in some situations because of permission issues. One example of such situation is running an instance from Horizon and making it a cinder volume at the same time (default). This leads to a volume file with qemu ownership. Cinder backup runs as cinder user and cannot do anything with such volume:
2017-10-24 12:20:09.259 1 ERROR oslo_messaging.
2017-10-24 12:20:09.259 1 ERROR oslo_messaging.
2017-10-24 12:20:09.259 1 ERROR oslo_messaging.
2017-10-24 12:20:09.259 1 ERROR oslo_messaging.
This is due to recent default NFS backend settings:
nas_secure_
nas_secure_
There is a similar bug @ RedHat - https:/
https:/
"""
Cause: The NFS backend driver for Cinder implements enhanced NAS security features that default to being enabled. However, the features require non-standard configuration changes in Nova's libvirt, and without those changes some cinder volume operations fail.
Consequence: Some cinder volume operations fail when using the NFS backend.
Fix: Add TripleO settings to control the NFS driver's NAS secure features, and disable the features by default.
"""
Also these features enabled actually disable possibility to use snapshots.
Changed in kolla-ansible: | |
assignee: | nobody → Vladislav Belogrudov (vlad-belogrudov) |
Fix proposed to branch: master /review. openstack. org/514639
Review: https:/