Setup Error Detection missing in CloudByte Driver
Bug #1501304 reported by
Abhishek Shrivastava
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
Currently in CloudByte Cinder driver there is now way of checking the "absence" or "validity" of configuration parameters, which are configured by clients during DevStack setup against CloudByte Storage in "cinder.conf".
In this case the cinder-volume service initializes the driver with the absent or invalid parameters, and due to this several ambiguity happens at client-end, like:
* Volume related operation failure.
* No proper detection of the cause of failure.
So, to rectify this problem a new method should be build which will check the absence and validity of configuration parameters and will not initialize the driver until the cause is rectified.
Changed in cinder: | |
status: | New → In Progress |
assignee: | nobody → Abhishek Shrivastava (abhishek-2) |
tags: | added: cloudbyte drivers |
Changed in cinder: | |
status: | In Progress → New |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/229814
Review: https:/