Red Hat Bugzilla – Bug 1480490
[Huawei] [Defect] [Cinder] - Huawei Storage Cinder driver fixs metadata issues by change private date storing place in Redhat openstack 11
Last modified: 2018-02-13 11:29:16 EST
Description of problem:
Change Huawei driver's private data storing place to fix issues below:
This patch is to fix issues at two circumstances:
1. Create volume from image by non-admin user, this operation will fail because Huawei driver tries to record LUN WWN at admin metadata, however non-admin user doesn't have the admin metadata access right, so exception is raised.
2. Restore volume backup to 3rd volume, this operation will also restore backup volume's metadata to the 3rd volume, but the data recorded in metadata is strong correlative to the corresponding LUN at backend storage, so this will break the one-to-one relationship between the restored volume and the LUN at storage.
To fix the issues above, we moved all LUN private data to provider_location, stored as a dict string, not use admin metadata or metadata to store LUN private data.
So it's necessary to backport to redhat openstack 11(Ocata) stable branch for Huawei cinder driver.
Version-Release number of selected component (if applicable):
Redhat Openstack 11, python-cinder
Steps to Reproduce:
1. login as no-admin user
2. excute create a volume from image task
3. create task failed
create task fails due to admin metadata access Permission denied。
Create a volume from image from non-admin user successfully.
The openstack community in Newton has fixed this bug in blueprint:
Primary Red Hat contact:
a. Name: Jingjing Niu
b. Email: email@example.com
Primary Partner contact:
a. Name: Taifu Xiong
b. Email: firstname.lastname@example.org
c. Primary Phone: 15922901778
This may require this follow-up:
This issue is fixed in below bugzilla id which is already released.
The version is openstack-cinder-10.0.4-3.el7ost.noarch
According to our records, this should be resolved by openstack-cinder-10.0.4-3.el7ost. This build is available now.
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.