Users with _member_ or member roles are unable to use cinder-volume via Horizon Dashboard.
Version:
Queens
Environment:
openstack-dashboard-13.0.2-0.20180913182351.c7dc4b4.el7.noarch
openstack-cinder-12.0.4-0.20181005163903.8b1aa5f.el7.noarch
python2-cinderclient-3.5.0-0.20180211213738.1de605c.el7.centos.noarch
python-cinder-12.0.4-0.20181005163903.8b1aa5f.el7.noarch
puppet-cinder-12.4.1-0.20180831230802.22ee15c.el7.noarch
puppet-horizon-12.4.1-0.20180921011912.0177965.el7.noarch
How reproducible:
Every time. Tested with file, nfs, rbd cinder backends.
Step to reproduce:
1. Assign a user with either _member_ or member role to a project;
2. Log in as the user and switch to the project;
3. Go to Project -> Compute -> Instances, click on "Launch Instance" to get following errors:
Error: Unable to retrieve the volume snapshots.
Error: Unable to retrieve the volumes.
(Notice that users are unable to choose volume as a boot source from Source)
4. Go to Project -> Volumes -> Volumes, Click on "Create Volume" to get following errors:
Error: Unable to retrieve list of volumes.
Error: Unable to retrieve volume snapshots.
These problems only affect users using Horizon Dashboard. The same users have no issues with cinder-volume service via CLI.
codylab suggested i might have a very similar issue.
On Newton i am using the cinder. volume. drivers. san.hp. hpmsa_fc. HPMSAFCDriver driver for a second volume/cinder backend.
A _member_ user on the command line is creating volumes on the correct storage backend, our HP MSA).
But while in Horizon the _member_ user is creating volumes on the incorrect storage backend (our RBD/CEPH), even though the same MSA volume type as on the command line is being selected
any news on a fix for this I'd love to overlay/dropfile a fix into my Newton environment.
thanks!