Closed awels closed 4 years ago
Thanks for the bug report.
Looks like Ember-CSI is not respecting the capacity_range
field, because the CO is not setting limit_bytes
, so we can return a larger volume than requested, and we still fail.
Debug logs of a 200Mi volume:
2020-03-12 14:39:18 lvm INFO ember_csi.common [req-9feaa5bf-7a34-492f-9215-fc90067db483] => GRPC CreateVolume pvc-2295813b-3bf7-4bef-b9b2-986eb56401f4
2020-03-12 14:39:18 lvm DEBUG ember_csi.common [req-9feaa5bf-7a34-492f-9215-fc90067db483] With params:
name: "pvc-2295813b-3bf7-4bef-b9b2-986eb56401f4"
capacity_range {
required_bytes: 209715200
}
volume_capabilities {
mount {
fs_type: "ext4"
}
access_mode {
mode: SINGLE_NODE_WRITER
}
} dolog /ember-csi/ember_csi/common.py:127
2020-03-12 14:39:18 lvm ERROR ember_csi.common [req-9feaa5bf-7a34-492f-9215-fc90067db483] !! GRPC CreateVolume failed in 0s with OUT_OF_RANGE (Unsupported capacity_range (min size is 1GB)): Exception
When I create a PVC of size lets say 200Mi ember is rejecting the PVC request with this error in the logs:
Now I understand cinder only supports volumes sizes to the nearest GB, but I would expect it to create a 1G PV for me and that should get bound to my requested PVC.