NetApp driver prints confusing warning when vsadmin credentials are used

Bug #1284796 reported by Ben Swartzlander
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Ben Swartzlander

Bug Description

If I configure cinder with the NetApp driver and provide a username/password with only vsadmin access (not cluster admin), I get the following warning:

The user does not have access or sufficient privileges to use all ssc apis. The ssc features [disk type, raid type] may not work as expected.

This message doesn't really make it clear what you can and can't do under the circumstances. I also notice that there's an inconsistency with the spelling of "dedup", "nodedup", and "nodedupe".

Changed in cinder:
assignee: nobody → Ben Swartzlander (bswartz)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/76343

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/76343
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b40efb3633b4bffada4d5f191d26c4c75da9815e
Submitter: Jenkins
Branch: master

commit b40efb3633b4bffada4d5f191d26c4c75da9815e
Author: Ben Swartzlander <email address hidden>
Date: Tue Feb 25 11:44:14 2014 -0800

    Change warning message in NetApp driver for vsadmin creds

    The new warning messages explicitly lists the extra_specs that
    can't be supported depending on the access level fo the creds
    that were provided. Also corrects a spelling error for the
    netapp_nodedup extra_spec.

    Change-Id: I1b27d9f4043321a4812e4e457c32a1040676c8e5
    Closes-Bug: 1284796

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in cinder:
milestone: none → icehouse-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: icehouse-3 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.