disk cachemodes should be restricted with multiattached volumes

Bug #1788619 reported by Eric Harney
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Invalid
High
Unassigned
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

If using multiattach, the "writeback" and "unsafe" disk_cachemode options presumably break the semantics that an application writing to a clustered datastore would rely on for data consistency between multiple nodes.

Volumes should not be allowed to attach to multiple instances (multiattach) with unsafe cache modes.

(This may even include writethrough? I'm not sure.)

Tags: cinder volumes
Jay Bryant (jsbryant)
Changed in cinder:
importance: Undecided → High
tags: added: cinder volumes
Revision history for this message
Matt Riedemann (mriedem) wrote :

Have you tested this or just guessing that the libvirt driver in nova isn't doing the right thing? Because multiattach disks are always set to cache mode "none":

https://github.com/openstack/nova/blob/20bc0136d0665bafdcd379f19389a0a5ea7bf310/nova/virt/libvirt/driver.py#L423-L426

        # Shareable disks like for a multi-attach volume need to have the
        # driver cache disabled.
        if getattr(conf, 'shareable', False):
            conf.driver_cache = 'none'

Changed in nova:
status: New → Invalid
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

Description only refers to nova settings. I don't see anything here for Cinder, so I am going to close it as Invalid. If there is something, please reopen and provide more detail what Cinder is doing (or not doing) that it should.

Changed in cinder:
status: New → Invalid
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.