ensure_export model_update ignored
Bug #1918449 reported by
Walt Boring
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Incomplete
|
Wishlist
|
Unassigned |
Bug Description
The volume manager calls the driver's ensure_export() at startup time. There are several volume drivers that return a model_update from ensure_export, but the volume driver ignores that model_update.
https:/
For example,
cinder reference driver lvm.py
https:/
hpe 3par driver
https:/
https:/
Changed in cinder: | |
status: | New → Incomplete |
importance: | Undecided → Wishlist |
tags: | added: manager volume |
To post a comment you must log in.
In the case of the LVM driver, this doesn't seem to matter, because it returns ensure_export() from the target driver, but none of the target drivers appear to return anything.
Does the 3par driver actually return updated values in this situation? Do any other drivers?
I ask because it's not clear if we actually need to apply model_updates from the ensure_export driver method -- the API may just be that it isn't expected to update any information.