Bug 1561746 - Huawei cinder driver is always enforcing QOS on backend side
Summary: Huawei cinder driver is always enforcing QOS on backend side
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
: 10.0 (Newton)
Assignee: Eric Harney
QA Contact: Avi Avraham
RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks: 1417761
TreeView+ depends on / blocked
 
Reported: 2018-03-28 19:41 UTC by Eric Harney
Modified: 2019-07-10 15:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1417761
Environment:
Last Closed: 2019-07-10 15:46:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Eric Harney 2018-03-28 19:41:01 UTC 
+++ This bug was initially created as a clone of Bug #1417761 +++

Description of problem:
When using QOS for cinder volume, the huawei cinder driver attempts to enforce QOS on the backend even if consumer is set to front-end (nova). If the SAN is not able to do QOS, volume creation fails.

Version-Release number of selected component (if applicable):
openstack-cinder-8.1.1-2

How reproducible:
Every time a volume with QOS is created

Steps to Reproduce:
1. Use Huawei backend that doesn't support QOS
2. Set QOS consumer to front-end
3. Create volume

Actual results:
Volume creation fails

Expected results:
Volume creation succeeds

Additional info:
Modifying the driver by adding: https://github.com/huaweistorage/OpenStack_Driver/blob/master/Cinder/Mitaka/smartx.py#L48-L50 allows this to function correctly.
Note You need to log in before you can comment on or make changes to this bug.