Description of problem: cinder-backup container doesn't have the source NFS share mounted so backing up such volumes fails. When we manually mount the source NFS folder in the cinder-backup container, backups starts working. Version-Release number of selected component (if applicable): All How reproducible: This environment. Steps to Reproduce: 1. Try to backup a cinder volume 2. 3. Actual results: Fails Expected results: Succeeds Additional info:
I'm wondering if brick shouldn't use those mount options if they are defined ? [username@hostname cinder]$ cat cinder.conf | grep mount_options #backup_mount_options = <None> backup_mount_options=vers=4.0,rw,sync,nosharecache,context=system_u:object_r:cinder_var_lib_t:s0 #nfs_mount_options = <None> #nas_mount_options = <None> #vzstorage_mount_options = <None> #zfssa_nfs_mount_options = nfs_mount_options=vers=4.0,rw,sync,nosharecache,context=system_u:object_r:cinder_var_lib_t:s0
os-brick is a library that is used by several services, e.g. nova-compute, that won't have access to cinder.conf. I think what we need is an RFE that allows cinder to somehow "pass" NFS options to os-brick whenever clients (nova-compute, glance-api, cinder-backup) need to connect to a volume. This is a good topic for the cinder squad to discuss.
Hi, Are there any plan to implement this feature? Just to have an update after +1y.