Skip to main content
NetApp Knowledge Base

OpenStack: During controller upgrade, write access to Cinder volumes is lost

Views:
5
Visibility:
Public
Votes:
0
Category:
openstack
Specialty:
virt
Last Updated:

Applies to

  • OpenStack Yoga
  • Canonical packages
  • NFSv3 storage pool

Issue

During a OpenStack controller upgrade from Xena to Yoga, user ownership of Cinder volumes on a backing NFSv3 mounted storage pool changes.  As a result, this causes instances to lose write access to their underlying storage. 

Details of the environment where this issue has been seen:

  • Systemd deployment
  • Canonical Cinder packages
  • NFSv3 Storage Pools

When upgrading the 'cinder-common' package, the following changes are observed:

  1. Prior to the cinder-common package upgrade, the Cinder volumes on the Compute nodes are owned by a user such as libvirt-qemu:

$ getfacl -e /opt/stack/data/nova/mnt/d25beb55fef91aab4945de91411d8dc5/volume-d6f844c6-5be0-41ba-ae85-898743dfd991
getfacl: Removing leading '/' from absolute path names
# file: opt/stack/data/nova/mnt/d25beb55fef91aab4945de91411d8dc5/volume-d6f844c6-5be0-41ba-ae85-898743dfd991
# owner: libvirt-qemu
# group: kvm
user::rw-
group::rw-
other::---

  1. The cinder-common package is upgraded
  2. Ownership of the Cinder volumes on the compute nodes changes to something like cinder:cinder (in this example, there is no cinder user on the compute host therefore a user id such as 64061 is seen):

$ getfacl -e /opt/stack/data/nova/mnt/d25beb55fef91aab4945de91411d8dc5/volume-d6f844c6-5be0-41ba-ae85-898743dfd991
getfacl: Removing leading '/' from absolute path names
# file: opt/stack/data/nova/mnt/d25beb55fef91aab4945de91411d8dc5/volume-d6f844c6-5be0-41ba-ae85-898743dfd991
# owner: 64061
# group: 64061
user::rw-
group::rw-
other::---

  1. Depending upon the unix permissions on the Cinder volumes, the instances either go into a 'read-only' state or access is lost completely

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.