Moving cinder from host to containers changes ownership of files on NFS backend
Bug #1887435 reported by
Alan Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Committed
|
Medium
|
Alan Bishop |
Bug Description
When a cinder driver uses NFS to access volumes on a storage backend, upgrading from Pike to Queens causes files on the NFS share to change ownership to 42407:42000 (the UID:GID for cinder:kolla). This happens because kolla's startup script for the cinder-volume service recursively changes the ownership of anything in cinder's /var/lib/cinder service directory [1].
This is a problem when upgrading from a non-containerized deployment (Pike). Although the cinder-volume service has been stopped on the host, the NFS share is still mounted. Later, when kolla executes [1], files on the backend are affected because the NFS mount point is under /var/lib/
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
Changed in tripleo: | |
milestone: | victoria-3 → wallaby-1 |
Changed in tripleo: | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
Fix proposed to branch: stable/queens /review. opendev. org/741940
Review: https:/