You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// If SP has VOLUME_MOUNT_GROUP node capability and CO provides
2252
2254
// this field then SP MUST ensure that volume is mounted with
2253
-
// provided volume_mount_group.
2255
+
// provided volume_mount_group and all files and directories
2256
+
// within the volume are readable and writable by the provided
2257
+
// volume_mount_group.
2258
+
// If NodeStageVolume was previously called with volume_mount_group
2259
+
// CO must ensure that NodePublishVolume does not get called
2260
+
// with different volume_mount_group for same volume_id.
2254
2261
// This is a OPTIONAL field.
2255
2262
string volume_mount_group = 9;
2256
2263
}
@@ -2272,6 +2279,7 @@ The CO MUST implement the specified error recovery behavior when it encounters t
2272
2279
| Volume published but is incompatible | 6 ALREADY_EXISTS | Indicates that a volume corresponding to the specified `volume_id` has already been published at the specified `target_path` but is incompatible with the specified `volume_capability` or `readonly` flag. | Caller MUST fix the arguments before retrying. |
2273
2280
| Exceeds capabilities | 9 FAILED_PRECONDITION | Indicates that the CO has exceeded the volume's capabilities because the volume does not have MULTI_NODE capability. | Caller MAY choose to call `ValidateVolumeCapabilities` to validate the volume capabilities, or wait for the volume to be unpublished on the node. |
2274
2281
| Staging target path not set | 9 FAILED_PRECONDITION | Indicates that `STAGE_UNSTAGE_VOLUME` capability is set but no `staging_target_path` was set. | Caller MUST make sure call to `NodeStageVolume` is made and returns success before retrying with valid `staging_target_path`. |
2282
+
| Volume staged with different volume_mount_group | 9 FAILED_PRECONDITION | Indicates that volume with specified `volume_id` was node staged using different `volume_mount_group` on this node and hence can not be node published. | Caller MUST make sure that `NodePublishVolume` is called with same `volume_mount_group` which was used in `NodeStageVolume`. |
0 commit comments